Director of Engineering vs Head of Engineering: 99 Leaders, 63 Titles

Two titles. One job. No honest way to rank them from the words alone.

99 people in our member records lead engineering above the manager line. Between them they hold 63 different job titles.

I have been programming meetups for these people since 2019. Members keep asking for an evening on how to get the director role. It sits in the backlog rated three stars, with a note on it reading “avoid generic advice”, and it has stayed open for two years because I cannot write the abstract. The word director does not tell me who would walk into the room.

What a director of engineering does

A director of engineering is accountable for the output of more than one engineering team, through the managers who run them, rather than for one team directly. Three things fill the week: choosing which problems those teams take on, keeping the managers under them able to run their teams, and defending the budget and headcount that pays for it.

That is the answer to the search you probably typed. It is also, word for word, a description of a Head of Engineering. And of a VP of Engineering at a company one size band down.

So the useful question is not which of the two ranks higher. It is what the rest of the title is doing.

99 people, 63 titles

The first two rows add up to the 99. The other two are here for scale.

Recorded title	People	Distinct strings
Director, engineering or tech	57	35
Head of, engineering or tech	42	28
VP or SVP, any	39	30
CTO	61	13

Read from the 840 member profiles carrying a structured job title in August 2026. Each figure is a headcount, not a percentage. Only a quarter of the community fills that field in, so the real numbers run higher.

The scatter is the story. 54 of those 63 strings belong to exactly one person. The three largest are Director of Engineering with 13 people, Head of Engineering with 8 and Engineering Director with 7.

The words after the title carry the information

52 of the 99 titles are bare. They name no scope beyond engineering itself: Director of Engineering, Engineering Director, Head of Engineering, with a seniority prefix at most. Those people tell you nothing except that someone above them picked a word.

The rest carry a qualifier.

Title	Bare	Carries a qualifier
Director, 57 people	36	21
Head of, 42 people	16	26

Code those qualifiers by what they name and the two words separate.

The qualifier names	Director titles	Head of titles
A business system or area	12	5
A technical craft	5	20
A site or location	2	0

Three qualified titles resisted coding and sit outside the second table.

The director side, verbatim from the records: Director of Retail IT Delivery. Director of Core Banking Systems. Director Company Data Management. Director End User Technologies and Service. Director of IT Operations and Digital Platforms.

The head of side, verbatim: Head of QA. Head of SRE. Head of Firmware Development. Head of Platform Engineering. Head of Mobile. Head of Data Science.

Read those two lists aloud and seniority stops being the difference. The director titles name something the business sells, runs or reports on. The head of titles name something engineers do. A Director of Retail IT Delivery is accountable for retail IT arriving. A Head of QA is accountable for a capability existing and being good at it.

I coded those qualifiers by hand, alone, and another coder would move two or three of them. The direction is bigger than the wobble, which is why I am willing to build on it.

The title tells you which vocabulary your company speaks. The words after it tell you what you are on the hook for.

Why the salary pages disagree by 2.2x

Page one of that same search reports $139,450 at Indeed and $309,867 at Glassdoor for one job title. Nobody on that page explains the gap.

Some of it is method: those two sites survey different populations and count total compensation differently. The census adds the part they leave out. A bare Director of Engineering, a Director of Retail IT Delivery and the person James Stanier describes running a division of 250 people all report the same string, so any average over it blends jobs that are not the same job.

Which is why quoting a salary survey at your own company is a weak move, and quoting the scope is a strong one. These are US figures against a CEE readership, so treat the spread as the transferable part, not the numbers.

VP is not always a rung

39 people in the base carry VP or SVP, and 14 of those titles name a business desk with no engineering or product noun in them. VP Cash Equities Equity Derivatives. VP Rates Options Intraday. VP Risk Finance Treasury.

Two go further: VP, Frontend Developer and VP, Lead Developer, UI UX Expert are individual contributor jobs with VP in front of them. That is two strings out of 39, so take it as a symptom rather than a rule.

What it points at is documented. In investment banking, Vice President is a mid career grade and the rung above it is Director, called Senior VP or Executive Director at some banks. Wall Street Prep publishes the ladder in that order. Mergers and Inquisitions puts ages against it: VP at 28 to 40, the rung above at 32 to 45.

In a US product company those same two words run the other way round. Both kinds of employer hire engineers in Prague and Bratislava, and their people sit in the same row at the same meetup. Ranking two offers by title alone is a coin flip.

It also means the VP rung is a strange thing to wait for. There are 61 CTOs in this same base and 23 VPs with an engineering scope, which is why the VP step is the one to stop waiting for if the seat you want is the top one.

Where the titles come from

This region runs on delivery centres owned from somewhere else. ABSL counts 380 business services centres in the Czech Republic employing 200,000 people in 2025, and reports that 80% of them operate as internal captive units, serving their own parent group rather than external clients.

A captive centre inherits its job architecture from a headquarters that designed it for a different org. That is the structural reason the strings scatter. 63 titles across 99 people is not carelessness. It is 63 companies each exporting a vocabulary into the same four cities.

It also explains the qualifiers. A group that opened a Prague site to own retail IT delivery writes a title saying retail IT delivery. A company that hired one person to make testing work writes Head of QA. Neither is thinking about how the string will read to a recruiter in two years. Two director titles in the base end in Site Lead, which is a delivery centre writing its place in a global org chart straight into somebody’s job.

Four questions that decode an offer

Ask these in an interview, or about the job you already hold. The first one is the one this census earns and the one the standard advice does not contain.

What is the qualifier for, and who wrote it? If the offered title is Head of or Director of Something, ask what that something is scoped to and who chose the words. A craft qualifier and a business area qualifier describe different jobs, and in these records they split cleanly between the two titles. If the person hiring you cannot say who wrote the string or what it was meant to cover, you are being handed a grid entry rather than a job.

How many management layers sit below you? Stanier’s range is the calibration: a director at a medium sized company “may have a few small teams reporting to them, but in the biggest companies that same job title may entail running a division of 250 people.” Same string, two different jobs. Compare your own org shape against this community in the leadership ratio benchmark rather than against a US industry report.

Does the roadmap arrive, or do you set it? A director who receives the roadmap and a director who writes it share a title and share little else. This is the whole argument of the previous post.

Who signs off headcount? If the answer is a person you have met, you hold authority. If it is a committee three timezones away that you submit to once a year, you hold a case to make, and a title that will not help you make it. The tell to listen for is site: the two titles in the census ending in Site Lead belong to people running a location for an owner somewhere else, and that arrangement usually decides headcount before you are in the room.

Two offers, one Head of Engineering and one Director of Engineering, and no honest way to rank them from the strings. Run all four questions against both, in writing, before you sign.

The strongest objection

Levelling frameworks exist. Inside one large company the ladder is usually consistent, documented and tied to compensation bands. Anyone working somewhere with a real framework will read this and say that “titles are meaningless” is a lazy take. They are right about their own building.

The catch is that the framework stops at the company boundary, and that boundary is exactly where a job search, a recruiter conversation and a peer comparison at a meetup happen. 63 strings across 99 people is what the outside of those buildings looks like.

Credit where it is due. LeadDev’s guide to the role, which currently outranks everyone on this search, concedes the same thing: jobs with the same title “can vary widely from company to company, or even across groups within the same company.” We disagree about how much that matters, not about whether it is true.

Engineering has run this argument once already, one ladder over. Meetup #18 was The Real Role of Staff and Principal Developers, booked because the same confusion had built up on the IC side and a room wanted it settled. The management ladder has not had its version of that evening yet.

If head of engineering is the title you are weighing, I have written separately about where it sits and what it signals about company stage.

Where people work this out

The fastest way to calibrate a title is to stand next to 40 people holding variations of it and compare the jobs underneath. That is what the meetups are, 12 a year across Prague, Brno, Bratislava and Kraków. It is also the cheapest first move when the question is your own next step rather than the title, which is why the room comes before a coach.

If you hold one of these titles, here is what I would like to know and cannot count. Of the 36 people carrying a bare director string, how many chose it and how many were handed it? The records cannot tell me. Come and argue about it, and I will write the meetup abstract I have owed the backlog for two years.

How I counted

The base. Titles come from the structured job title field on our own member records, with no fallback to the profile headline. 840 of the records carry one. The member list held 3,193 records when I ran the query on 11 August 2026; the published community figure is 3,184, which is the nightly count, and the gap is a day of joins.

Why 99 here and 173 in What Is Engineering Leadership? Same community, two rulers.

	Base	Counts	Result
Post one	1,263 profiles, job title or LinkedIn headline	Director and head of, any domain	173
This post	840 profiles, structured job title only	Director and head of, engineering or tech only	99

The bare and qualified split. Done by regex, then checked by eye. A title counts as bare if it names no scope past engineering, software engineering, development or technology, allowing a seniority prefix. Three qualified titles are uncoded: one is a profile headline rather than a job, one is bare in substance with a seniority prefix the pattern missed, and one is a dual title carrying no scope.

The qualifier coding. By hand, by me, one bucket per title, with no second coder and no inter rater check. The calls I would defend but not insist on: Head of Product Development coded as business, Director of Architecture coded as craft, Head of Technical Programs coded as craft. 19 and 25 coded titles is a small sample, and twenty new members could move it by several points.

The banking read. That VP means a mid career grade rather than an engineering rung in a slice of these companies is my inference from the shape of the strings, not from anyone’s HR documentation. The banking ladder itself is sourced above. There is also no rigorous public study of span of control broken out at director level, which is why Stanier’s published range stands in for one.

The ABSL figures. They count the whole business services sector, which is mostly finance, HR and procurement operations with IT and R&D as a slice, so they are evidence about ownership structure rather than a headcount of engineers. ABSL publishes the 80% captive split but does not publish a share foreign owned figure, so I have not claimed one.

Self reported. These are titles members wrote about themselves, not extracts from payroll. A share of them are aspirational, a share are stale, and two are written in Czech and English at once.