Comment by move-on-by

I think the staff role varies a lot between companies- so take this with a grain of salt.

> Because I've been out of the daily coding game for three years. I know what I don't know. I need time to rebuild those muscles - to remember what it's like to be in the weeds of production incidents at 2am, to own features end-to-end, to debug race conditions that only show up under load.

I think you’ll find that your management skills transfer easily to the staff role. Staff, at least in my org, has a lot of cross over between management.

Maybe you are given a large ambiguous task and it’s up to you to solve it. You don’t have a team, but you can gather requirements- scope out the work and depending on timelines, you’ll get people assigned. Lots of project management aspects.

Or maybe a project already in progress is going off the rails and you get thrown in the mix to get things back on track. You need to identity why things aren’t going as expected. Is it scope creep? Was it bad estimates? Is the design not working out? Maybe the team just doesn’t have the necessary skills? These are all things that I would expect a staff engineer to be able to identify. It’s a nice option for leadership to be able to add a peer to an engineering manager into a team to get another viewpoint. It would certainly be awkward to add another EM to a team, but a staff can provide assistance without the awkwardness.

> And honestly? I want something to work toward over the next three years while my kids are young.

Well, I have young kids and I can’t say I disagree with you there. I’ve been on this horrible project the past 3 months and I’ve found myself daydreaming of going back to Senior - or just switching companies all together.

Anyways, staff role varies a lot. From my viewpoint if you are a half decent EM, then those skills should transfer just fine for you to be a half decent staff engineer.