I wonder if it's the definition of "senior" that shifting. From someone well versed and experienced in software development to deep domain experts who happen to have development skills.
10-15 years ago, the advice for anyone was to apply for the job even if you don't fit 100% of the requirements. "It's a wishlist not a requirement list".
At some point in the past,few years this seemed to gave changed. Now you have to be an expert
Some years ago I applied to a government that I thought sounded interesting. It seemed to be a pretty damn good match for my skill and resume. It basically entailed developing a CRUD app to store and analyze fishery statistics. Everything about the job made it sound like it was mostly rub of the mill .NET work. Surely a good fit for me who has done that stuff for a variety of different government and private organization. I got rejected for not having enough domain experience
I'm not sure where they planned to find such a cross-domain expert who was willing to move to such remote, yet high CoL area for the already comparatively dismally salary, but hey, it didnt matter, the agency got gutted a year or two later.
In a similar way I'm reminded of when I first looked into "scientific programmer" jobs. HN swore up and down that they were desperate for developers, and that this was mostly a product of lower pay. The reality seemed a bit different. Nearly every job I saw in that area wanted a PhD scientist who could program, not the other way around.
How many of those postings are real, though?
I wonder if it's the definition of "senior" that shifting. From someone well versed and experienced in software development to deep domain experts who happen to have development skills.
10-15 years ago, the advice for anyone was to apply for the job even if you don't fit 100% of the requirements. "It's a wishlist not a requirement list".
At some point in the past,few years this seemed to gave changed. Now you have to be an expert
Some years ago I applied to a government that I thought sounded interesting. It seemed to be a pretty damn good match for my skill and resume. It basically entailed developing a CRUD app to store and analyze fishery statistics. Everything about the job made it sound like it was mostly rub of the mill .NET work. Surely a good fit for me who has done that stuff for a variety of different government and private organization. I got rejected for not having enough domain experience
I'm not sure where they planned to find such a cross-domain expert who was willing to move to such remote, yet high CoL area for the already comparatively dismally salary, but hey, it didnt matter, the agency got gutted a year or two later.
In a similar way I'm reminded of when I first looked into "scientific programmer" jobs. HN swore up and down that they were desperate for developers, and that this was mostly a product of lower pay. The reality seemed a bit different. Nearly every job I saw in that area wanted a PhD scientist who could program, not the other way around.