Technical Depth vs Breadth

In this lesson, Adam Ernst, Software Engineer at Meta, shares his perspective on what it takes to reach the highest levels of the Individual Contributor (IC) career ladder. Rather than choosing between technical depth and breadth, Adam explains how he developed both by following curiosity and solving real engineering problems. He describes a practical approach to learning unfamiliar systems, collaborating effectively across teams, and continuously expanding his expertise through hands-on experience instead of formal study.

• Develop Both Depth and Breadth: Adam believes senior engineers benefit from deep expertise in their primary domain while gradually building knowledge across adjacent systems. This combination enables engineers to solve complex cross-functional problems and make a broader organizational impact.
• Learn Through Real Problems: Instead of studying technologies in isolation, Adam dives deeply into unfamiliar systems only when they become relevant to the problem at hand. Solving real engineering challenges creates meaningful learning opportunities and builds lasting expertise.
• Become Self-Sufficient and Collaborative: By investigating issues independently before asking for help, engineers not only reduce the burden on partner teams but also arrive with informed questions and potential solutions. This approach accelerates learning, builds credibility, and strengthens cross-team relationships.