Why an executive title does not travel between company types
Engineering titles are local currency, and the exchange rate varies most at the top, because each company's levelling framework was built for its own size and shape. The same words describe very different jobs depending on company size and ownership, so treat the table below as a set of questions rather than a mapping.
| Company type | What a VP or Director title can mean there | What to check |
|---|
| Early startup | VP may be the top engineering role, reporting to the CEO, with a small team | Whether a CTO sits above you, or will be hired above you |
| Scale-up | VP over several directors, often hired just ahead of rapid growth | Whether the role is sized for today's organisation or next year's |
| Listed enterprise | Director may run a larger group than a startup VP, several layers below the CEO | Decision rights and budget sign-off, which shrink as layers grow |
| Private-equity owned | Titles tied to a value-creation plan with a fixed horizon | Who sets your targets, and what happens to the role at exit |
| Captive or capability centre | A site "Head of" can report into a global function, sometimes with dual reporting | Whether you own outcomes or only the people delivering them |
The consequence cuts both ways. A Director offer from a large company can be a bigger job than your current VP role. A VP offer from a forty-person startup can be smaller than the Director role you are leaving. Neither title tells you which.
The scope audit, with a worked comparison
Ask for the information directly, and ask early. A sample phrasing:
"Before I think about the title, can you walk me through the charter? Who would I report to, what budget would I own outright, which decisions need sign-off above me, and which leadership meetings would I be in?"
Then lay the two roles side by side. Suppose you are VP Engineering at a Series B company with 70 engineers, reporting to the CEO, owning the engineering budget, and sitting on the executive team. The offer is Director of Engineering at a listed company: 180 engineers across four groups, reporting to a VP who reports to the CTO, with budget held jointly with a finance partner.
| Dimension | Current VP role | Offered Director role |
|---|
| People led | 70 | 180, about 2.6 times as many |
| Layers to the CEO | 0 | 2 |
| Budget | Own it | Co-own it with finance |
| Architecture and vendor decisions | Final say | Final say up to a threshold, then escalate |
| Leadership forum | Executive team | Engineering leadership, not the executive team |
Reading the table honestly, the offered role is larger in people and smaller in authority. Whether that is a step down depends on what you want next. If your goal is a CTO seat at a large company, running 180 people inside a mature operating model may be the missing evidence. If your goal is the CTO seat at a startup, losing executive-team membership is the real cost, and the title is a symptom of it.
How the title reads to the next employer
The title lands on your CV and in a search firm's shortlist, and some screens filter by it. That cost is real, but it is smaller than the cost of a scope reduction, and you can partly offset it. Describe roles by charter rather than by title: "Led 180 engineers across four product groups, owned platform architecture decisions" carries the scope a title cannot.
Be honest that the market also discounts in the other direction. Some large-company recruiters already read a small-company VP title as roughly a director-level role, so the Director offer may not move how you are read at all. You cannot verify this precisely, so do not overweight it in either direction.
What to negotiate, in order
Negotiate in this order, because each item is harder to move once the previous one has been fixed.
- The charter, in writing. Scope, headcount, budget authority and decision rights belong in the offer or a written role description. A verbal "you will own platform" disappears with the first reorganisation.
- The reporting line. Who you report to matters more than the label. Reporting to the CTO as a Director can outrank reporting to a VP as a Senior Director.
- A dated title review. Agree a specific review point and the criteria for it. A promise of promotion "soon" is worth nothing at this level.
- The title variant. Some job architectures have a step between Director and VP, and some separate an external title from an internal grade. Ask; do not assume either exists.
- Pay inside the band. Argue the position in the band from the scope you have just documented.
Executive offers also carry terms that junior offers rarely do: severance, notice length, restrictive covenants, equity vesting and acceleration, and change-of-control provisions. Enforceability and norms vary sharply by country, so have an employment lawyer in the relevant jurisdiction read them. Do not negotiate them from memory.
Winning the title and losing the charter
Strong and adequate answers part company here. The adequate candidate spends negotiating capital on the word on the business card. A candidate who argues the executive title up to VP and accepts an undefined scope has won a label and lost the job. The strong answer audits scope first, puts the charter in writing, and then decides whether the title gap is worth a fight.
The same applies when the interviewer asks it directly ("Would you be comfortable coming in as a Director?"). The panel is reading for ego and for judgement. A good reply names the scope question rather than the title:
"The title matters less to me than the charter. If the role owns the platform decisions and the budget we discussed, I am comfortable with the title. If it does not, that is the conversation I would want to have."
At executive level, levelling is local and scope is portable. Negotiate the charter you can describe on your CV, not the title you would have to explain.
© 2026 Preptima. Originally published at preptima.com (opens in a new tab).