2.1 - The 4 archetypes of an engineering manager
When moving from a technical contributor to management, many engineers face a common frustration: "The company doesn't seem to understand what an Engineering Manager (EM) should actually do".
This confusion happens because engineering management is not a one-size-fits-all role. Depending on the company's size, tech stack, and current bottlenecks, an EM must adjust their focus.
Renowned tech leader Pat Kua outlines this brilliantly in his framework, defining the 5 Engineering Manager Archetypes (The Tech Lead EM, Team Lead EM, Delivery EM, Product EM, and Lead of Leads EM). For a team-level manager transitioning from an Individual Contributor (IC) track, understanding the first four core archetypes is essential to mapping your daily strategy.
Understanding the 4 core archetypes
An EM generally balances four distinct areas: Technical direction, Team growth (People), Process tuning (Delivery), and Product context. Where you spend your energy defines your archetype.
1. The tech lead EM
- Core Focus: Technical Direction & Solutions.
- What they do: This archetype emerges when a manager wears two hats, acting as both the EM and the Tech Lead. They regularly write code, drive architectural discussions, manage technical debt, and actively mentor engineers on coding practices.
- The Trap: Because they are heavily hands-on, they often prioritize writing code or reviewing technical designs at the cost of neglecting 1:1s, team health, and people management.
2. The team lead EM (People-first)
- Core Focus: People Growth & High-Performing Teams.
- What they do: They focus deeply on recruiting, career progression, building retention strategies, and establishing an environment of psychological safety. Unlike the Tech Lead EM, they rarely write code and prefer to let the team drive technical discussions, only stepping in if the team cannot reach a consensus.
- The Trap: They can become over-invested in making everyone happy, running the risk of losing their technical edge or failing to push back on weak architecture and slow project timelines.
3. The delivery EM (Process-first)
- Core Focus: Process, Execution, & Value Flow.
- What they do: These managers excel at tuning agile workflows, clearing administrative roadblocks (bureaucracy), managing delivery risks, and keeping stakeholders perfectly aligned. They treat technical quality and people management as tools to reduce delivery risks.
- The Trap: They can treat engineers as simple "resources" on a chart, becoming overly rigid with agile metrics while causing team burnout through constant timeline pressure.
4. The product EM
- Core Focus: The "Why" and "What" of the Product.
- What they do: This manager acts almost like a Product Manager. They spend heavy time on market research, building domain knowledge, and setting clear business context for the engineering team. They map business goals directly to engineering capabilities.
- The Trap: They risk overwhelming the team with business demands, neglecting essential internal software quality, refactoring tasks, and technical debt.
Side-by-side comparison matrix
| Archetype | Primary Driver | Primary Strength | Major Weakness / Risk |
|---|---|---|---|
| Tech-Led EM | Code Quality & System Design | High technical authority, great technical mentoring. | Micromanagement; neglecting people management duties. |
| Team Lead EM | Career Growth & Psychological Safety | High team morale, strong retention, trust. | Avoiding tough technical or timeline performance decisions. |
| Delivery EM | Predictable Timelines & Process Flow | Excellent risk mitigation, clears roadblocks fast. | Treating engineers as replaceable units; rigid processes. |
| Product EM | Business Context & Customer Value | Strong alignment between engineering and business. | Neglecting technical debt and long-term codebase health. |
The evolution toward the "Tech-led coach"
Many EMs begin their journey by over-indexing on a single archetype to survive. For example, a new manager might lean heavily on Process/Delivery to ensure they hit immediate deadlines, or over-rely on Tech Leadership because coding feels safe.
However, true maturity in this role means evolving toward a balanced Hybrid Model (The Tech-Led Coach):
- You retain enough technical sharpness to understand architectural bottlenecks and empathize with developers.
- You use that authority to coach the people behind the code, letting them build the solutions while you focus on fixing the system environment.
🎯 Self-Reflection for You
Look honestly at your current calendar and energy allocation:
- Which archetype describes your daily behavior right now? Are you coding, managing tasks, sitting in product alignment meetings, or conducting deep 1:1s?
- What archetype does your engineering team actually need from you at this exact moment to succeed?
Finding your alignment within these archetypes is the key to stopping burnout. If you feel stuck between technical expectations and managerial duties, let's map out your unique leadership profile in a virtual coffee chat.