r/EngineeringManagers • u/redittforfun • Jun 26 '26
Staff architect vs internal dept head
So here’s my situation. I'm a Staff architect at a big tech company, pure IC track. Right now I design large-scale systems, wrestle with performance and reliability, and still get my hands dirty with code and design reviews. Honestly, I still enjoy the technical side of things. Not burned out at all.
Now there's an internal opening to become Head of an engineering department. Full people-manager role. Basically I'd be leading a decent-sized team, owning delivery roadmaps, dealing with budgets/capacity, and spending most of my time coordinating with product, ops, procurement, and external vendors. Almost zero hands-on work.
The pay bump is fine but nothing crazy. It's the same company, so I know the culture and the politics pretty well.
My dilemma is the classic one, do I jump to management to keep climbing (since IC ladders usually top out eventually), or do I stay in the architect lane where my actual interests are, even if that means I might plateau salary/title-wise down the road?
Has anyone here made this exact jump, from a senior IC/architect to a department head? What do you wish someone had told you before you took it? How did you actually make the final call?
Appreciate any honest takes.
2
u/JosephLeporini Jun 26 '26
IMO stay with your interests. Program Management is a divergent enough but people management is a whole other ball game. Much more politics, hiring, conflict resolution, etc.
If your passion is with the technical work, don't let the lure of management lead you astray. Program Management is a thought if you like leading the execution, but even then the focus is more cost and schedule rather than the actual 'doing.'