> It might surprise you but I’m not a young developer at all Have you considered becoming a team leader/scrum master/whatever it's called nowadays? I slipped i

> It might surprise you but I’m not a young developer at all Have you considered becoming a team leader/scrum master/whatever it's called nowadays? I slipped into that role by accident, but found it very fulfilling. I saw my role as shielding my devs from mgmt, so they could deliver, which is all management wants at the end of the day. You still need to be technical, participate in design, do code reviews, maybe do a bit of coding etc, but you aren't slogging it in the trenches/doing the grunt work. You'll have to do more planning, sizing items, distributing work, but that also takes dev skill and dev knowledge. Give it a try if you can. Worst case you can say it isn't for you, and you don't seem to have a problem finding a job. Best case, you might become a great team leader (or even manager if you want to go even less technical), and make a difference for the devs who'll be in a similar situation like yours once the novelty wears off. Team leaders can make huge changes to process, if you can justify them with e.g. hours of engineering saved. Best of luck to you. I know what it feels like when you think you're trapped in one career path because you happen to be good at it, and it's horrible.