Defining Good Code
How do you define 'good code'? Describe a time you demonstrated exceptional code quality or introduced a standard that improved overall codebase health.
Why Interviewers Ask This
Meta interviewers ask this to assess your engineering philosophy beyond syntax. They evaluate if you prioritize maintainability, scalability, and readability over quick fixes. This question reveals whether you align with Meta's culture of long-term impact and open-source collaboration, ensuring you build systems that other engineers can easily understand and extend.
How to Answer This Question
1. Define your framework: Start by articulating a multi-dimensional definition of good code, explicitly mentioning readability, testability, performance, and modularity rather than just 'working' code. 2. Select a specific STAR scenario: Choose a story where you identified technical debt or a lack of standards that hindered team velocity at a previous role. 3. Detail the action: Explain how you introduced a concrete standard, such as a new linting rule, a refactoring strategy, or a documentation template, emphasizing your leadership in getting buy-in from peers. 4. Quantify the outcome: Use metrics like reduced bug rates, faster onboarding times for new hires, or decreased merge conflicts to prove the value of your intervention. 5. Connect to Meta: Conclude by linking your approach to Meta's emphasis on moving fast while maintaining a robust, scalable infrastructure for billions of users.
Key Points to Cover
- Prioritizing maintainability and readability over immediate speed
- Demonstrating leadership through introducing tangible standards
- Using specific metrics to quantify improvements in code health
- Aligning personal values with Meta's focus on long-term impact
- Showing ability to influence team culture and adoption
Sample Answer
I define good code not just by its ability to run, but by its longevity and clarity for future maintainers. For me, it must be readable, well-tested, performant, and modular. At my last company, our frontend codebase was…
Common Mistakes to Avoid
- Focusing solely on technical syntax without addressing human factors like readability
- Claiming all previous code was perfect and ignoring real-world technical debt
- Providing vague examples without quantifiable outcomes or specific actions taken
- Neglecting to mention collaboration or how you convinced others to adopt the standard
Sound confident on this question in 5 minutes
Answer once and get a 30-second AI critique of your structure, content, and delivery. First attempt is free — no signup needed.