Internal Candidate or External Hire? How to Decide Fairly

You've got a role open. Someone on your team has been doing half of it informally for a year and clearly wants it. You also know the team could use a fresh perspective, or the internal person isn't quite ready. So you post the job externally anyway — and now you're worried the whole thing looks rigged no matter what you do.

This is one of the more uncomfortable decisions a small employer makes, because it isn't really about skills. It's about trust, morale, and whether people believe your process is honest. Get it wrong and you either lose a good employee who feels used, or you promote someone unready because saying no felt too awkward.

Decide the criteria before you know who's in the running

The single biggest mistake is defining "what good looks like" after you've already got applicants, because by then you're unconsciously grading against the person you already know. Write the job requirements — the actual tasks, the level of ownership, the skills — before you open applications, internal or external. Put it in writing somewhere, even just an email to yourself or a shared doc. It sounds bureaucratic for a 30-person company, but it's the only thing that stops the criteria quietly bending toward whoever you like.

A useful test: if you wrote these requirements and neither the internal nor external candidate existed yet, would you still write them this way? If a requirement only makes sense because it happens to describe your internal candidate exactly, drop it or rewrite it.

Should the internal candidate go through the same steps?

Yes — same interview questions, same work sample or test, same scorecard. Not because you don't trust them, but because anything less is unfair to the external candidates who don't get the benefit of the doubt, and it also robs you of real information. People you work with every day are surprisingly easy to misjudge, in both directions: you either overrate them because you like them, or you underrate them because you've only ever seen them in their current, narrower role.

If you're using any kind of structured test or work sample as part of the process, run everyone through the identical version — same time limit, same scoring. This is one place where a tool built for this actually helps: AssessFit runs the same adaptive test for every candidate and caps how much a CV (or, in this case, tenure and familiarity) can influence the score, so an internal candidate's charm or history with you doesn't quietly outweigh the evidence. That matters more here than almost anywhere else, because internal politics are exactly the kind of thing scoring rigor is supposed to protect against.

One exception worth naming: if the internal person has been doing pieces of this job for months, it's fair to ask them harder, more specific questions than a fresh external candidate — not different topics, but deeper follow-ups, because they've had more chances to think about it. That's not bias, that's appropriately raising the bar for someone with more context.

Tell them before they apply, not after they lose

The conversation that gets skipped, almost always: sitting down with the internal candidate before the process starts and telling them plainly that you're also looking externally, why, and what you're specifically weighing them against. Something like:

"I want you to know we're posting this externally too. That's not a signal about you — it's because [reason: the role's changing shape / we want to see the market / it's a big enough hire that we owe it to the business to compare]. You'll go through the same steps as anyone else. I'll be straight with you either way."

This single conversation prevents most of the resentment that follows a "no." People can handle losing a fair competition. They can't handle discovering after the fact that they were part of a process that was never really open.

If you already know the answer

Sometimes you don't actually have a real decision to make — you already know you're going external, or you already know the internal person has it locked in, and the "process" is theatre. If that's true, don't run one. A fake competitive process is worse than no process at all, because it costs external candidates real time and costs the internal person real anxiety, for a decision you'd already made. If you know, just say so and do it directly. Save the formal process for when the outcome is genuinely open.

What to say if the internal candidate doesn't get it

This is the part that decides whether you keep them or lose them within six months. Be specific about why, without pretending it was close if it wasn't. Vague comfort ("it was really tight, you were great") when it wasn't tight reads as condescending once they compare notes with anyone. Better:

"We hired externally because we needed [specific gap — deeper experience running a team this size, a particular technical background, whatever is actually true]. That's not a reflection of your work here, which has been genuinely good, and here's what I think would make you the clear choice next time this comes up."

Then actually follow up on that plan in the next few months. An internal candidate who loses fairly and sees a real path forward usually stays. One who loses and hears nothing again starts job hunting within the quarter — and you'll have taught your whole team what happens when you compete honestly for something.

The judgment call you can't script

There's no formula that removes the real tension here: loyalty and institutional knowledge are worth something, and they're genuinely hard to score against a stranger's polished interview performance. Weighing that fairly against what an external hire might bring is a judgement call, not a checklist item — the best you can do is make the criteria explicit, apply them the same way to everyone, and be honest with people about which one you're doing. If you can't defend the process to the person who didn't get the job, it wasn't fair, no matter how it looked on paper.