An internal interview looks like the easy version. You know the building, you know the acronyms, and at least one person on the panel has seen your work. That is exactly why it goes wrong so often: candidates prepare less for it than for an external interview, and the panel expects more.
Everything you say in an internal interview is checkable. The people across the table can walk down the corridor and ask your manager whether the project really shipped on time. Your reputation arrives in the room before you do, and your job is not to introduce yourself. It is to change what they already think.
You are judged on a known record, so talk about the scope you have not held
An external candidate has to prove they can do the work. You mostly do not. The panel already has a view of your skills, formed from meetings, from the last review cycle, from how you handled that outage in March. Spending twenty minutes proving you are good at your current job wastes the one thing they cannot see from where they sit.
What they cannot see is how you operate at the next level. If you are moving from analyst to team lead, nobody has watched you manage a low performer or defend a headcount request. If you are moving sideways into product from support, nobody has seen you say no to a customer. That gap is the real subject of the interview.
So prepare around the scope you have not yet held:
- Pick two or three situations in which you already did a slice of the new job without the title. Covering for a manager on leave, running a cross-team project, owning a budget line for a quarter.
- For each one, be precise about what was yours and what was borrowed. "I ran the weekly sync" is different from "I decided which work got cut."
- Name what you would do differently at full scope. This shows you have thought about the job, not just about getting it.
The question behind every internal interview is not "can you do this?" but "can you do the part of this we have never seen you do?"
The shared-context trap
This is the most common mistake, and it is invisible to the person making it. Because the panel knows the company, you skip the setup. You say "the migration" and assume everyone remembers which migration, how late it was, and what you did to rescue it. They do not. People remember outcomes vaguely and contributions almost never.
The result is that internal candidates under-explain their own results. An external candidate describing the same project would give the context, the problem, the numbers and their part in it. You, trying not to bore people who were "there," give a sentence and move on. The panel then scores the external candidate higher for the same work, because they could actually hear it.
A practical fix: write out your three main examples as if for a stranger, then cut only what is truly redundant. Keep the numbers. Keep the "I" statements. If someone on the panel was involved, credit them by name, which also stops you from overclaiming in front of a witness.
It is also worth asking the hiring manager before the interview who is on the panel and how much of your work each of them has seen. That tells you how much to explain, instead of guessing.
When the panel includes someone awkward
Internal panels bring configurations that never happen externally. The two that throw people most:
Someone you currently outrank
A peer from another team, or someone junior to you, may sit on the panel as a future colleague or stakeholder. Treat their questions with exactly the same weight as the hiring manager's. Anything that looks like impatience or talking down gets noticed by everyone else on the panel, and it is the fastest way to confirm a worry about how you would lead.
Someone who did not back you
Maybe a senior person turned down your last project proposal, or you know they supported a different candidate. Do not try to win them over with warmth you do not feel, and do not relitigate the old disagreement. Answer their questions directly and, if the history is relevant, acknowledge it once in plain terms: "We disagreed on the vendor choice last year. Here is what I took from it." That reads as maturity. Avoiding the topic reads as a grudge.
Tell your manager before they hear it elsewhere
In most companies your current manager finds out that you applied. HR may notify them, the hiring manager may call them for a reference, or someone mentions it at lunch. The only question is whether they hear it from you.
Tell them first, before or right after you submit. Keep it short and forward-looking: what attracts you about the role, that it is not a reaction to anything wrong with your current job (if that is true), and that you will keep delivering in the meantime. Do not ask for permission unless your company policy requires it. Do ask whether they would be willing to speak for you.
This conversation also protects you. A manager who learns about your application from the hiring manager will feel blindsided, and a blindsided manager gives a cautious reference. A manager who heard it from you has had time to decide how to support you.
The question you will definitely get: why this role rather than growing where you are
Every internal panel asks some version of this, and it is harder than it looks, because both obvious answers hurt you. "I have outgrown my team" sounds like a complaint about your manager, who may be a friend of the person asking. "I just want a new challenge" sounds like you have not thought about it.
A good answer has three honest parts:
- What the new role does that your current path cannot. Be specific: owning a P&L, working closer to customers, managing people. Not "more growth."
- Evidence that you have already tested the interest. The side project, the shadowing, the course you took on your own time.
- What your current team gets out of it. A clean handover plan, a person you have been developing who can step up, a timeline.
The third part is the one most candidates forget, and it is the one that answers the unspoken worry: will moving you leave a hole?
If you do not get it
Internal rejections sting more than external ones, because you still have to sit in the same meetings the following week with the people who said no. How you handle the next month matters more for your career at that company than the interview did.
Ask for feedback, but ask in a way that gets a usable answer. "Any feedback?" produces something polite and empty. Try instead: "What would you need to see from me in the next six months to be the obvious choice for a role like this?" That question is about the future, it is concrete, and it invites the hiring manager to become an ally for the next opening.
Then do three unglamorous things. Thank the panel individually. Tell your manager what you learned. Keep your current work at the same standard, because people will watch whether you check out. The candidates who get the second internal role are very often the ones who handled the first rejection well.
If the feedback points to a gap in how your experience comes across on paper, it is worth tightening your profile and CV before the next opening. A tool like Postulit can turn an up-to-date LinkedIn profile into a clean CV quickly, which helps when the next internal posting has a short window.
What to do this week
Before an internal interview, do these in order:
- Tell your manager, in person, before the panel does.
- Ask the hiring manager who is on the panel and what each of them has seen of your work.
- Write your three strongest examples for a stranger, with numbers and your exact part.
- Prepare one clear answer to "why this role rather than growing where you are," including what happens to your current team.
- Draft your feedback question now, so you have it ready whatever the outcome.
The external candidates are preparing as if the job depends on it. Prepare the same way, and use the one advantage they do not have: you can prove the claims you make.