Skip to content
AptResume

Internal Transfer Resume: Moving to a New Team

An internal transfer resume is for a reader who already knows the employer. You are moving to a new team, a new desk, or a new kind of work inside the same organization. The page has to show which part of your current job belongs on the team you want.

People who had been at Anthropic for at least a year were 50% more likely to move across departments each month in 2026 than in 2025. That figure is from How employment is changing at Anthropic (16 October 2026). It is that company's experience. It is not a rate to expect at yours, and it is not a promise that a transfer is available. It is a reason to have a resume ready when an internal posting shows up, because the move is a different document from the one that got you hired the first time.

If you are leaving the employer, use the starter resume for a new field. The rest of this page stays on the same-employer move.

Reframe the job you have

The new team's manager can often see your title in a directory. What they cannot see is which decisions in that job look like their work. Open with those.

Write a short summary that names the team or the kind of work you want, then one result from your current role that the new team would recognize. Keep the employer's name. Change the emphasis.

Summary shape: Support specialist moving to the internal tools team. The current role already includes a handoff that another desk uses.

Then rewrite two or three bullets so they face the target desk. Leave the bullets that only make sense in the old workflow lower down, or cut them. A transfer packet is often one page. The directory already holds the long version.

Name a decision that traveled

"Traveled" means the decision still matters on the other side of the org chart. Three kinds show up often:

Put one of those in a bullet with a number.

Process: Negotiated the handoff of a billing checklist to the team you are joining, and the next close finished on time for 8 people.

Tool: Defined a one-page intake form for another desk, and their ticket volume fell 20%.

Customer: Prioritized a complaint two teams had been bouncing, and repeat contacts on that issue dropped 15%.

The verb is the decision. The number is how you know it mattered. A duty list ("responsible for tickets, reports, and meetings") tells the new manager what the old job contained. They can read that in the posting you already hold.

Write it for the posting, then stop

Internal postings are often short, and they reuse the company's own words. Mirror the team name, the tool names, and the outcome the posting uses, when those words are true of your work. Skip the jargon you would have to explain to a teammate.

You usually do not need a full early-career history. Keep education, a certification the new team asked for, and the current role. Older jobs can stay as one line if they explain why you can do the new work.

Ask one person on the target team which result they would care about, if you can do that without turning it into a campaign. Then put that result first. A resume that tries to prove you can do every job at the company makes the transfer harder to see.

What to leave off

Build the page in the editor. The readiness panel's Quantified achievements check counts experience bullets that include a number, under How is this scored? Use that as a nudge to keep the result in the sentence.

A transfer is a different problem from a first search

Someone reading an external resume has never worked with you. Someone reading an internal one may have. That is why the bullet has to be a decision they might already have felt, with a number attached, rather than a tour of your department.

When the posting is entry-level in title and senior in the years line, the entry-level posting guide covers that mismatch. For the internal move itself, start from the job you have, point it at the team you want, and keep the page short enough to read between meetings.