There's a trap on both sides of this one, and most companies fall into whichever is more comfortable for them.

Hire for today and you'll fill the org with people who are excellent right now and underwater in a year. You'll then run the same painful conversation repeatedly, wondering why the team keeps topping out.

Hire for the imagined future and you'll bring in a senior executive from a company ten times your size, hand them a role with no infrastructure under it, and watch them leave in eight months genuinely confused about what happened.

Both are expensive. The second is more expensive, and it's the one that gets praised as ambitious.

The question that resolves it

Not "what does this role need today?" and not "what will it need at scale?" but:

What does this role need to become within the next 18 months, and can this person get there?

Eighteen months is deliberate. It's long enough that you're hiring for growth rather than for the immediate gap. It's short enough that you're describing a real job rather than a fantasy.

Under that framing the criteria change. You stop screening primarily for current capability and start screening for slope — how fast has this person grown, and what did they do when the job outgrew them last time?

What slope actually looks like

The signal isn't a title trajectory. Titles inflate, especially at small companies.

What I look for is evidence of someone who has been in a role that changed underneath them and handled it deliberately. Concrete versions:

  • They joined when the team was 4 and stayed effective at 30 — and can describe specifically what they had to stop doing.
  • They built something informal, then replaced it with something structured when it broke, and can explain why they waited as long as they did.
  • They hired someone better than themselves at part of their own job.
  • They can name a thing they were wrong about, what it cost, and what changed as a result.

That last one is the single best question in an interview and the hardest to fake. People with real slope have a ready answer because they've genuinely examined it. People without one produce a rehearsed non-answer about being a perfectionist.

Where seniority actually helps — and where it doesn't

The mistake isn't hiring senior people. It's hiring senior people into an environment that can't support how they work.

An executive from a large company is often extraordinary at operating a function that already exists — a team, a budget, systems, analysts. Drop that person into a company where they're expected to personally build all of it from nothing and you've mismatched them badly. Not a talent problem. A context problem.

So the real screen for senior hires is: have they built, or have they only run?

Both are legitimate skills. At your stage, one of them is nearly useless. Someone who scaled a function from 2 people to 20 is far more valuable to a growing company than someone who managed 200 — even though the second résumé is more impressive.

Ask directly: what existed when you arrived, and what did you personally build? The answers separate these two candidates in about four minutes.

Hire the constraint, not the wish list

When budget is tight — and it always is — the discipline is to hire against your actual binding constraint rather than your longest wish list.

Most growing companies have exactly one constraint at a time. Everything is under-resourced, but one thing is the thing capping growth right now. Maybe you can't fulfill what you're already selling. Maybe you have no channel to sell into. Maybe the founder is the bottleneck on every decision.

Hire into that. Then re-ask the question, because it will have moved.

The failure mode here is hiring proportionally across every function to keep things "balanced." That feels fair and it's how companies end up with a bigger team and the same ceiling.

The part nobody wants to do

Hiring for the company you're becoming has an unavoidable corollary: some people who are genuinely good today will not be right for the company in two years.

Handling this badly — quietly sidelining people, layering managers over them without a conversation, hoping they'll leave — is corrosive, and everyone sees it happening.

Handling it honestly means saying early and clearly: here's where this role is going, here's the gap, here's the support available, and here's the timeline. Some people rise to it, and those are often your best long-term leaders precisely because they were told the truth and chose to grow. Some decide it isn't what they want, and they leave on good terms and speak well of you.

Both outcomes are far better than the slow ambiguous version, which ends with a resentful departure and a team that learned you won't say hard things.

You cannot build a company that outlasts you on relationships that require avoiding the truth.