RecruitLingo

What the level actually means — scope, blast radius, and how to tell.

Director of Engineering

Also seen as: Head of Engineering, Engineering Director, D1, VP Engineering (at smaller companies)

Scope

A function, a business line, or an entire engineering org at a smaller company. Sets direction, owns budget and headcount, and answers for outcomes rather than for delivery.

Blast radius

Organisational and financial. Hiring plans, structure, technical strategy and culture all sit here, and all of them take a year or more to correct.

Autonomy

Operates from business goals. Frequently the person deciding what engineering does not do.

With other people

Works through managers and senior ICs. Peer to Product and Design leadership; regularly in front of the exec team or the board.

Resume tells

  • Owned a budget and a headcount plan, with numbers attached
  • Hired and developed managers, not just engineers
  • Made a structural or strategic call — a platform investment, a rebuild, a decision to stop something — and can say what it cost
  • Evidence of operating with the exec team or the board
  • Can describe a period where the org shrank as well as one where it grew

Title inflation risk

The most title-inflated rung in the whole ladder, in both directions. 'Head of Engineering' at a 15-person startup is often a senior IC with a title and no reports; 'VP Engineering' at seed stage can mean first engineering hire. Meanwhile a Director at a large company may own more people than a startup CTO. The title is close to meaningless without headcount and budget attached.

Calibration questions

  • “How many people were in your organisation, and what was the budget you owned?”
  • “What did you decide engineering would stop doing, and how did that land?”
  • “Tell me about a time you had to reduce the team. How did you decide, and what did you learn?”
  • “Which of your managers did you hire, and how did you assess them?”

Where this goes wrong

Screened on years or title rather than on scale of organisation. A Director from a 400-person company and a 'Head of Engineering' from a 20-person one may both be right for a role, or neither — headcount, budget and layers tell you, and the title does not.

Years of experience: 10+ years is typical, but at this level the relevant history is what they've been trusted to own, and the failures they can describe honestly.

Where was the title earned?

The same title means different things at different companies. Apply this before believing the level on a resume.

Seed / early startup (under ~50 people)

Titles are recruiting currency and cost nothing to give. 'Senior' often means 'third engineer hired'. Scope can genuinely be large — they may have built whole systems alone — but calibration against a wider bar has never happened.

“How many engineers were at the company when you joined, and when you left?”

Growth-stage (~50-500 people)

The ladder is usually being invented while people are on it. Titles are often regularised in a single re-levelling event, so the same person can be Mid one quarter and Senior the next without the job changing.

“Was there a re-levelling or a formal promotion process, and where did you land in it?”

Large tech company with a calibrated ladder

Titles mean something specific and were defended in a promotion committee. A Senior here has been measured against a written bar. This is the most reliable title signal you'll get — and the reason level codes (L5, IC3) are worth asking for.

“What level were you at, in your company's internal terms, and when were you last promoted?”

Agency, consultancy or outsourcing firm

Titles are often client-facing and inflate to justify billing rates. Scope tends to be broad but shallow — many projects, rarely owning anything after handover. The 'operate it after launch' evidence that separates Senior from Mid is frequently missing, through no fault of theirs.

“Which of those projects did you stay on after go-live, and what did you have to fix?”

Non-tech company (bank, retailer, manufacturer, public sector)

Ladders are often HR-wide rather than engineering-specific, and titles can be tied to tenure or grade rather than scope. Deep domain expertise is common; exposure to modern tooling and fast release cycles may not be.

“How often did your team release, and who decided when something shipped?”

The levels either side

Individual contributor track

Management track

Open the full tool for the glossary, role profiles, and the JD decoder.