3 ms·

This point doesn't really matter but 200+ is a small company. But leading 15 developers is a nice pin in your hat. I wouldn't apply for senior roles. I'd look

This point doesn't really matter but 200+ is a small company. But leading 15 developers is a nice pin in your hat. I wouldn't apply for senior roles. I'd look for Principle, Architect type roles. Something that acknowledges your leadership skills but is also technical. I think a 'Senior Developer' role would definitely be a huge step backward in terms of career. Personally I find the long term career aspects for someone that can manage a few dozen developers to be much MUCH brighter than a senior developer, so I have a hard time understanding why you'd want to switch. I mean, your next role could be a VP type role where if you are smart with your $$ you can go and be whatever you want after a few years...

sleenaidor 11y ago
Thank you for your response - I agree with what you are saying. > so I have a hard time understanding why you'd want to switch The main reason is that I want to write code and build stuff. Most of my current time is bug fixes (last point of escalation), estimates, meetings and managing people, and the odd "new feature" I develop when everyone else is busy. One of my main strengths is that I can get to the bottom of bugs really quick and provide (what other people call) "elegant" solutions but I think I'm falling behind on actual development skills due to lack of time (I see what other developers write on the internet and I realize that I'm waaaaay behind). I'm aware that from a career perspective it doesn't make much sense and that is why I asked this question in the first place. I do want to write more code but I 've worked very hard to get where I am now and I don't want to make a bad call.