An engineering director is the leader who runs a group of teams through their engineering managers. Many companies write the title as director of engineering. It’s the layer between a single team and the whole org, which is where most of the actual scaling happens and where most of the career pain lives.
It’s the first role where you manage managers, and that single change breaks more strong EMs than any other step on the ladder. Which is why the title deserves its own guide rather than a paragraph inside a VPE post.
Directors and their equivalents, the mid-level leaders, are 23% of my mentee mix across 3,662 1:1 leadership sessions with 317 engineering leaders since 2019. Before mentoring I created this exact layer from scratch at Mews, growing the engineering org from 8 to 80 through Series C.
What an engineering director owns
- Delivery across teams. Each EM owns their team’s output. The director owns the sum, including the cross-team dependencies no single EM can resolve. Some orgs hire a technical program manager to track them, but the director still owns the result.
- The managers. Hiring EMs, growing them, and acting when one isn’t working out. Your calendar shifts from code reviews to career conversations.
- Org design inside the area. When to split a team, when to merge two, where the next manager comes from. Decisions with two-quarter feedback loops.
- Priorities and trade-offs. Product wants everything, platform wants stability, and the director arbitrates without escalating every fight upward.
- The standard. Quality bar, incident discipline, planning hygiene. Whatever the director tolerates becomes the culture of their group.
Director vs the roles around it
| Engineering Manager | Engineering Director | VP of Engineering | |
|---|---|---|---|
| Also titled | Software engineering manager | Director of engineering, director of software engineering | VPE, VP Engineering |
| Manages | Engineers | Engineering managers | Directors, the whole org |
| Horizon | Sprint to quarter | Quarter to year | Year plus |
| Closest to | The code and the people | The system between the teams | The business |
| Day dominated by | 1:1s, delivery, unblocking | Cross-team priorities, growing managers | Exec alignment, org strategy, hiring |
| Breaks when | The team gets overloaded | Managing through others doesn’t stick | Translation to the exec team fails |
The table leaves out two things. In practice, in a 40-person org “director” and “VPE” are often one job under two names, title inflation is real and mostly harmless. And the “manages managers” row carries most of the meaning, the rest of the table is detail around it.
What director of engineering job descriptions ask for
The list above is how I see the seat. Job ads describe it in their own words, so here is what ten director of engineering postings from autumn 2026 ask for, nine of them still open on 9 October 2026 and one (n8n) closed in August.
- Managing managers. Eight of the ten say it outright, and Datadog calls it non-negotiable. The scope behind it varies a lot: three engineering managers at GitLab, about 40 engineers and managers at Elastic, 50 to 60 engineers at Datadog.
- Technical direction for an area. A roadmap and the architecture calls for a group of teams, not for the whole company. Datadog wants the director to shape the product roadmap “rather than simply executing against it”.
- Hiring, org design and performance. Hiring plans, team structure, promotions, and in Elastic’s words “managing underperformance through to resolution”. TTEC Digital says you personally own the hiring funnel and the bar.
- Incidents. Four of the ten put production incidents on the director’s plate, and Datadog puts the director on the on-call rotation.
- AI adoption. Half of the ads now carry it, from driving AI tooling across the org (Datadog, solidcore, TTEC Digital) to expecting AI in everyone’s daily workflow (GitLab).
Budget shows up in only one of them: GitLab’s director manages the database infrastructure budget together with FinOps.
The US ads that publish pay put base salary between $185,000 at solidcore and $345,000 at Robinhood, and Elastic goes up to $379,300 in its most expensive metros. That’s base only, equity comes on top. The European ads in the sample, Monzo, Datadog Paris and n8n, publish no range at all.
Three lines in these ads are worth a question in the interview:
- On-call. If the director carries a pager, ask how often, and whether you are the backup or the first page.
- Hands-on. Fullscript wants a “strategic and hands-on leader”, TTEC Digital wants someone who reads Go, Python and TypeScript well enough to call out architecture in review, and ZenBusiness warns against the director turning into the team’s day-to-day solution architect. Ask how many hours a week in the code the hiring manager expects.
- Influence without authority. Monzo asks you to influence outcomes “across teams that do not directly report to you”. That’s accountability for results you can’t order. Ask which decisions are yours and get the answer in writing before you sign.
Why the transition breaks people
The skills that got you the job are the ones you now have to drop. As an EM you were close to the work: you saw the PRs, you knew every person, you could fix things directly. As a director, fixing things directly is the anti-pattern, every reach past an EM into their team weakens the manager you’re supposed to be growing.

The failure mode I see most in sessions: a new director keeps operating as a super-EM for two quarters. Their old team is happy, the other teams drift, and the EMs learn that real decisions happen without them. By the time delivery slips, the habit is already set.
What helps? Moving your attention from the work to the system: weekly 1:1s with every EM that are about them rather than status, written priorities, and letting a visible mistake happen when the lesson is worth more than the cost.
This transition is one of the most common reasons leaders book mentoring with me. The concepts aren’t hard, doing this under delivery pressure with your old team watching is.
Related roles
- VP of Engineering: what the role owns, vs CTO
- How to Become a VP of Engineering: The Three Gaps
- Should you take the VP of Engineering job, and what to negotiate first
- Head of Engineering: what the title means
- Team Lead: the role, vs tech lead, vs engineering manager
- What a Staff Engineer role is all about
- AI engineering manager: the 2027 career fork



