A technical software engineer career?
Yesterday, I had my year review and its the first time I've felt "stuck". I got a normal 2-3% raise, but my manager said to really grow my career, I need to stop working with so many projects and start focusing on a single project, by leading a team or becoming 'known' for something that directly effects the companies bottom line (to get "name recognition"). Before the review, I saw my year as stellar. I worked on many projects, mentored younger engineers in many technologies, and never missed a deadline.
This review caused me to rethink everything and where my career is going. In my mind, being a valuable member of various teams around the company is how I get name recognition, but, it seems, depth is more valued at the company than breadth.
About me:
* I love technology and learning new software technology * I don't see myself as a manager or someone that has to spend more time in meetings than "in the code" * I have a bad case of imposter syndrome and have felt burned out many times over the past few years * I'm introverted when it comes to working with big groups, but thrive when I'm working with a smaller team on a day-to-day basis
I haven't been on the market for 15-ish years, so I'm not sure what's "normal" these days. Is this sort of mid-career ceiling normal? Is it even possible to stay in a tech role and still climb the career ladder? I realize at some point, I need to go test the waters and see what I'm worth on the market, but I keep finding reasons to stay on my current path due to not having the time to prepare myself for the interviewing process. Any words of wisdom would be greatly appreciated.
1. It is possible to remain a technical (non manager) software engineer for your whole career. I'm 59, and I'm still a programmer, not a manager. But it gets rarer. You need a company whose mental model of software development has more options than "junior code monkey", "senior code monkey", and "manager". Those companies exist, but they aren't on every corner.
2. For you to continue to make more money, you need to be more valuable to the company than someone with 5 years experience. You do this by knowing more than the younger people, by designing better architectures, by not writing as many bugs, by not starting down as many dead ends, by not writing as many maintenance issues. You can do this while still not working as many hours as the younger people. Bonus points for being able to coach the younger developers and help them also become better.
3. When searching online, the job titles you're looking for are "lead software engineer", "principal software engineer", and maybe "software architect". But "software architect" is also used for someone who doesn't write code and doesn't mentor, depending on the organization.
4. You didn't say what kind of programming you do. Places that will let you continue to be technical are somewhat more common in embedded systems, and in defense. But that may not match what you do or where you want to be.
5. Don't "prepare yourself" for the interviewing process, except for writing a stellar resume. Don't grind leetcode for 3 months. If you're interviewing for somewhere that you hope will actually value you as a technical contributor, and they judge you based on algorithms that you could look up instead of wasting months to memorize, then you don't want to work there.
Quite frankly I would kill to be empowered to focus on one impactful project.
If your manager is unable to see that, it's time to find one that can.