Senior Director of Engineering / D2 / VP-1 Guide for Tech Companies (2026)

What changes at D2 / VP-1: the executive politics tier

The D2 / VP-1 transition is the fourth and final discontinuity in the engineering management ladder for most modern-tech-company orgs. Above D2 / VP-1 is typically VP-Engineering at companies that have a separate VPE-CTO split, or CTO at companies that combine. Horowitz's The Hard Thing About Hard Things — full book, especially the chapters on senior leadership, hiring executives, layoffs, and politics — is the canonical reading at this tier. Andy Grove's High Output Management generalized to multi-org leadership applies. The structural changes from D1:

• Span typically 200+ people across 2–4 director-led sub-orgs. Some D2s have 1,000+ people for company-wide engineering functions. The unit of analysis is the director and the sub-org strategy, not the engineering strategy of any one sub-org.
• Most of the calendar is C-suite peer partnership and politics. Pragmatic Engineer's coverage of senior-engineering-leadership schedules and Horowitz's chapters on senior leadership confirm: 70%+ of the time is in meetings with peer C-suite leaders (CTO, CPO, CFO, COO), with the CEO occasionally, with peer VP-Engineering / VP-Product, and with the board for company-stage-appropriate scope. Direct people-management with directors underneath is 15–20%.
• Capital allocation becomes a primary lever. The D2 partners with the CFO on engineering capacity, with the CTO on technical strategy and infrastructure investment, and with the VP-Engineering peer functions on cross-org headcount distribution. Decisions about which strategic bets to fund, which to defund, and how much infrastructure to invest in (vs. application work) are made at this tier.
• Executive recruiting is the most leveraged hire. A new director hire shapes the next 2–3 years of an entire sub-org. The D2 spends material calendar time on the director hiring loop, on backchannel references, and on the offer-and-negotiation conversation. Horowitz's chapter on hiring executives is mandatory reading at this tier.
• Strategic conflict and politics surface. Multi-quarter disagreements between engineering and product / design / sales leadership are surfaced at this tier. The D2's craft is forcing the disagreement into writing, naming the alternatives, naming what the cost of each is, and accepting the C-suite's decision once the alternatives are evaluated honestly. Horowitz's framing in The Hard Thing About Hard Things: 'most political fights at the C-suite are about resourcing and priority; the leader who turns them into evaluable written decisions wins; the leader who turns them into personal contests loses.'

The empirical sign you have made the D1-to-D2 transition: the directors underneath you run their sub-orgs without daily input; you spend 70%+ of your time outside engineering with C-suite peer leaders; you have made at least two consequential director hires the company credits as turning points; and you have led at least one strategic-conflict resolution at the C-suite level that produced a written decision. The empirical sign you have not made the transition: you are still functioning as the D1 of one of your sub-orgs while nominally running the rest.

Worked scenario: hiring a new director and resolving a cross-functional strategic conflict, in 9 months

A 9-month worked scenario — senior director of engineering owns 4 directors / 3 sub-orgs (one director is consolidating two sub-orgs after the prior senior-director's exit; total ~280 people). The company is mid-growth-stage. Two parallel challenges in the same period: (1) hiring a new director to take over the 110-person infrastructure sub-org after the prior director left to be a CTO at a startup, and (2) resolving a 6-month cross-functional disagreement between engineering and product about platform-investment-vs-feature-investment ratios.

• Months 1–2 (the hiring sourcing and the strategic conflict surface). The D2 begins backchannel sourcing for the director hire — calls 12 prior managers and peers from their network with explicit asks ('who is the strongest infra director you've worked with in the last 5 years who might be open to a move?'). Three serious candidates emerge over the period. In parallel, the D2 has been hearing from the infrastructure director (now interim, the one consolidating) and the platform M3 underneath that the product team has been pushing hard on feature-velocity for 2 quarters and that platform investment has been suffering. The D2 begins to write a memo.
• Month 3 (the memo and the meeting). The D2 writes a 4-page memo titled 'Engineering capacity allocation 2026: feature vs platform' and sends it to the CTO and CPO before sharing more broadly. The memo is structured as a Rumelt-style strategy document: diagnosis (what is the situation, with platform health metrics and feature-velocity metrics named), guiding policy (what we optimize for), three named alternative allocations with explicit trade-offs, and the D2's recommendation. The memo lands at a regular CTO-CPO-CFO meeting; the conversation is hard but productive — the CPO had been pushing feature-velocity because the CEO had asked for it, but the platform-health data in the memo was new to them. The decision is to shift the allocation 15% back toward platform for the next 2 quarters.
• Months 4–5 (executing the decision and the hiring final round). The D2 communicates the allocation shift to the directors and senior-managers underneath. The platform M3, who had been on the verge of resignation, materially de-escalates. In parallel, the director-hire process advances. Two of the three candidates make it to final rounds. The D2 personally conducts a 90-minute behavioral round with each. Reference calls are extensive — Horowitz's framing: 'check references with people the candidate did not select.' Both candidates have strong references; one has a slightly cleaner re-org track record, the other has stronger cross-functional partnership signal. The D2 picks the one with the cross-functional signal because of the platform-vs-feature dynamic the D2 is currently navigating.
• Months 6–7 (onboarding the new director). The new director joins. The D2 spends the first 60 days at line-manager-level cadence with them — 60-min weekly 1:1, plus pre-reads on the platform-vs-feature memo and the org context. The new director runs their first 1:1s and skip-levels under the D2's guidance. The handoff from the interim director (the one who had been consolidating) is structured: explicit knowledge-transfer document, joint 1:1s for the first month, then a clean handover.
• Months 8–9 (stabilization and the strategic-conflict retrospective). Platform-health metrics improve. Feature-velocity is 8% lower than peak but still above the year-prior baseline; the CPO is content. The new director is operating independently. The D2 writes a retrospective with the CTO and CPO on the platform-vs-feature decision: what worked (the structured-decision-memo format that surfaced the trade-off in writing), what they would change (the issue had been festering for 4 months before the memo; could have been surfaced at month 1). The largest lesson: strategic conflict at the C-suite tier is best resolved by being the leader who writes the structured decision memo first. The leader who escalates verbally without the artifact loses the framing of the decision.

The lesson Horowitz names directly in The Hard Thing About Hard Things and the Pragmatic Engineer's coverage of FAANG senior-leadership echoes: at the senior-director / VP-1 tier, the leader's leverage comes from forcing decisions into writing with named alternatives. Verbal politics is what happens when the writing has not been done; written strategy memos are how the senior-director changes the C-suite conversation.

Executive recruiting: the highest-leverage D2 activity

A new director hire is the most consequential single decision a senior-director makes per quarter. The hiring shapes the next 2–3 years of an entire sub-org. Horowitz's chapter 'How To Hire An Executive' in The Hard Thing About Hard Things is the canonical reading. Larson's 'Hiring senior leaders' on lethain.com extends the framework. The Pragmatic Engineer has covered FAANG executive-recruiting practices in depth (newsletter.pragmaticengineer.com). The mechanics:

1. Sourcing is mostly network, not pipeline. The senior-director typically sources director candidates from their personal network (prior peers, prior reports who have grown, referrals from other C-suite leaders) plus occasional executive recruiter introductions. Cold-application directors are rare at FAANG-tier; they happen more at fast-growth startups. Larson's 'Hiring funnel' coverage extends to senior tiers but funnel volume is low and quality of each candidate is high.
2. Backchannel references are weighted heavily. Horowitz's principle: 'check references with people who have managed the candidate, not the references the candidate selects.' For a director hire, the D2 will typically talk to: (a) one or two of the candidate's prior bosses, (b) 2–3 peers (other directors at the candidate's prior companies), and (c) at least one report (a senior-manager or M3 who has reported to the candidate). The reference calls are 30–45 minutes, structured around 'walk me through a difficult performance situation they handled' and 'what would they say is their biggest growth area.'
3. The interview loop has fewer rounds and more depth. 4–5 90-min behavioral rounds with the C-suite peers and the senior-director. A 'walk me through your last re-org' panel is common. A strategic-thinking round where the candidate reads a 1-page memo and produces a written response is increasingly common at AI-labs. Less code-and-systems-design; more leadership-and-strategic-thinking signal.
4. The offer is a relationship, not a transaction. Horowitz's framing: the offer conversation with a director-tier hire is the start of a multi-year relationship. The senior-director is selling not just the role but the company's direction, the team they will lead, and the senior-director's own commitment to their development. Cookie-cutter offer letters fail at this tier; structured 'here is what we want from you in 6 months, 12 months, 24 months' letters succeed.
5. Failure modes. Hiring the candidate the senior-director knows best from prior context, even when the role calls for a different shape (Horowitz: 'don't hire your friends; hire the right person'). Settling on a candidate because the role has been open too long (the cost of an empty seat is rarely as high as the cost of the wrong seat). Skipping reference calls because the candidate is a known quantity (the most-cited Horowitz mistake — surprises after the hire that came up immediately on reference checks the senior-director skipped).

Compensation: the real bands at senior-director / VP-1

Total comp at D2 / VP-1 FAANG-tier and AI-lab in 2026 (US, per levels.fyi self-reports — heavily caveated because senior-leadership comp has more equity-cycle variance than any other tier and is the noisiest part of the levels.fyi dataset):

Three structural facts at D2 / VP-1 comp:

1. AI-labs sit far above FAANG. Anthropic and OpenAI senior engineering leadership comp at peak-vesting cycles produces the highest reported total comp in the engineering-leadership market in 2026. The risk is private-company equity concentration; the upside is durable.
2. Equity refresh cadence dominates the multi-year picture. A single-year snapshot at this tier is highly misleading. The 4-year stack (initial grant + refreshes + special grants for retention) is the right framing.
3. Negotiation has more dimensions. Beyond cash and equity, D2-tier offers commonly include severance terms, change-of-control vesting acceleration, and explicit role-scope commitments. Horowitz covers this directly in The Hard Thing About Hard Things; the Pragmatic Engineer has reported on FAANG senior-leadership offer structures.