# From Individual Contributor to Manager: How to Tell That Story on a Resume
Most IC-to-manager resumes fail in one of two ways: they bury the transition so the reader can't tell when you stopped shipping and started leading, or they swap in generic management language like "responsible for a team of six," which describes every manager alive and distinguishes none of them. Here's how to do it better.
The transition started before the title did
Almost nobody gets a management title cold. You were running the intern program, leading the migration workstream, mentoring two juniors, or serving as tech lead for a year before the org chart caught up. That pre-title leadership is the most persuasive part of the whole story. It shows the move was earned rather than assigned. Most people leave it out entirely.
Put it on the resume explicitly, inside the IC role where it happened: "led a workstream of 4 engineers across two teams while a senior IC" or "ran hiring loop and onboarding for the team's 3 new hires." When the manager title then appears in the next role, the reader sees a progression instead of a jump. Progressions are believable. Jumps get probed.
Change what you count
The core narration failure is keeping IC metrics after the role changed. A manager's resume line that says "built the new billing service" signals one of two things: you were still doing IC work instead of managing, or you're taking the team's credit. Both readings are bad.
Manager accomplishments are things that happened through other people, and the numbers that prove them are different numbers: team throughput and delivery ("team shipped 3 major releases in 12 months, up from 1 the prior year"), people outcomes ("grew the team from 4 to 9, retained everyone through a reorg, promoted 2"), and organizational reach ("cut onboarding time from 8 weeks to 3"). "Enabled" and its cousins earn their place here. You didn't build the thing. You built the team that built the thing. Saying it that way is the whole point.
Keep your credibility, lose the nostalgia
New managers over-correct in one of two directions. Some scrub all technical content, which reads as someone who has abandoned the craft and can no longer evaluate the work. Others keep a resume that's 80% IC accomplishment with a manager title stapled on, which reads as someone who never made the transition.
The balance: your most recent role should be mostly about outcomes through the team, with one line that anchors technical credibility, for example "still review designs and unblock the hardest technical calls." Your older IC roles carry the hands-on record. The further back the role, the more compressed it should be.
Handle the awkward cases plainly
Did the job without the title? Say what you did, not what you were called: "acted as engineering manager for a 5-person team (title: Senior Engineer), owning 1:1s, planning, and performance reviews." Recruiters see title lag constantly and can translate it when you give them the facts.
Went back to IC afterward, or managed a team of one or two? Same rule. State the scope truthfully and frame the movement as chosen where it was chosen. A stint of management followed by a deliberate return to senior IC work is a normal career shape now. Narrating it confidently beats letting the reader invent a demotion story.
The interview version
The resume gets you the conversation, and the conversation will open with some version of "tell me about the transition." Prepare the honest answer: what pulled you toward management, the first thing you were bad at, and what you changed. "I thought the job was technical decisions at larger scale. It turned out to be mostly building people and clearing paths, and the skill I had to learn fastest was giving hard feedback early." A story with a real stumble in it outperforms a flawless one every time, because every hiring manager remembers their own first year.
One structural note: this story needs different emphasis for different applications. A manager role wants the leadership arc front and center. A senior IC role at a company you'd happily return to the craft for wants the technical record leading, with the management chapter as context. Same true history, different emphasis per target. That's exactly the job of Angles in TailorFit: enter your background once, keep a manager-track and an IC-track framing ready, and send each role the version of you it's actually hiring.