Senior Engineering Manager / M2 (Manager of Managers) Guide for Tech Companies (2026)

What changes at M2: the discontinuity Fournier names

The transition from line-manager (M1) to senior-manager (M2) is the second-largest discontinuity in the EM ladder per the canonical references. Fournier devotes chapter 7 of The Manager's Path entirely to it. Larson's An Elegant Puzzle 'managing managers' chapter and the related lethain.com posts cover the same material. The structural changes:

• Direct line-of-sight to engineering work disappears. At M1 you knew every PR, every design doc, every retrospective on your team. At M2 you have 2–4 line-managers reporting to you, each with their own 5–10 reports. You cannot read every PR. You cannot attend every design review. The temptation is to compensate by going deep into one of the line-managers' areas — that is the senior-manager-as-line-manager-with-extra-headcount failure mode. Larson is explicit: 'managing managers means letting go of being the manager.'
• Your product is your line-managers. The mental shift Fournier describes: at M1 your output is your team's output; at M2 your output is your line-managers' development plus the output of teams you influence (Grove's manager output equation generalized one level up). A senior-manager who promotes one of their line-managers to M2 over 18 months has done their job; a senior-manager who 'ships projects' but whose line-managers are stagnant has failed.
• The 1:1 cadence shifts to skip-levels. At M1: weekly 1:1 with each direct report. At M2: weekly 1:1 with each line-manager (4 hours/week). Skip-level 1:1s with every IC under your line-managers on a 6–12 month rotation (variable hours). Larson's lethain.com 'Skip-level meetings' post is the canonical mechanic.
• Staff-meetings replace standups. A weekly 60–90 minute staff-meeting with your line-managers becomes the team's decision-forcing function. Hogan's Resilient Management chapter on meeting design and Larson's 'Running an effective staff meeting' on lethain.com are the references. The default failure mode is the round-robin status report; the high-leverage pattern is 1–2 named decision items per meeting with pre-reads.
• Cross-functional partnership scales up one level. You are no longer partnering with the PM who runs your team's roadmap; you are partnering with the senior PM (M2's PM peer) who owns the multi-team product area. The conversation shape changes — less feature-level, more multi-quarter-strategy.

The empirical sign you have made the M1-to-M2 transition: when your line-managers run their teams without daily input from you, when they bring you problems already half-solved, and when your skip-level 1:1s confirm the line-managers' read of their teams. The empirical sign you have not made the transition: you are still functioning as the line-manager of one of your sub-teams while nominally managing the others.

Worked scenario: running the budget cycle, in 6 months

A 6-month worked scenario — senior-manager owns 3 sub-teams, 22 ICs total, going into the company's annual headcount and budget planning cycle. The scenario is drawn from Pragmatic Engineer's coverage of FAANG planning cycles, Larson's 'Quarterly planning' on lethain.com, and Stripe's publicly-discussed planning frameworks (Patrick Collison's interviews and the Stripe Press essays).

• Months 1–2 (planning prep). Your director sends the headcount template and the strategic-priority memo for the next 12 months. You spend two weeks reading: every team's last 4 quarters of OKRs, every IC's last 2 perf reviews, every line-manager's quarterly retros. You write a one-page 'state of the org' for your director: top 3 strengths, top 3 risks, top 3 strategic bets. You ask each line-manager to write the same one-pager for their team.
• Month 3 (proposing headcount). Your director gives you a target: 'you can grow from 22 to 25, but you have to justify each hire against the strategic priorities.' You sit with each line-manager and rank-order their hiring asks. You make a hard call: line-manager A wanted 2 hires, line-manager B wanted 3, but the strategic priority memo suggests the work belongs more in line-manager C's area where they wanted 0. You move 1 of A's hires to C. You write the justification memo. You have the hard conversation with A in person before they see the result in writing — a Larson-named pattern: 'no surprises in writing.' A is unhappy but understands the reasoning.
• Month 4 (calibration). Performance calibration cycle. You and your peer senior-managers meet with your director to calibrate ratings across the org. You have to defend your line-managers' ratings of their ICs. The hardest moment: line-manager B has rated one of their ICs as 'meets expectations' when the cross-team data suggests 'partial.' You side with B in the meeting because B has the line-of-sight you don't, but afterwards you have a 1:1 with B asking them to walk you through their reasoning more carefully. B's case turns out to be sound — the IC has been heads-down on a critical infrastructure project that wasn't visible to peers. You learn something about B's judgment.
• Month 5 (announcement). Your director announces the headcount. The team finds out. Line-manager A's IC who had been waiting for that headcount to delegate work to is disappointed. You meet with A and the IC together to acknowledge the disappointment, walk through the reasoning, and re-scope the IC's work. The IC is still unhappy. Two months later they ramp up; six months later they tell you in a 1:1 they appreciated the directness even though they hated the answer. Larson's 'no surprises' pattern again.
• Month 6 (execution and review). The hires start landing. Line-manager C's new hire ramps faster than expected and the team's velocity increases. Line-manager A's reduced headcount forces them to make a tough scope decision they had been avoiding for two quarters. You write the retrospective: what went well, what you would change next cycle. You share it with your line-managers. You realize the hardest part of senior-manager budget work is not the math — it is the interpersonal work of holding firm on a strategic priority when the line-managers all have legitimate reasons to want more headcount.

The lesson Pragmatic Engineer names repeatedly in coverage of FAANG planning cycles: at senior-manager+ the budget cycle is the single most consequential leadership artifact each year. It determines what the team can do, who joins, who leaves, and whether the team's strategy is real or aspirational. New senior-managers who treat budget as a paperwork exercise rather than a strategic act under-perform within their first cycle.

Skip-level 1:1s: the senior-manager craft skill

Skip-level 1:1s are the senior-manager's primary calibration and signal-gathering channel. Larson's lethain.com 'Skip-level meetings' post and Fournier's chapter 7 both treat skip-levels as the load-bearing artifact of the M2 job. The canonical mechanics:

1. Cadence. Every IC under your line-managers gets a skip-level 1:1 every 6–12 months. Senior ICs (E5+) trend longer; new hires and early-career ICs trend shorter. New line-managers — set up the first round of skip-levels with their team in their first 60 days; do not wait. Larson recommends 30 min, in-person where possible.
2. Agenda. The skip-level is the IC's, not yours. Open with: 'this is your time. I have three questions if we run out, but you go first.' The three fallback questions: (1) what is your manager doing well that I should not change? (2) what is one thing you wish your manager would do differently? (3) what is your career goal and is your work today moving you toward it? Hogan's BICEPS frame helps you read the answers.
3. Confidentiality. The skip-level is not gossip. The IC is talking to their manager's boss. You do not relay specific complaints back to the line-manager. You do, however, look for patterns across multiple skip-levels: if 3 of 6 ICs on a sub-team mention the same line-manager weakness independently, that is calibration data. You take that to the line-manager in a 1:1 as your observation, not as 'I heard.'
4. Action. Don't promise to act on individual feedback. Do log patterns and bring them to your line-manager 1:1s. Do escalate if a skip-level surfaces a serious issue (harassment, bias, severe performance problem) — those go through HR immediately, not through the skip-level mechanic.
5. Failure modes. The senior-manager who uses skip-levels to micromanage their line-managers' teams. The senior-manager who treats skip-levels as morale-building chats with no calibration purpose. The senior-manager who promises action on a complaint and either follows through (undermining the line-manager) or doesn't (losing the IC's trust). Charity Majors's charity.wtf has multiple posts on this; the through-line is 'the skip-level is a privileged signal channel, not a problem-solving meeting.'

Compensation: the real bands at senior-manager

Total comp at senior-manager (M2) FAANG-tier and AI-lab in 2026 (US, per levels.fyi self-reports — same caveat about manager-comp noise as line-manager):

The structural facts at senior-manager comp track the line-manager picture, amplified: AI-labs sit further above FAANG, the management premium over senior IC stays small or zero (Meta E7 IC and E7 manager track), and Netflix's single-band model continues to push nominal numbers higher. Pragmatic Engineer's continued coverage of the trimodal compensation framework is the best public reference for negotiating a senior-manager move.