“The Coding Machine” at Meta – with Michael Novati

Key Concepts:

• Coding Machine: An engineer who delivers outsized impact through rapid and high-quality code production, refactoring, and unblocking other engineers.
• Archetypes: Models of successful engineers at Meta (Facebook), used for performance reviews and promotions to ensure fairness and recognize diverse contributions.
• Impact: The primary metric for evaluating engineers at Meta, focusing on how their work moves projects forward, launches products, and improves the codebase.
• Product Engineering Culture: A culture where internal tools are treated as products, built on the same codebase as user-facing features, fostering innovation and efficiency.
• Zuck Review: A weekly product review session with Mark Zuckerberg, providing direct feedback and guidance on product development.
• Hiring Committee: A group of directors and VPs at Meta who review candidate packets and make final hiring decisions, ensuring level consistency and identifying potential red flags.
• Team Matching: A process where candidates who pass the on-site interviews must then match with a specific team to receive an offer.

1. The Coding Machine Archetype at Meta

• Definition: The "coding machine" archetype was created at Meta (Facebook) around 2015 to recognize Michael Naati's unique contributions. It describes an engineer who delivers significant impact through rapid code production, refactoring, and unblocking other engineers.
• Controversy: The archetype is controversial because simply writing a lot of code doesn't qualify someone as a coding machine. The key is the impact of that code.
• Examples of Impact:
  • Moving projects forward rapidly.
  • Enabling one engineer to do the work of a 5-10 person team.
  • Unblocking other engineers by pushing things forward.
  • Refactoring code quickly so new engineers don't have to deal with legacy libraries.
• Michael's Role: Michael was known for quickly prototyping, refactoring, and cleaning up codebases, often contributing to projects "on the side" while also fulfilling his responsibilities as a product engineer.
• Tom Allison's Sponsorship: Tom Allison, now head of the Facebook app, championed Michael and worked with other VPs to create the coding machine archetype.
• Professional Sports Analogy: The archetype system is likened to a professional sports team, where each player has a specialty but is also proficient in the basics. The coding machine is the go-to person for rapid prototyping or refactoring.

2. Meta's Engineering Culture and Archetypes

• Fairness and Pattern Matching: Archetypes are used to ensure fairness in performance reviews and promotions by providing examples of what engineers at different levels should look like. They are modeled after existing engineers.
• Specialties: While all engineers at a certain level can perform basic tasks, archetypes recognize individuals with exceptional specialties.
• Engineering-First Culture: Meta has an engineering-first culture that values individual contributors and empowers them to have a significant impact.
• Individual Contributor (IC) vs. Manager: Meta aimed to break the idea that you have to be a manager to progress. Senior ICs were intended to be superstars with social influence.
• Limitations of IC Impact: Even with exceptional coding ability, an IC's impact has a limit compared to a manager who can oversee and direct the work of many engineers.
• Tenure Importance: For senior IC roles (E8+), tenure becomes crucial because long-term employees have a deep understanding of the systems, a strong network, and are better aligned with Meta's values.
• External vs. Internal Hires: External hires at senior levels often struggle to align with Meta's values and have a harder time making an impact compared to those who rose through the ranks internally.
• Values in Practice: Meta's values, such as "move fast and break things" and "be bold," were genuinely practiced and rewarded, even if they led to mistakes.

3. Michael's Career Trajectory at Meta

• Rapid Progression: Michael went from intern to E7 (principal engineer equivalent) in six years, a significantly faster trajectory than typical.
• Key Factors:
  • Manager Relationship: Trust and transparency with managers were crucial. Michael's managers knew his strengths and weaknesses, and he trusted them to put him in the right roles. He also helped his managers by mentoring junior engineers.
  • Work Log: Michael kept a notepad of accomplishments to use in performance reviews, ensuring his contributions were recognized.
• Intern Project: As an intern, Michael rewrote Meta's org chart tool, making it horizontal and more user-friendly. This was well-received and reinforced the idea that anyone could contribute impactful code.
• Product Engineer Role: Michael was always allocated to a product team but spent a significant portion of his time on refactoring and codebase-wide efforts.

4. Meta's Internal Tools and Product Engineering Culture

• Internal Tools as Products: Meta treated internal tools as products, built on the same codebase as user-facing features. This fostered a culture of innovation and rapid development.
• Custom Infrastructure: Meta built its own infrastructure from scratch, including servers and hardware, leading to the development of custom tools to work with this infrastructure.
• Engineering Product Ecosystem: The company had a strong engineering product ecosystem, where even non-engineers felt like they were part of a technology company solving problems with internal tools.
• Examples of Internal Tools: Custom version control, code review tools, build tools (Buck), experimentation platforms (Gatekeeper), and meeting room booking tools.
• Seeding of Startups: Many startups have been founded by former Meta employees who saw the potential to productize internal tools and concepts developed at Meta.
• Mark Zuckerberg's Vision: Mark Zuckerberg wanted Facebook to be known for training people to build good products and become successful founders.

5. Interaction with Mark Zuckerberg and the Zuck Review

• Friendship: Michael became Facebook friends with Mark Zuckerberg after a strategic maneuver in a game of Risk.
• Zuck Review: Weekly product review sessions with Mark Zuckerberg, where teams presented their work and received feedback.
• Detail-Oriented Feedback: Zuckerberg asked detailed questions and focused on whether he trusted the team's judgment.
• Honesty and Product Focus: The goal was to be honest about the product's strengths and weaknesses and to find ways to improve it.

6. Outages and Learning Experiences

• Profile Picture Template Outage: A feature allowing users to overlay a French flag template on their profile pictures caused a major outage when 100 million people used it, overloading the database node where the template was stored.
• Two-Way Edge Problem: The issue was caused by a two-way edge between the template and the profiles, leading to excessive writes on a single database node.
• Prototype vs. Production: The two-way edge was used in the prototype to simplify logging and data collection, but it was not suitable for production.
• Resolution: The infrastructure team removed the two-way edge and made it a one-way edge. The feature was then productionized with proper logging and performance considerations.
• Importance of Systems Design: The outage highlighted the importance of understanding basic systems design principles, such as federation and partitioning.

7. Meta's Hiring Process and Hiring Committee

• Interview Process: The process starts with a recruiter screen, followed by a technical screen (coding interview), and then an on-site interview with coding, behavioral, and systems design components.
• Technical Interview Characteristics: Meta's technical interviews are known for being whiteboarding style with almost no small talk.
• Hiring Committee:
  • Purpose: To review candidate packets and make final hiring decisions, ensuring level consistency and identifying potential red flags.
  • Composition: A quorum of at least three directors or VPs of engineering.
  • Packet Contents: Interview feedback, interview history of the interviewers, histogram of past ratings, questions asked, and number of times those questions were asked.
  • Focus: Leveling is the most common topic of discussion, ensuring the candidate is hired at the appropriate level.
• Open Door Policy: The hiring committee meetings were open, allowing engineers to observe and provide input.
• Michael's Motivation: Michael attended the meetings to ensure Meta didn't lower its hiring bar as it scaled.

8. Interviewing Advice and Job Market Trends

• Similar Recruitment Processes: Many top tech companies have similar recruitment processes to Meta, borrowing from each other and focusing on stack-agnostic problem-solving skills.
• Importance of Preparation: It's crucial to prepare for these interviews, even for experienced engineers, as they test fundamental skills that may not be used in day-to-day work.
• Job Market Changes: The job market has become more competitive, with more candidates and new processes like team matching.
• Team Matching Process: Candidates who pass the on-site interviews must then match with a specific team to receive an offer.
• Online Assessments: More companies are using online assessments to filter candidates early in the process.
• Finding the Right Job: It's more important to find the right job than to simply pass an interview.

9. Rapid Fire Questions

• Diffs Closed in Most Productive Year: Thousands, potentially 5,000-10,000 per year.
• Language Used Most at Meta: Hack (Meta's version of PHP).
• Language Used Most Now: JavaScript (front-end and back-end).
• Favorite Programming Language: TypeScript, because it helps catch bugs and encourages better code structure.
• Book That Had an Impact: "Histories" by Herodotus, which showed the power of storytelling in communicating events and influencing people.

10. Synthesis/Conclusion

The video provides a detailed look into Meta's engineering culture, hiring practices, and the concept of the "coding machine" archetype. It highlights the importance of impact, fairness, and continuous learning in a fast-paced environment. Michael Naati's experiences offer valuable insights into how to succeed as an engineer at Meta and the importance of adapting to changing job market trends. The discussion emphasizes that while technical skills are essential, understanding the company's values and culture is equally important for long-term success.