We scan new podcasts and send you the top 5 insights daily.
Michael Bolin attempted to tackle Meta's massive 'web speed' problem, a 'hero quest' that didn't align with his strengths. This failure taught him that senior impact comes from choosing projects that leverage one's genuine skills and interests, not just tackling the biggest available problem.
Contrary to conventional wisdom, a distinguished engineer advises senior engineers to delegate the most challenging, interesting work. They should instead take on necessary but unglamorous tasks, which builds immense credit and allows junior engineers to grow faster on high-impact problems.
Kevin Scott recounts leaving his PhD because his work was intellectually stimulating but had marginal real-world impact. At Google, he chose to automate ad approvals—a less 'sexy' problem that ultimately saved the company a billion dollars in operating costs, cementing his 'impact-first' framework.
Michael Bolin's experience at Google shows that working hard on high-quality but low-priority projects can lead to frustration and stalled career growth. True impact comes from finding the intersection of personal passion and company-wide strategic importance.
The path to senior engineering levels is tied to the scope of your work's influence. Rather than explicitly seeking promotions, focus on projects with natural potential to grow from solving a team's problem to solving an organization's. The promotions will follow the impact.
Many engineers start by wanting to work on cutting-edge, abstract technical challenges (like LLM memory) but later pivot to finding greater satisfaction in applying that technology to solve concrete customer problems with measurable business impact, a common 'metamorphosis' in their careers.
Just as PMs are warned against solution-bias, the same discipline applies to problems. The goal is not just to find one problem, but to find multiple, then assess which is most valuable, strategically aligned, and worth pursuing for the right audience before committing resources.
A critical career inflection point is moving from solely executing tasks (writing code) to influencing strategic decisions about what problems to solve. True value and impact come from being in the room where decisions are made, not just being the person who implements them.
Michael Bolin proposes a three-step algorithm for career impact: First, identify your genuine passions. Second, understand your employer's strategic priorities. Third, find the intersection between the two and dedicate yourself to it. This alignment maximizes your success and avoids wasted effort.
At Meta, Michael Bolin built the 'Buck' build system during a hackathon to solve excruciatingly slow Android iteration times. Despite widespread skepticism, the dramatic performance improvement won over doubters, proving that solving your own pain can create massive organizational value.
The leap from Senior to Staff Engineer is a major mindset shift. It's not just about solving harder problems, but about autonomously owning the entire lifecycle: identifying the right problems to solve, pitching their value to stakeholders, and then leading the execution end-to-end.