>Bob doesn't want to lead or be a manager,
pretty sure at amazon or any "big tech" you get fired for this
SDE I -> SDE II -> SDE III -> Principal Engineer (SDE IV) - you provide technical advisory and strategy across an organization -> Distinguished Engineer/Sr. Principal Engineer etc. (SDE V)
Some choose to stay at SDE III level until the end of their career though since it offers the most freedom to code. You absolutely don’t get fired for this.
This track exists at Oracle and Google. I am not familiar with the others.
There’s a whole book on this: https://staffeng.com/book
I once basically had a part time secretary and it was fantastic. A few hours a week could even be enough, it just frees up so much mental space. It boggles my mind this is not the norm.
It doesn't mean it's a solo project. It just means you have the technical direction and you can let ppl manager to handle ppl side of things and you do almost 100% tech side of work. If you have 0 tech leadership and can only work on tasks assigned to you, you are not even ic4 worthy, that's absolutely ic3 ie ng level.
Again this is more of a feature in big tech where this kind of projects are available
SDE I - can work on clearly defined components of a project assigned to them
SDE II - can work on an ambiguous project with multiple components lead by a technical strategy
SDE III - lead influence and define strategy for ambiguous projects across multiple teams
This person is operating at an SDE II level but is being managed at an SDE I level...it’s time for a promotion. What’s worse is the manager is micromanaging the engineers. Instead the employee needs to be given more ambiguous project level work that aligns with the team/product strategy where they can define their own tasks. Also the manager should consider falling back from managing at the task level, instead helping facilitate at the project (or “story”) level. The fact that the manager is managing at a task level and is unable to find work for this engineer tells me that the team doesn’t have a strong tech lead who is familiar with the team/product strategy and can help mentor/lead other engineers.
In terms of retaining the engineer and making them less insecure about their role, when the manager gives the team member more insight into the team’s strategy and the way that the manager is evaluating their work it helps team members feel more secure in their role. A lot of the anxiety comes from guessing what your manager is thinking and how you are being evaluated and shows a lack of communication between manager and team on strategy, values and performance evaluation. The manager should consider holding weekly 1:1s focusing on these topics.