TheDudeAbidesMan in
Software Engineer
SWE with 2.5 YOE, need career advice
Hi all,
I am a senior software engineer with an established bank in the midwest, and have 2.5 YOE thus far.
I'm currently sitting around $105k base, with ~ $5k bonus.
I originally worked in finance and made the career change to SWE a few years back, so I'm still relatively "green".
I'm 30 years old, so I'm concerned I have a lot of time to make up for compared to other candidates who are new grads and have more projects than I currently do.
I've come to realize that my current position is mostly maintaining established applications, and I'm really not doing much coding.
All that said, I've recently taken up studying Data Structures and Algorithms again, and doing Leetcode to prepare for interviews.
I'm not gunning for a FAANG by any means, but I do aspire/hope to make $200k-$300k at some point in my career.
Is there anything I can be doing specifically to make up for the lost time in regards to earning potential?
Does anyone have any advice as to what I should be studying/reviewing/learning in preparation for interviews?
Thanks in advance.

6
3485
Sort by:
eightysixerSoftware Engineer
I sympathize with the "lost time" thing. I started my SW career at age 26, but didn't crack $100k until 34. I know inflation, etc. but you're doing better than you think!
Anyways I think you have the right idea. Switch jobs every 2-3 years to get a diverse background of experience, and to elevate your pay. Salaries tend to plateau around 10 YOE, that's the marker for where it makes more sense to find a job you like long term and do senior+ or staff level work, because the large payoff of changing jobs gets a lot smaller IMO.
You can shortcut this by jumping to a larger tech company, a FAANG, or a VC-backed startup (levels.fyi is great for checking if a prospective company is worth your time, at least for big companies). The startup risks are obvious, these are not stable jobs. The FAANG/big tech risk is they are so large, you may end up doing extremely niche work that doesn't translate well anywhere else, and a layoff leaves you hard to employ.
Another shortcut is overemployment with remote jobs. Again, there are risks, but if you avoid the risks it is very lucrative.
At your level, basic leetcode/DS&A will get you hired into a new role. In ~2 years, interviewers will start to expect you to do high level system design. The best way to get ahead of this is hands on work, so make sure each new role is also expanding the scope of the problems you're working on (subsystems in a component -> a whole component -> multiple components). You should also make sure it becomes easier to draw a direct line from your work to a positive revenue/cost impact on the company.
If you score a big 50% raise or similar in your next role, take the opportunity to max out your 401k contributions. Ultimately "making up for lost time" is about living comfortably when you're done working. Some employers with middling pay might have amazing 401k matches too so don't sleep on that (best I ever had was a 12.5% match, the pay sucked, but I might be back).
Final note is nobody is going to judge you on your age/appearance compared to your level. I've worked with career changers in their mid-50s. It's never too late to start a software career if you have the drive to make it work.
3
Unlock by Signing Up!
Create a free account to view all comments, posts, and more!
About
Public
Tech
Members
736,430