Career Switchers · Primly Community

switching from IC to engineering manager: when to do it, when not to, and the part nobody tells you

staff_steph · 4 replies

been a staff IC for four years. made the IC-to-EM switch eighteen months ago. here's what i know now that i didn't know going in.

when it actually makes sense to switch

you find yourself spending more energy on unblocking your team than writing code and you're not resentful about it. you care about the team's output more than your own output. when something ships, you feel more satisfaction from the team doing it well than from the code you personally wrote. if those things are true, the EM path is probably the right call.

you're doing the EM job informally anyway. if you're the person running retros, unblocking dependencies, giving feedback in code reviews that's more about growth than bugs, coordinating with design and product when your tech lead is busy, you've already done the audition.

when to wait

you want the title or the manager salary but you're not actually sure you want to stop coding. this is the most common mistake. a lot of people become EMs because it felt like the obvious next step and then spend two years being quietly miserable. the path back is real but it costs you.

you haven't actually managed conflict between two people yet. this is the part that ends people. most ICs have never had to hold two people in a room and work through a real disagreement about work or work style. until you've done that once, you don't know how you'll respond.

the part nobody tells you

your peer group changes. as a staff IC, your closest colleagues are often senior ICs at the same level talking about technical problems. as an EM, your peers are other managers, and the conversations shift to org structure, performance management, and headcount planning. if you don't like those conversations you will be lonely.

you stop getting individual feedback loops. code either runs or it doesn't. an EM's output is measured over months through team retention, delivery quality, and the fact that nobody escalated anything to your director. the absence of drama is success, and that's genuinely hard to get used to after years of shipping and seeing results.

leveling when you switch externally: if you're a strong senior or staff IC going to a new company as an EM, you'll often be evaluated on the size of team you've managed. no team = EM1 or EML3 equivalent. that's fair but worth planning for.

4 replies

careerveteran

the peer group change is so accurate. it's an identity shift that nobody warns you about. you've spent years building your technical identity and suddenly your job is to not have opinions about the implementation and let the team own it. some people can make that shift. some really can't.

firsttime_mgr

i'm eight months in as a first-time EM and the 'absence of drama is success' thing took me a long time to understand. i kept feeling like i wasn't doing enough because i couldn't point to a specific thing i shipped. my director had to literally tell me 'the fact that your team shipped three weeks ahead of schedule and nobody is burning out is the work.' i intellectually knew that. emotionally took longer.

staff_steph

it took me about six months to stop feeling guilty about not coding. month seven it clicked. your output is the team's output.

director_dee

the external leveling point is important. if you want to come in as a senior EM at a new company, you need to have managed a team for at least 12-18 months and have specific stories about performance management, not just 'i led a project.' the upgrade path is: first EM job at current company, build the stories, then use those stories externally.