Jobs like presales engineers have higher salaries than developers, require 15+ years experience (dev preferred) and excellent soft skills.
To be clear, I've certainly met people in their 20s that have senior-level ability, but they are by far the exception.
In fact, the 6-8 years of experience you quote is far higher than I would have guessed if you asked me when the average company (incorrectly) starts handing out "senior" titles.
Move to a market where your skills are in high demand and focus on middle/business and back end development. Or better yet, embedded systems development.
I've been at this for 25 years and IMO, the further down the call stack you go the more your cumulative years of experience are an asset.
This doesn't mean you can stop learning new tech, it just means the trends in those lower layers seem to be more sustained and of a longer duration.
Given your struggles to get a job and your very valuable experience, what's holding you back from going as a contractor / setting up your own shop?
Heck, to the right client, that one i860 or C80 programmer might be worth gold. Either that, or just do a highly competent job at embedded programming generally.
Can't afford to live in the US anymore but Mexico is working out pretty well.
Joining a bootcamp makes it look like you are new to the field and will settle for an entry-level salary. This is a very extreme solution, but might help you solve this problem for several years.
I feel bad for saying this, but my advice is to dye your hair, join a gym and take some years of your Facebook profile.
Try to save some money to buy a car to do Uber, start a small IT consulting firm or get a job teaching. Most people will advice mild patches but they dont know what it's like to run out of money. I feel your pain.
Being somewhat older than you, but bored, I think about taking up the oar again. My problem doubles down on yours in that my background is all in products with an expensive hardware component or workstation software, neither appears to be a growth industry.
Aside from the inevitable well-meaning advice to become some sort of 'project manager', etc. I wonder if it makes any sense to hit the .gov job markets at all.
Has anyone done that at an advanced age?
TLDR; I believe a lot of people mistake price discrimination as age discrimination.
Long version: Let's say you need some code monkey to slap together go or rust services. Well, sure, you get a lot of people applying with 25 years experience, you also get a lot of people applying with 5 years experience.
Now here's the rub, it's highly unlikely that anyone's been coding go or rust services for 20 years in any case. (To be honest, it's even unlikely that anyone's been coding go or rust services for 5.) So any of those applicants, as long as their references check out, will do.
Which salary do I want to pay?
If I have a low level, quasi hardware layer service that I need coded in C or C++? Fine, yes, experience matters. It matters a lot in those instances, and I'd be foolish to hire some kid to do that. But there is less and less of that kind of work. (Flip side being that such work is more and more critical.) The dirty secret of the tech industry however, is that most work is just CRUD equivalent stuff that could be satisfactorily accomplished by any warm bodied techie. So it just makes no sense to pay more for those warm bodies.
> ...the dirty secret of the tech industry however, is that most work is just CRUD equivalent stuff
No.I see this a lot on HN, the idea that "CRUD" applications are trivial, but it's a myth. It simply is not true.
I think folks are just extrapolating from "Pet-shop" or "Northwind" examples that they've seen in tutorials/docs and assume that that is what, say, enterprise developers actually do at the same level of complexity. It's not and it has never been the case.
When I was a team lead, I wouldn’t overpay for a crud developer.
I call myself an “enterprise developer/architect” on HN for context - meaning I don’t work for the cool hip startups but let’s call a spade a spade, I’ve spent the last 10 years working on yet another software as a service crud app or bespoke internal apps. Yeah I spend some time in meetings, dealing with “cloud native” infrastructure and I can hold my own up and down the stack.
Nah, it's true. For the average small to medium size company, CRUD apps are mostly "plug library A into framework B, with a dash of glue logic" and you're done. The most difficult part is the yak-shaving needed to get things to work together.
Things like embedded systems or scaling to FAANG levels are much more difficult.
This is a common misunderstanding: yes, Rust is new but prior experience with everything else is not capped at 5 years and it matters a lot. Over my career, I’ve had to fix or replace a number of those “any warm bodied techie” apps where they had incorrect results, security issues, unusable performance, etc. because the developers had been marginally proficient in a popular tool but lacking more general skills and, most importantly, the ability to recognize that they were out of their league.
Our job was his first interview in a year.
It always sticks out as an, "Oh REALLY?" But without talking to the candidate you never know if it reflects poorly on their knowledge of their own limitations, or is just a sign they happened to work for companies with title inflation. I've seen both.
3 years after that, I went to work for a company that had the same thing happen and now I'm a 'Technical Lead / Software Architect'. I didn't choose the title life, the title life chose the shitty companies I worked for :(
I always specified entry level, intermediate, etc, but as times get harder, what you start to realize out here in flyover country is that everyone is applying for all positions. They don't really care about the title or labels. (At least, I suspect it's because times are getting harder? I don't know of any other reason highly experienced people would be applying for some of these kinds of positions.)
You know, that could be. Dunno why you got the downvote so here's an up.
Offshoring of manufacture probably has something to do with the dearth of work. Development was bound to follow mass production.
On the other hand, when people who are already in their 50s post about this topic, they are saying things like, "My phone interview went really great and they were impressed by my skills, but when I went in their attitude changed the second they saw how old I am."