I'm a bit younger and it may not be the only solution but the one that worked for me was to stop positioning myself and competing for a pure SW dev role altoget

I'm a bit younger and it may not be the only solution but the one that worked for me was to stop positioning myself and competing for a pure SW dev role altogether. In my opinion one of the key strength you get with experience is perspective on solving problem efficiently in a no bullshit way, and more importantly in the business context. There is a limit on how much value a developer can bring by working on assigned stories and tickets, and experience after a few years plateau (and age discrimination start to kick in), but go higher in the chain and suddenly you experience becomes very valuable. I don't know how it is at FANNGs but even there are huge architecture decisions really made by young developers? Most companies burn millions on poorly driven software projects, with layers of useless abstractions and accidental complexity. Execs love when you bring them a working solution no matter how you did it, e.g. the dashboard they are dreaming of all the while the official team and the consulting company that is costing $$$ are stuck in their big-data/blockchain/whatever grandiose project. So I would look either expert small shops, or consulting companies with a career track for experts. Anecdotal but you can have a better time in a consulting company as "the guru" moving from projects to projects every few months than stuck in a mono product company for years.