Almost everywhere in the Midwest, except Chicago perhaps.
Unless your remote working, low cost of living doesn't come without a big catch.
It boils down to simple economic rules. If you're good at developing software, there aren't a lot of people like you looking for a job and the market has a high demand for your skill then you are probably doing something wrong if you're not earning well into the 100's or higher (if that is what you're trying to optimize for).
I've been doing embedded/firmware engineering in this area my entire career and, right now, 100K is typical for a senior position with very few positions available over 125K. The only way to go higher is to consult.
Perhaps it's the glut of ex-Moto/ATT/Lucent/Tellabs people floating around. I dunno.
I knew a guy who was about 50, brilliant, brilliant engineer working for one of the big IT players. Well respected and trusted advisor to many customers. He got vaporized in some big restructuring that hit his division.
Because of non-compete and what he did, he was basically out of work for almost a year, and was stuck in career purgatory for a few years doing random contract work.
Anyone older cut their teeth on assembly or C, NetBIOS, and CLI and may or may not have stayed current afterwards. Consider that the industry was a lot "older" (just look at old pictures) until those technological shifts happened and shook out all the people that learned in the 60s or 70s.
If something like quantum computing or a parallel functional computing revolution or VR/augmented interfaces or anything else grossly disruptive to current development practices comes around, we're all going to be in the same boat: learn or die. Getting through that is not so much a factor of age as the circumstances around age and one's willingness to keep at it.
Is there something wrong with these in that they are not useful anymore? I see a lot of jobs that require these, and I think they're still very relevant. Actually, I'm relatively young and love that stuff and work with that stuff... I'd love to work with someone who's been working with those for decades, experience really does show.
IBM was particularly brutal about this stuff when they were eliminating people still on the pension plan.
However, in any case, the reality is that for small companies, for all but the most senior and/or desired employees (and even then), a potential non-compete issue just isn't worth dealing with. Doesn't matter whether it would ultimately lose in court, you're just not prepared to go there. That's the real issue with non-competes.
I've worked for a small firm and a candidate with even the most peripheral non-compete was just a non-starter.
Where is it that late-career engineers are barely pulling in six figures? Don't get me wrong, it's a lot of money (3x mean personal income in the US, and ~1.75x mean HHI, give or take), but I'd expect most senior folks in any engineering field to be in the mid 100k range if not pushing 185ish.
> Time and again, he says, employers seem to lose interest after he answers a question that they ask early on: “What was your last salary?”
Your last salary has absolutely no bearing on what you are worth or what the market rate is for the position for which you're applying. You have absolutely nothing to gain by sharing a previous salary.
> A survey by AARP last year found that of job seekers between 45 and 70 years old who found work after a spell of unemployment, nearly half earned less than before.
I don't think this is that surprising, is it? If I make $100k and lose my job, often with little notice, I will take $80k. If I make $100k and leave of my own volition, it's unlikely I'll entertain anything below $110 or $115.