Career Switchers · Primly Community

engineer to engineering manager and back: how bad is the level drop when you return to IC?

corp_refugee · 5 replies

i went from L6 IC to EM (skipped the senior EM title) at my last company. took the role because i wanted to try it, because someone asked and i wasn't doing anything else interesting at the time. classic mistake, honestly.

18 months later i wanted my technical identity back. the question was: what level would i come back as?

here's what i found. the answer is: it depends on how long you were managing and how honestly you assess your technical drift.

if you were EM for less than 2 years and you kept some technical involvement (architecture reviews, coding on nights for side projects, staying current on your stack), most companies will try to land you at the same level you left or one below. you'll need to pass the full coding loop again, which is jarring, but if your fundamentals are solid you can get through it.

if you were EM for 3+ years, plan for a one-level drop as a baseline and be grateful if you land at the same level. the market knows that people drift. a staff eng loop is hard even when you've never stopped coding.

what actually helped me: i was honest in screens. i said 'i've been managing for 18 months and my coding pace slowed, but i've been reviewing architecture and staying current on the domain.' honesty calibrates the loop better than pretending. i leaned hard on system design. that's where my EM experience actually helped: i had sat in the room where the big technical calls got made, and i could talk about tradeoffs at a level most ICs can't. i took 6 weeks to practice before applying. not kidding, i needed it.

came back at the same level i left. not everyone does. some people come back a level down and then promote quickly once they're in. that's also a valid path.

if you're thinking about the EM to IC switch: do it, if that's where your energy is. just prep for the loop.

5 replies

staff_steph

the system design advantage is real. spent two years doing tech leading and hiring, and my system design interviews got noticeably better because i'd actually lived through making those calls at scale. the interviewers can tell when you're describing something you've actually argued about in a war room versus something you read about.

careerveteran

from the hiring side: we expect EM candidates returning to IC to have slightly rusty leetcode. what we're actually probing for is 'does this person still think like an engineer, or do they think like a manager who used to write code.' the mindset question matters more than the specific syntax.

corp_refugee

that's a useful reframe. i spent a lot of prep time on LC mediums when the actual signal they wanted was probably in the design round.

newgrad_neil

unrelated question but this thread is making me think: is it bad to become an EM early, like within 5-6 years of graduating? i've been told to wait until i'm 'technically deep enough' but i don't really know what that means.

director_dee

neil, answered in a different thread but short answer: the risk isn't going EM too early, it's going EM before you have enough technical credibility that your reports respect your judgment on technical tradeoffs. that's usually senior+ IC, but it varies by team.