Matt Fitzpatrick: The Subtle Art of Engineering Your Career

You're grinding through another feature, debugging some ancient Python, when a Slack message pops up: "Hey, got a sec? Wanna pick your brain about career stuff. Specifically, how do you even think about your career trajectory after Staff+?" You're not alone. We all hit that point where the next "promotion" isn't just about coding harder. It's about influence, strategy, and often, a surprising amount of soft skills. This is where guys like Matt Fitzpatrick come in, not as a guru, but as a lens. He hasn't written the definitive guide to your career, but his work, particularly the "Ten Things" series, offers a valuable framework for understanding what separates the good from the truly impactful.

Beyond the Code: Impact, Not Just Output

Early in your career, you're judged on output. Can you ship code? Does it work? Is it tested? That's table stakes. You quickly learn that shipping a ton of features that no one uses, or that break constantly, isn't actually impact. Fitzpatrick's "Ten Things I've Learned About Teams" isn't just theoretical; it codifies observations you've probably already made but haven't articulated. For example, he talks about "getting to zero" – clearing out the cruft, the tech debt, the unresolved issues. This isn't glamorous, it’s not a new microservice, but it dramatically improves team velocity and morale.

Think about the last time your team was stuck on a project. Was it a lack of coding skill? Probably not. It was likely unclear requirements, a dependency hell, or a political blockage from another team. Identifying and unblocking these systemic issues, rather than just writing more code, is a skill that senior individual contributors (ICs) and managers excel at. This is a subtle but profound shift. It’s moving from "how do I solve this problem?" to "what is the real problem we should be solving, and what's stopping us?"

The "Ten Things" Framework: A Mental Model for Growth

Fitzpatrick doesn't just list ten random ideas. He often structures his observations into actionable categories. Take his "Ten Things I've Learned About Engineering Management." He covers everything from the necessity of radical candor – giving direct feedback, even when it's uncomfortable – to the importance of psychological safety. We often talk about these concepts, but seeing them distilled into concrete principles helps. For example, "Feedback is a gift" isn't a new concept, but Fitzpatrick emphasizes the receiver's responsibility to listen, not just the giver's to deliver.

When you're preparing for a Staff Engineer interview at a place like Google or Meta, they aren't just looking for your technical depth. They want to see how you think about these meta-problems. Can you identify an organizational weakness? Can you propose a cross-team initiative? Can you mentor junior engineers effectively, not just by reviewing their PRs, but by helping them understand the larger system? Matt's frameworks provide a language for discussing these capabilities. You can say, "I've focused on fostering psychological safety by..." instead of just "I try to make people feel comfortable."

The Caveat: Not Every "Ten Things" Applies to Everyone

Here’s the thing: Fitzpatrick writes from a place of experience within specific large tech companies, operating at scale. His observations are incredibly valuable, but they aren't universal dogma. If you're working at a 20-person startup, some of his advice, like "Don't build your own data center," might seem obvious or irrelevant. Conversely, "Focus on developer experience" is always applicable, but the how differs wildly. At a startup, it might mean choosing sensible defaults for your tech stack. At a FAANG, it could mean designing an internal platform used by thousands of engineers.

Your context matters. Don't blindly apply every single point. Instead, use his writing as a prompt: "How does this apply to my team? My company? My career stage?" If he talks about managing upwards, consider who your manager is and what their priorities are. If he discusses organizational debt, think about the specific technical debt that plagues your team. This isn't about memorizing his articles; it's about using them to provoke deeper thought about your own professional environment.

From Theory to Practice: Interview Prep and Beyond

So, how do you actually use this stuff? First, read some of his "Ten Things" series – start with the ones most relevant to your current role or aspiration. For example, if you're aiming for Staff, read the one on ICs. If you're considering management, read that one. Don't just skim. Take notes. What resonates? What challenges your assumptions?

Second, translate these concepts into your own experiences. When you're asked in an interview, "Tell me about a time you influenced a decision without direct authority," you can draw on Fitzpatrick's ideas about communication, building trust, or understanding different perspectives. Instead of a generic answer, you can articulate a specific strategy you employed, perhaps inspired by his emphasis on data-driven arguments or iterative improvements.

For example, when discussing a tricky refactor that required buy-in from three different teams, you might Frame your actions around "optimizing for clarity and shared understanding," similar to his advice on effective communication. You didn't just tell them what to do; you presented a clear trade-off analysis, held multiple cross-functional design reviews on Figma, and prototyped the new API in a sandbox environment to demonstrate feasibility, mirroring his emphasis on demonstrating, not just describing.

Finally, apply this thinking to your actual job. Stop just completing tasks. Start looking for systemic issues. Ask "why" five times. Seek out opportunities to mentor, to improve processes, to clarify strategy. That's the real differentiator for senior engineers – not just writing the best code, but making everyone around you better, and making the entire system more effective.

Ready to Ace Your Next Interview?

Practice with AI-powered mock interviews tailored to your target role and company. Start Practicing for Free | Explore Interview Prep