Interviewing internal candidates: fairness, confidentiality and the no

Interview internal candidates against the same competencies, with the same questions and the same rating scale you use for external applicants. What changes is the evidence around the interview: you already have performance data, colleagues with opinions, and a person who will still work here on Monday whatever you decide. Handle those three well and an internal process is fairer and faster than an external one.

This page covers what to decide before the role is posted, confidentiality, questions that work for internal candidates, using performance history without double counting it, conflicts of interest, and the conversation when the answer is no.

Decide the process before the role is posted

Most internal hiring goes wrong before any interview happens, because nobody wrote down how it would work. Settle these with your recruiter or HR partner first, and put the answers in the posting.

• Are internals considered first, or alongside externals? Both are defensible. Not saying is not.
• Who interviews them, and at which stages? If they skip the recruiter screen, decide who covers compensation, level and timing instead.
• What are the eligibility rules? Time in role, performance standing, manager notification. Apply them to everyone or drop them.
• When is the current manager told? Before the first interview, at offer stage, or when the employee chooses. Your policy may decide this; if it does not, agree it with the candidate.
• Who decides, and does anyone have a veto? A current manager who can block a transfer should know that before anybody interviews.
• What is the fallback if they are not selected? Who tells them, when, and what development conversation follows.

Write the competencies and anchors at intake, before the internal candidate is known, exactly as for an external search. Criteria written after you know who is applying tend to describe that person, or to describe the opposite if you would rather they did not apply.

Confidentiality: who knows what, and when

An internal application is sensitive for the candidate. It signals that they are looking, and if it becomes known before they choose, it can change their standing in their current team.

• Say the rules up front. "Your manager will be told before the final round" is workable. "We will probably mention it at some point" is not.
• Keep the interview list short and brief every interviewer on confidentiality in the same words you would use for an external candidate's compensation.
• Do not discuss an application in shared channels, open-plan meeting rooms, or calendar invitations with revealing titles. "Chat with Priya" beats "Team Lead interview".
• Keep scorecards where the candidate's colleagues cannot read them. An ATS with visible feedback is a problem when the interviewer sits next to the candidate.
• If it leaks, say so. Tell the candidate what happened and what you are doing about it, rather than hoping they have not noticed the room go quiet.

The reverse also applies. Internal candidates sometimes know things about the role, the team or other applicants that external candidates do not. Say plainly what they should not share: other people's applications, compensation information they see in their current seat, or what they heard about the reorganization.

What stays the same, and what changes

The most common failure is the interview that is not really an interview: twenty minutes of catching up, because you work with the person already. The candidate then has nothing on record, and if an external candidate is chosen there is nothing to show the decision was made on evidence. Run the hour properly. The interview scorecard template is the same one you use for everyone.

Questions for internal candidates

Ask these in addition to the role's core questions, and ask them of every internal candidate. They test the two things that decide whether an internal promotion works: whether the person has thought about the change in relationships, and whether they can see the role rather than the extension of their current job.

• "What would you do in your first 90 days that is different from what you do now?"
  Strong: names a change of scope, not more of the same work. Red flag: describes their current job with a new title.
• "Which parts of your current work would you have to stop doing, and who picks them up?"
  Strong: has thought about the handover, names people, knows what would suffer. Red flag: "I'd keep doing both."
• "You would be managing people who are your peers today. How would you handle the first difficult conversation?"
  Strong: a concrete plan and an acknowledgment that some friendships change. Red flag: "Nothing would change, we're all adults."
• "What do you know about this team's problems that you would not know as an outsider, and what would you do about the first one?"
  Strong: uses inside knowledge constructively and discreetly. Red flag: criticism of named colleagues.
• "Where would you need support in the first six months?"
  Strong: specific and self-aware. Red flag: nothing, or something that is obviously not the real gap.
• "If you do not get this role, what do you want from the next year here?"
  Asked gently, and it tells you a great deal about retention and about how they will take a no. Do not use the answer as a reason to decline them.
• "What will be hardest about leaving your current team?"
  Strong: names the relationship or responsibility honestly. Red flag: contempt for the team they are leaving.

One question to avoid: "why should we choose you over an external candidate?" It invites a comparison the candidate cannot make and tells you nothing about the competencies.

Using performance data and colleagues' opinions

The information advantage of internal hiring is real, and it is also where fairness breaks down. Three rules keep it useful.

1. Same sources for every internal candidate. If you read one person's last two reviews, read everyone's. If you speak to one person's manager, speak to all of them, with the same questions.
2. Job-related evidence only. A review rating is evidence about the job they do now. Use the content, not the number: what it says about how they lead, decide or deliver, matched to the competencies you defined.
3. Hearsay is not evidence. "People say they're difficult" does not go on a scorecard. If the concern matters, turn it into a question for the structured manager input below, or into an interview question asked of every candidate.

Collect the manager's view the way you would collect a reference, in writing, against the competencies:

MANAGER INPUT: [candidate] for [role]
Completed by: [manager]      Date: [ ]
(Shared with the hiring panel. Kept with the hiring record.)

1. What does [name] own today? Scope, team size, budget, systems.
2. Give an example of [competency 1] from the last six months.
3. Give an example of [competency 2] from the last six months.
4. What would they find hardest about the step up, and why?
5. What support would they need in the first 90 days?
6. Anything about readiness or timing we should know? (Facts, not
   predictions about what they would "probably" do.)
7. If they are selected, what is the handover plan and the timeline?

Not asked, and not relevant: personal circumstances, health, family,
plans outside work, anything protected by law.

A current manager may have an interest in keeping the person. Score their input as one source among several, and give the candidate the chance to answer anything that would change the decision.

Conflicts, and what to do about them

• You know the candidate well. That is an advantage and a bias risk both. Bring a second assessor who does not know them, score independently, and write the evidence down.
• The candidate reports to you now. Involve HR, and be clear with yourself about whether you are assessing their work or rewarding loyalty.
• The candidate's manager is a peer of yours. Agree the handover terms before the offer. A transfer blocked after a yes is the worst outcome for everyone, especially the candidate.
• You have a personal relationship outside work. Say so to HR and step out of the decision. A recusal costs you one process; a challenged promotion costs more.
• Another leader has already promised them something. Surface it early and bring it into the open. Half the internal hiring conflicts in a company are undocumented promises.
• Two internal candidates from the same team. Tell both the same things at the same times, and think about who manages the aftermath in that team.

Records and the rules you cannot bend

• Promotion decisions are part of the hiring record. 29 CFR 1602.14 requires covered employers to keep application forms and other records having to do with hiring, promotion, demotion, transfer, lay-off or termination for one year from the record or the personnel action, whichever is later, and until final disposition if a charge is filed. Scorecards and manager input for internal candidates are those records.
• Do not let protected activity influence the decision. The EEOC's facts about retaliation explain that punishing applicants or employees for asserting their rights is unlawful, and that denial of promotion can be a materially adverse action. Someone who raised a complaint or took protected leave is assessed on the same competencies as everybody else.
• Watch the reasons that hide something else. "Needs another year of seasoning", "not ready", "we need them where they are" are not evidence. Write what the candidate did or did not show against a defined competency.
• Keep the same standard in the record as in the room. Everything in what not to write in interview notes applies, with the extra weight that this person may read it in a performance conversation later.

The conversation when it is no

This is the part that decides whether the internal process strengthens your team or costs you a good employee. Do it yourself, on the same day the decision is made, before the announcement and before any email.

THE NO CONVERSATION (15 minutes, in person or on video)

1. The decision, first sentence. "I want to tell you myself: we've
   offered the role to someone else."
2. The reason, specific and job-related. "The gap was [competency].
   In the interview, [what they showed]. What we needed to see was
   [anchor]."
3. What would close it. One or two things, with what "done" looks like.
4. What you will do. "I'll put you on [project] so you can build that,
   and we'll review it on [date]."
5. What you will not promise. "I can't promise the next opening will be
   yours. I can promise you'll be a serious candidate for it."
6. Their turn. Ask what they are thinking, and let the silence run.
7. The practical part. Who else knows, when the announcement goes out,
   what you will say if colleagues ask.
8. Follow up in writing the same day, and put the review date in both
   calendars.

Three traps in that conversation:

• Softening the reason into nothing. "It was very close, the other person just had a bit more experience" gives the person nothing to work on and reads as a brush-off.
• Promising the next one. You do not control it, and the promise comes back at you in a year.
• Letting them find out from the announcement. If the news is going out on Friday, the conversation happens before Friday. If the timing is impossible, delay the announcement.

Expect them to consider leaving; some will. Follow up in the next week rather than treating the conversation as closed, and keep the review date even when the quarter gets busy. The written follow-up should match what you said; the rejection email templates include a version for internal candidates, to send after the conversation and never instead of it.

When the internal candidate gets the role

• Agree the handover and the start date with their current manager before the announcement, in writing, including what happens to unfinished work.
• Tell the people affected in the right order: the candidate, their manager, the team they are leaving, the team they are joining, then the wider announcement.
• Brief them on managing former peers if the role involves it: what changes on day one, what conversations they should have in the first week, and what they can no longer share.
• Give the same onboarding you would give an external hire, adjusted for what they already know. Internal promotions often get nothing, on the assumption that the person is already up to speed.
• Close the loop with everyone else who applied, internally and externally, before the announcement reaches them by another route.

If external candidates were in the same process, the comparison itself needs to be evidence-based rather than a contest between the familiar and the new; see how to compare candidates after interviews.

A checklist for an internal process

• Competencies, anchors and the process written before the role is posted.
• Posting says whether internals are considered first, and what the eligibility rules are.
• Manager notification rules stated to candidates before they apply.
• A real interview, with the same questions and scorecard as external candidates.
• Internal-specific questions asked of every internal candidate.
• Performance data and manager input collected the same way for each of them, in writing.
• Hearsay excluded; anything material put to the candidate directly.
• Conflicts declared, with a second assessor or a recusal where needed.
• Scorecards and manager input kept with the hiring record.
• The no delivered in person by you, before the announcement, with a gap, a plan and a date.
• The review date kept.