Applying for a Job at the Company You Already Work For

An internal posting reads like a lower-stakes version of the whole job search. You already have a badge, a manager, a track record someone there can vouch for. It's tempting to treat the application itself as paperwork — attach whatever resume is lying around, write two lines in the notes field, and let your reputation carry it. That instinct is wrong often enough that it's worth taking apart, because the reasoning behind it is usually correct about the wrong audience.

The person who knows you usually isn't the person deciding

Say your reputation really is strong. Your manager likes your work, your team trusts you, people two desks over would say good things if asked. None of that is who reads an internal application first. At most companies past a certain size, an internal move still runs through a posting, a resume, and a hiring manager on the other team who has never worked with you. It often also runs through an HR business partner doing an initial screen, and sometimes a panel that includes someone from a third team entirely who is there to check for a specific skill gap the hiring manager is worried about.

None of those people have the context your reputation is built on. To them you are a name attached to a document, exactly like an external candidate, except you also have an internal profile they can casually check — which cuts both ways. If your resume undersells you, they may not bother digging past it to find out you're better than it says. Coworkers get the benefit of the doubt from people who already trust them. A hiring committee on another team owes you nothing they haven't been shown.

What your current team knows doesn't transfer with you

The deeper problem isn't that the new team doesn't know you. It's that they don't know what you did. Your manager has watched you work for two years and could describe your strengths without looking anything up. The person hiring for a role on a different team has never seen any of it, and "we work at the same company" doesn't fix that the way it feels like it should.

This shows up hardest when you're moving toward a different function than the one you're visibly known for. Say you're in customer support and applying to an internal ops role — you've spent a year building spreadsheets and light automation nobody outside your team asked you to build, because it made your own job easier. That work is real and directly relevant, and it is also completely invisible to anyone who wasn't sitting near you when you did it. Your current resume, if you have one on file at all, almost certainly doesn't mention it, because you didn't write it for this purpose. It was never asked to do this job.

This is the same discipline that makes any tailored resume work — selecting and describing the specific things you did that map to what the reader needs, rather than trusting that a general account of your role will get there on its own. An internal move just makes it easier to skip that step, because it feels like the reader already has the context a fresh resume would normally supply. They usually don't.

The promotion case is a different document

A promotion in place — same team, same manager, a level up — is not the same situation as a transfer, and it's worth not writing them the same way.

For a promotion, the manager deciding almost always does have direct visibility into your work, and often the document isn't really informing them of anything new. What it's doing is building a case that survives a calibration conversation with people who don't have that visibility: other managers, a director, sometimes HR, comparing your case against other promotion cases across the org using whatever the promotion criteria say for the next level. Your manager needs specific, checkable examples to bring into that room, not because they're unconvinced, but because they're now arguing your case to people who are.

That changes what belongs in the document. It should map directly onto the stated criteria for the next level — the actual competency language your company uses for that level, not a generic account of doing good work — and it should give your manager sentences they can lift almost directly into that conversation. Vague self-assessment ("I've grown a lot this year and taken on more responsibility") gives your manager nothing to work with. A specific instance of you operating at the next level, described the way you'd describe it to a stranger, gives them something to argue with in the room you're not in.

Don't let "they'll ask around" replace the document

There's a version of internal-application overconfidence that isn't really about the resume at all — it's a belief that informal backchannel conversations will do the actual convincing, and the formal application just needs to exist. Sometimes that's even true; a hiring manager who's already decided based on a conversation with your manager may barely read the resume. But you don't control whether that's the process you get, and a weak document is a real cost in every version where it isn't: the calibration meeting you're not in, the other candidate the hiring manager is also considering, the HR partner doing a first pass with no informal context at all.

The other failure mode runs the opposite direction: writing the internal application as if the reader has zero context, over-explaining what your current team does and why it matters, the way you might for an external reader with no institutional knowledge at all. The reader usually does know the company. What they don't know is your specific work. Spend the space there.

Tell your manager before the posting closes, not after

This isn't really a resume point, but it's the mistake that undoes good resume work most often: applying internally without your current manager knowing costs you more than a slightly awkward conversation. Most internal-mobility processes at companies large enough to have one either require manager notification at some point or make it obvious after the fact, and finding out secondhand reads as something being hidden from them, whatever the actual reason was. A short, direct conversation before you apply — not a request for permission, just a heads-up — costs a few minutes and removes a variable that has nothing to do with whether you're qualified.

What this comes down to

The comfortable assumption behind a lazy internal application is that you're known. The accurate version is narrower: you're known to some people, for some of what you've done, and the process for an internal move routes your case through people outside that circle more often than it feels like it should. The resume still has to do the job a resume does — surfacing the specific, real work that maps to what the new role or the next level actually needs — because the person deciding is rarely the person who already knows.