Career Hub

Engineering Manager Hub: Land, Level Up, and Lead at Tech Companies in 2026

By Blake Crosley · Last verified

In short

Becoming an engineering manager at a tech company in 2026 means proving three things: that you can develop people (1:1s, performance conversations, sponsorship, hiring), that you can ship through a team (scope, prioritization, technical judgment exercised through others), and that you can partner credibly with PM, design, and cross-functional engineering. The ladder runs from line-manager (M1, 5–10 reports) through senior-manager (M2, manager of managers, 15–40 reports) and group-engineering-manager (M3, 40–80) into director (D1, 80–200) and senior-director / VP-1 (D2, 200+). The reference texts are Camille Fournier's The Manager's Path and Will Larson's An Elegant Puzzle; the working voice is Charity Majors at charity.wtf and Will Larson at lethargicem.com. This hub covers every level, the companies hiring, and the management craft that compounds.

Key takeaways

  • Senior-manager (M2) total comp at FAANG-tier clusters $600,000–$900,000 at Meta E7 / Google L7 with stock vesting; director (D1, Meta E8 / Google L8) commonly clears $900,000–$1.4M; senior-director / VP-1 commonly $1.2M–$2M+ (levels.fyi 2026 self-reports).1
  • The IC-to-EM transition is the largest career discontinuity Camille Fournier names. The Manager's Path (O'Reilly, 2017) chapter 4 ('The Tech Lead') and chapter 5 ('Managing People') frame the transition as a separate craft — not a promotion of the IC job. The most-cited prep reading on the modern web.2
  • Charity Majors's "Engineer/Manager Pendulum" reframes the path as cyclical, not unidirectional. Strong technologists can move between IC and EM tracks across a career; the modern frame is leverage and energy fit, not a one-way ladder. The post (charity.wtf, 2017) is the canonical short-form reference; Larson concurs in An Elegant Puzzle.3
  • Managing managers (M2 / senior-manager) is the second-largest discontinuity. Fournier's chapter 7 ('Managing Managers') and Larson's An Elegant Puzzle ('Managing managers') both name skip-level 1:1s, hiring-and-leveling-managers, and staff-meeting-as-decision-forum as the new craft skills. Direct line-of-sight is gone; you grade your line-managers' judgment, not the team's code.4
  • Andy Grove's High Output Management is the canonical pre-software management text Stripe, Anthropic, and Pragmatic Engineer's career-resource lists all reference. Task-relevant maturity (Grove's framework: how 'directive vs delegating' should depend on the task, not the person) and the Manager's Output Equation (output = output of your team + output of teams you influence) are the two most-cited frames.5
  • Lara Hogan's feedback equation is the most-shared single artifact in modern engineering management. 'Observation + impact + question or request' (Resilient Management, A Book Apart, 2019) is the structure. The BICEPS core needs framework (Belonging / Improvement / Choice / Equality / Predictability / Significance) is the canonical 1:1 / performance-conversation diagnostic.6
  • Engineering management hiring tightened materially 2022–2024. Public layoff data (layoffs.fyi) and Pragmatic Engineer's coverage of FAANG layoffs document above-average reductions in middle management at Meta, Google, Microsoft, and Salesforce. AI-labs (Anthropic, OpenAI) are the counterbalance with aggressive engineering-leadership hiring at frontier-lab compensation. Strong, well-articulated track records are the entry signal.7

Land your first EM role

Most engineering managers come from senior IC (5–8+ years) inside the same company — promoted into a tech-lead-manager hybrid first, then converted to a clean line-manager job once a manager opens up. Camille Fournier's The Manager's Path (chapter 3 'Tech Lead' through chapter 5 'Managing People') is the canonical preparation. External line-manager hires happen, but the bar is strictly higher: companies want a track record of named-and-sourced shipped scope, named-and-sourced people development, and the willingness to discuss specific 1:1, performance, and hiring situations under pressure. Total comp at line-manager (M1 / Meta E5 manager / Google L5 manager) clusters $350,000–$520,000 in the US per levels.fyi 2026; AI-labs (Anthropic, OpenAI) sit materially above this on heavy private-company equity.1

Make senior-manager (manager of managers)

Senior-manager (M2 / Meta E7 / Google L7) is where the line-manager job becomes manager-of-managers — Fournier's chapter 7 and Larson's An Elegant Puzzle 'managing managers' chapter both name this as the second-largest discontinuity after IC-to-EM. The new craft skills: skip-level 1:1s as a calibration and signal-gathering channel, hiring and leveling line-managers (a different rubric than hiring engineers), running staff-meetings as decision-forcing-functions, holding line-managers accountable for performance management of their teams without micromanaging the people two levels down. Senior- manager total comp at FAANG-tier in the US in 2026 self-reports cluster $600,000–$900,000 at Meta E7 / Google L7 on levels.fyi; AI-labs (Anthropic, OpenAI senior engineering manager / director of engineering) commonly clear $1M+ on equity-heavy total comp.1

Get to director and senior-director / VP-1

Director (D1 / Meta E8 / Google L8) and senior-director / VP-1 (D2) is where engineering management transitions from craft to executive function. Director scope is typically 80–200 people across multiple product surfaces; senior-director / VP-1 is 200+ and partners directly with C-suite peers (CTO, CPO, CFO). The work is org design (Charity Majors's 'sociotechnical org design' framing on charity.wtf and Larson's chapter 'organizational design' in An Elegant Puzzle), strategy articulation (Larson's Good Strategy / Bad Strategy reading list), executive-level hiring (recruiting senior managers and directors from outside the company), and re-org execution. Total comp at director clusters $900,000–$1.4M with stock vesting per levels.fyi; senior-director / VP-1 commonly clears $1.2M–$2M+ at FAANG-tier and exceeds this materially at AI-labs.1

Targeting specific companies

Each company page covers what's verifiably published about engineering management at the company: how levels map to titles, what's known about the interview process, compensation data from levels.fyi, and the org / culture artifacts the company has chosen to share publicly (Netflix's culture deck, Stripe Press's books and engineering blog, Pragmatic Engineer's reporting on Meta's perf-cycle, Google's published leveling rubric via Hello Interview). Where companies don't publish their internal rubrics, we note that and stick to what's externally verifiable rather than fabricate authority. AI-labs (Anthropic) sit at the top of the comp market in 2026; FAANG (Meta, Google, Netflix) and developer-platform companies (Stripe, Linear, Databricks, Airbnb) round out the canonical EM hiring landscape.

Deep skills that matter in 2026

The EM craft compounds across decades, but six skill areas come up across nearly every senior-manager+ promotion case: the IC-to-EM transition (the foundational discontinuity Fournier names), managing managers (the M2 transition, where direct line-of-sight ends), performance and feedback (Hogan's equation, Larson's 'Useful PiP' essay, Grove's task-relevant maturity), hiring and leveling (the single most leveraged manager activity, per Larson and Fournier both), strategy and roadmapping (Rumelt's Good Strategy / Bad Strategy applied to engineering — the chapter is in An Elegant Puzzle), and managing up and cross-functional (the director+ reality, where 60%+ of the calendar is partnership not direct-team). The canonical reading list, in priority order: Fournier (Manager's Path), Larson (An Elegant Puzzle, StaffEng), Hogan (Resilient Management), Grove (High Output Management), Charity Majors (charity.wtf), Rands in Repose (Lopp's Managing Humans), Pragmatic Engineer (Orosz, pragmaticengineer.com).

Frequently asked questions

What does an engineering manager at a tech company actually do?
An engineering manager owns the team, not the codebase. The job is people, hiring, performance, scope, prioritization, cross-functional partnership, and the calendar. At line-manager (M1) the team is 5-10 reports and the manager still touches code occasionally; at senior-manager (M2, manager of managers) the team is 15-40 across 2-4 sub-teams and the calendar is fully managerial; at director (D1) it is 80-200 and the work is org design, strategy, and partnership with VPs. The reference texts are Camille Fournier's The Manager's Path and Will Larson's An Elegant Puzzle.
How long does it take to become an engineering manager?
The most common path is senior IC (5-8 years post-graduation) into line-manager (M1) via tech-lead or tech-lead-manager apprenticeship. Camille Fournier's The Manager's Path frames the canonical progression: IC -> tech lead -> manager. Some engineers move into management at 4-5 years; some never do. Will Larson's StaffEng is the alternative read for engineers who want the senior IC track instead. Time-to-director is 8-15 years from line-manager; time-to-VP is rarely under 12-15 years total industry experience.
What is total comp for an engineering manager at FAANG?
Per levels.fyi 2026 self-reports, US senior-manager (M2, Meta E7 / Google L7 / equivalent) total comp clusters $600,000-$900,000 with stock vesting; director (D1, Meta E8 / Google L8) commonly clears $900,000-$1.4M; senior-director / VP-1 commonly $1.2M-$2M+. Anthropic and OpenAI engineering-leadership total comp materially exceeds FAANG at senior-manager+ on heavy private-company equity. Cash-vs-equity mix and four-year refresh-grant cadence dominate the actual take-home; a single-year snapshot is misleading.
Should I become an engineering manager or stay an IC?
Different jobs, not different levels of the same job. Charity Majors's 'The Engineer/Manager Pendulum' (charity.wtf, 2017) is the canonical framing: many strong technologists move between IC and EM across a career. The wrong reasons to switch: 'I'll have more impact' (false at most companies — staff/principal IC scope is comparable), 'I'm tired of coding' (you'll be even more tired of meetings), 'I want to be promoted' (the EM ladder is not faster). The right reasons: you genuinely care about the people problem, you find calendar/coordination work energizing, you're willing to give up the daily flow of code to gain leverage through others.
How is managing managers different from managing engineers?
The transition from M1 (managing engineers) to M2 (manager of managers) is the largest discontinuity in the EM ladder per Fournier (The Manager's Path, chapter 7) and Larson (An Elegant Puzzle, 'managing managers' chapter). At M1 you have direct line-of-sight into every project; at M2 you are dependent on your line-managers' judgment. The new craft skills: skip-level 1:1s as calibration channel, hiring and leveling line-managers (different rubric than engineers), running staff-meetings as decision-forcing-functions not status-readouts, holding line-managers accountable for performance management of their teams without micromanaging.
What frameworks should every new engineering manager read?
Five canonical references: (1) Camille Fournier, The Manager's Path (O'Reilly, 2017) — the spine of the field. (2) Will Larson, An Elegant Puzzle (Stripe Press, 2019) — systems thinking applied to engineering organizations. (3) Lara Hogan, Resilient Management (A Book Apart, 2019) — feedback equation, BICEPS, manager-of-managers craft. (4) Andy Grove, High Output Management (Vintage, 1983) — task-relevant maturity, output equation, the canonical pre-software management text Anthropic and Stripe employees commonly reference. (5) Charity Majors, charity.wtf — the working-engineering-leader voice. Bonus: Rands in Repose (Michael Lopp) for tactical patterns, Pragmatic Engineer (Gergely Orosz) for the modern-tech-company landscape.
How important is technical depth for an engineering manager?
Required at line-manager and senior-manager; less daily at director+. Charity Majors's framing: an EM who has lost the ability to read their team's PRs cannot effectively review them, defend their team's technical decisions in cross-functional, or hire credibly. The line-manager job is partly tech-lead — Fournier devotes a chapter to the tech-lead-manager hybrid. By director, technical depth is exercised through judgment about staff/principal engineers' proposals, not direct code review. The dangerous failure mode: an EM who hides from technical depth and becomes a project manager. The other failure mode: an EM who refuses to delegate technical decisions and bottlenecks the team.
Is the EM job market tighter in 2026 than in 2022?
Mixed. Public layoff data (layoffs.fyi 2022-2025) shows engineering management was disproportionately affected in 2022-2024 reductions at Meta, Google, Microsoft, and Salesforce — flatter org structures became a stated goal at multiple FAANG-tier companies. Senior-manager+ hiring is more selective in 2026 than the 2021-2022 peak; AI-labs (Anthropic, OpenAI) are aggressively hiring engineering leadership at frontier-lab compensation. The pattern: strong line-manager track records with named-and-sourced shipped scope, named-and-sourced people development, and named cross-functional partnership track record are the dominant signals at the senior-manager+ market entry.

Sources

  1. levels.fyi — Engineering Manager Compensation (FAANG, Stripe, Airbnb, Anthropic compare, 2026). Self-reported total compensation by EM level across FAANG-tier and AI-lab companies; Anthropic and senior-director / VP-1 totals materially exceed the median.
  2. Camille Fournier — The Manager's Path (O'Reilly, 2017). Chapters 3 (Tech Lead), 4 (Managing People), 5 (Managing a Team), 7 (Managing Managers) are canonical preparation for every EM transition.
  3. Charity Majors — 'The Engineer/Manager Pendulum' (charity.wtf, 2017). The canonical short-form reframing of EM as cyclical, not unidirectional.
  4. Will Larson — An Elegant Puzzle (Stripe Press, 2019). Systems thinking for engineering organizations. The 'managing managers' and 'organizational design' chapters are the senior-manager / director reference.
  5. Andy Grove — High Output Management (Vintage, 1983). Task-relevant maturity, the manager's output equation; the canonical pre-software management reference.
  6. Lara Hogan — Resilient Management (A Book Apart, 2019). The feedback equation (observation + impact + question/request) and the BICEPS core-needs framework.
  7. Gergely Orosz — The Pragmatic Engineer. Modern-tech-company engineering-management landscape coverage; reporting on FAANG perf cycles, layoffs (layoffs.fyi cross-reference), and engineering-leadership hiring.
  8. Michael Lopp — Rands in Repose / Managing Humans. The original engineering-management blog (running since 2002); chapters and posts on tactical patterns (1:1 mechanics, 'shields up', engineer archetypes).

Resources for engineering managers

  • Engineering Manager Job Description Reference — BLS Computer and Information Systems Managers career-info anchor: duties, skills, salary ($171,200 median), work environment, 15% projected growth.
  • Engineering Manager ATS Keywords — what tech-company hiring teams scan for in EM resumes: leadership scope, hiring evidence, OKRs, roadmap, cross-functional partnership — and the IC verbs that backfire.
  • Engineering Manager ATS Checklist — 22-item pre-submission checklist for EM resumes: format, scope numbers, hiring signal, EM-vs-IC framing, and verification.
  • Software Engineer — the IC track. Read this to remember what your reports are scored on.
  • Data Scientist / ML Engineer — the DS / ML org structure differs from SWE; useful when you manage a hybrid team.
  • Product Manager — your closest non-eng partner. The cross-functional dance lives here.
  • Product Designer — your design partner; read what they're scoring on so the trade-off conversations stay short.
  • iOS Engineer — if you manage a native iOS team, the platform-specific reality lives here.
  • Design Manager — the design-org peer. Same management-track mechanics, different IC discipline.
  • Frontend Engineer — the SWE specialization that increasingly hires distinctly at modern tech companies. Useful when you manage frontend or hybrid teams.
  • Backend Engineer — most EM track ladders run through senior backend before management. Read for context on what your senior+ backend reports are scored on.
  • UX Researcher — the evidence partner for engineering decisions. EMs who partner well with UXR ship better products faster.
  • Data Engineer — DE management is a tangent track many EMs end up on; data-platform EM is its own sub-discipline.
  • Android Engineer — many EMs manage hybrid iOS/Android teams; understanding the Android stack is required.
  • DevOps / SRE Engineer — many EM tracks include SRE management; reliability culture is a load-bearing piece of senior engineering leadership.
  • Security Engineer — security-engineering management is its own EM sub-track at scale. Vulnerability-management cadence, audit readiness (SOC 2, ISO 27001), and security-incident response are EM-load-bearing concerns.