Resume for an Internal Promotion: What Changes
The short answer: Yes, you still need one — and it should be different from the resume you'd send outside. The people deciding already know you, which is the problem: they know you at your current level, and the document's job is to make the next one easy to picture. Lead with scope, quantify the results your colleagues watched but never saw measured, include the work outside your job description, and use internal vocabulary freely — this is the one place it helps.
Internal candidates lose in a predictable way. They assume the work speaks for itself, submit something they last updated three years ago, and get beaten by an outside candidate whose document was written for the role being filled. Being internal buys you a read. It doesn't buy you the job.
Familiarity is the obstacle, not the advantage
Two things work against you. First, the people who know you best know you doing your current job, and it takes deliberate evidence to shift that picture upward. Second, the panel is usually wider than you think — a hiring manager in another department, a skip level, an HR partner — and at least one of them knows you only as a name on a list. Write for that person.
So the structure inverts the usual instinct. Don't catalogue what you've been doing; show the parts of it that already resemble the job you're applying for. If you're going for team lead, the bullets about training two new hires and running the handover process matter more than your throughput. That's the tailoring rule, and internally it's easier to apply because you can read the actual job description of the actual role and know what it means.
Quantify what they watched but never measured
✗ "Worked on the vendor migration project and helped improve the onboarding process for new team members."
✓ "Led the vendor migration for our team — moved 240 active accounts in six weeks with no service interruption, and wrote the runbook the other two teams used afterward. Rebuilt onboarding so new hires reach full caseload in three weeks instead of six; four hires through it so far."
Colleagues saw the project happen. Almost nobody saw the numbers, because nobody counts their own work as they go. The resume is where you count it. Pull real figures from the systems you already use — tickets, sales, cycle times, headcount, budget — and if you truly can't measure something, describe the before and after state instead. Never inflate; you're one of the few candidates whose claims can be checked by walking down the hall, which cuts both ways and makes an honest number unusually powerful.
Include the work outside your job description
The clearest evidence for a promotion is the promotion-shaped work you've already been doing for free: covering for your manager, onboarding and training, running a recurring meeting, cross-team projects, the committee, the process you fixed that nobody asked you to fix, the system you became the go-to person for. These are the trust markers, and internal candidates are sitting on more of them than anyone.
Also list internal recognition plainly: awards, spot bonuses, being asked to present to leadership, mentoring assignments, and any formal development program you've completed. And if the role is in another department, treat it as a partial career change — the domain knowledge transfers, but you must spell out how, because a manager outside your function can't do that translation for you.
Use internal language — this is the exception
Everywhere else, we'd tell you to strip company-specific acronyms and internal system names. Here, keep them. Your reader speaks that vocabulary, and naming the actual systems, programs, teams, and processes is instant proof you already operate inside the machine — a new hire would need months to learn what you can reference in a clause. Just keep one plain-language version of the document too, because you'll want it the moment you look outside, and the translation is much easier to do while the details are fresh.
The process, handled well
A few practical things. Apply through the official system even if you've already talked to the hiring manager, because HR needs the record and skipping it creates problems for the person hiring you. Tell your current manager, ideally before you apply — most internal processes notify them or require acknowledgement, and hearing it from HR first damages a relationship you still depend on; check your employer's internal mobility policy for what it actually requires. Write a short cover note rather than skipping it: one paragraph on why this role, one on the two most relevant things you've already done, and one on what you'd do in the first ninety days. Internal candidates are often the only ones who can write that third paragraph credibly.
And prepare for a real interview — the panel may include people who have never worked with you, and "you already know what I do" is not an answer. Go in able to tell each story on the page in two minutes, the same way you'd prepare for any screen. If it doesn't go your way, ask for specific feedback about the gap; internally, that's the one rejection that reliably comes with a map.
Two versions, one afternoon. PlainResume makes it easy to keep an internal version and a plain-language external one — free, no sign-up, no paywall on the PDF, and everything stays in your browser.
Build your resume free →Frequently asked questions
Do you need a resume for an internal role?
Almost always — HR needs it on file and the panel usually includes people who don't know you. Being internal gets you read, not hired.
How is it different from an external resume?
Lead with scope for the target role, quantify work colleagues witnessed but never measured, include work outside your job description, and keep internal vocabulary.
Should you tell your manager?
Usually yes, before applying — most processes notify them anyway. Check your company's internal mobility policy for what's required.