What Director–VP hires actually want, in their own words

Over a long run of Director–VP conversations we started writing down the first reason a candidate gave for being open to a move, before we prompted them. The pattern was striking mostly for what it left out. Compensation came up, it always does, but rarely first, and almost never as the thing they lingered on. What they lingered on was the shape of the role. Whether it owned a real outcome. Whether the decisions that mattered would actually be theirs. Whether they'd be able to point at something a year in and say they built it.

The perks got mentioned when we asked directly and forgotten the instant the conversation turned to why this role. The campus, the wellness budget, the sabbatical policy, a senior person has usually had all of it before. They aren't moving toward a nicer floor. So we stopped treating the offer letter as the centre of the decision. At this level the offer letter is a threshold to clear, and the reasoning that decides the move happens somewhere the letter can't reach.

Money has to be right, and getting it wrong ends the conversation before it starts. But “right” is only a threshold to clear; it never breaks a tie. Once it's cleared it stops mattering, and the candidate moves on to the questions they actually care about. Flexibility behaves the same way. It's expected now, and expected things don't persuade anyone; they only cause trouble when they're absent. Both of these are easy to compete on precisely because everyone competes on them, which means neither one wins a candidate who has options.

What decides the move is the mandate: whether the role owns a real problem, whether the scope is theirs or borrowed, and whether the manager is someone they'd learn from. These are the hardest things to convey in a process and the easiest to fake, which is why senior candidates probe for them so relentlessly. They've all been sold a scope that turned out to be a slide. They're testing whether the words are load-bearing.

Three things recur when we listen closely. Scope: how much of a problem is genuinely theirs to own, versus a slice of someone else's. Mandate: whether the authority on paper survives contact with the parent's decision rights, or evaporates the first time a hard call gets escalated over their head. And a line of sight to impact: whether they can see how their work reaches the business, or whether they'll spend 2 years executing decisions made elsewhere without ever knowing if any of it landed.

Every one of those is a question about experience, and none of them is about benefits. Each is decided long before day one, in how the role was scoped and how honestly it was described. The centres that keep their senior hires are the ones where the role the candidate imagined and the role they arrived to were the same role. When those two diverge, the person usually knows inside the first quarter, and the good ones start taking calls again by the second.

A smaller or younger centre often walks into the market convinced it's outgunned. The hyperscalers and the marquee names have the campuses, the food, the brand on the resume, and there's no realistic budget to match them perk for perk. So the instinct is to compete on the axis you'll always lose. For the senior AI, data, and engineering people worth fighting for, that was never the decisive axis. The office is a backdrop; the work is the day.

What moves them is whether the problem in front of them is real, hard, and genuinely theirs. A meaningful system to own beats a nicer building, because you can lose the amenity comparison and still win the candidate as long as the scope is something they can't get at the bigger, more crowded name. We've watched strong engineers turn down the shinier campus for the harder problem more than once. The problem itself does most of the selling; the recruiter's job is mainly to describe it accurately and get out of the way.

The catch is that senior technical people can tell the difference between owning a system and being handed a piece of one that's really controlled elsewhere. Ownership that evaporates the first time a decision matters is worse than no promise at all, because it confirms the bigger name would have been the safer bet. The advantage only holds if the work you describe is the work they actually get, and a Director–VP hire has been burned by the gap between the two often enough to assume it's there until proven otherwise.

Which is why this lives in the experience of the job rather than in the recruiting pitch. A centre that offers genuine scope has to protect it: keep the decisions local, resist the pull to centralise the interesting parts back to headquarters, let the person who owns the problem actually own it when it gets hard. Do that and the work recruits and retains at the same time. The campus impresses on the tour; the work is what they live every day, and what they'll stay for or leave over.

Offers enumerate the benefits carefully: comp, bonus, leave, insurance, the perks. The one thing that most shapes whether a senior person will thrive isn't on the list, because finance can't underwrite it: autonomy. The latitude to decide how the work gets done, to set their own approach, to be trusted with the how rather than handed a method to follow. It never appears in the offer letter, and it's weighed more heavily than half the things that do.

To someone senior, autonomy is the operating signal that they're trusted as the professional they were hired to be. Its presence reads as respect. Its absence reads, unmistakably, as a downgrade: a message that they were brought in for their judgment and will now be asked not to use it. You can match every number on a competing offer and still lose the candidate on this one line, because it's the line that tells them what the next 3 years will actually feel like.

The distinction that keeps senior people is clean enough to state in a sentence: hold them to the what, the outcome, the standard, the deadline, and leave them the how. That's what it means to hire a leader. The failure mode is the reverse: agreeing an outcome and then managing every step toward it, second-guessing decisions that were supposed to be theirs. Do that and you've paid senior money for a supervised job, and the person doing it works it out fast.

This is also where the offer and the reality most often come apart. A centre can win the offer and lose the person inside a year if the autonomy that was implied never materialises. Latitude costs nothing to give and everything to withhold, and it doesn't show up on any dashboard until the resignation does. If you want to know whether a senior hire will stay, watch how the first genuinely contested decision gets handled: whether it stays with the person who owns it, or quietly travels back up the line.

When two offers are close on money, and at this level they usually are, the deciding factor is which one the candidate can picture more clearly. The winning offer names the mandate in specifics: the outcome they own, who they answer to, what they get to decide alone. The losing offer talks about culture and campus and brand and hopes the candidate fills in the rest. The employers landing these hires in our processes did the thing most job descriptions actively avoid. They were specific about the hard part, the real constraints, the real reason the seat was open.

Precision reads as respect, and respect reads as a role that's been thought through. If you can't describe the mandate concretely, the candidate assumes it doesn't exist yet, and a senior person won't bet a good career on a role someone is still inventing. The teams losing out led with the brand and the benefits and wondered why strong candidates went cold after the first round. When your pitch to a Director–VP hire is indistinguishable from your competitor's, you've agreed to compete on money, the one axis where the best people have already decided you're interchangeable.