I'm about a year into my first management role and I'm starting to think about what my resume looks like if I ever need it. The problem: most resume advice for managers assumes you have years of performance review cycles, attrition numbers, hiring track records. I have one year.
Here's what I've figured out, with a lot of help from people who've been in this longer than me.
What you do have at one year: Team structure when you started vs. now (headcount, scope) Any hiring you did (I hired two people; that's something) Any org changes you drove or survived The projects your team shipped under your leadership How you set up 1:1s, processes, sprint rhythms, anything you built
None of those require years of data. 'Inherited a 4-person team, grew to 6 through two new hires, introduced bi-weekly eng reviews' is real and specific.
The thing I got wrong initially: I was trying to separate my IC contributions from my management contributions, but a lot of what I do is both. I still do architecture reviews. I still write code occasionally. A mixed role is normal for a first-time manager, especially at a smaller company. Your resume can reflect that without apologizing for it.
What not to do: Don't inflate. 'Built a high-performing team' is vague enough to be meaningless. Describe what the team did, not your assessment of whether it was high-performing.
The leveling question: If you're looking at roles and they say 'minimum 3 years management experience,' one year probably won't get you there unless you're in a different function or a different-sized org. That's okay. Know what you're going for.
Am I applying anywhere right now? No. Just future-proofing. But curious if others who made the IC-to-manager jump have figured out how to tell the story.