News for hackers. Stuff that matters.
Re:A technical software engineer career? by AnimalMuppet on Friday February 26, 2021 @06:20PM (#26281015)
Here's some words. The "wisdom" part may be in the eye of the beholder ;-)

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.

There are no comments on this comment yet.