> FAANG experience
Probably the reason. Most companies need people with experience in more than just one layer of a stack. Hard times for those who cant own a full stack, unfortunately.
Probably the reason. Most companies need people with experience in more than just one layer of a stack. Hard times for those who cant own a full stack, unfortunately.
It’s proving hard to sell generalist-ness to recruiters this round. They often lock on to the most recent specific domain I worked in. If anything, they seem to be filtering for people with very specific experience in a specific layer of a specific stacks - because they are getting so many applications, they can be very choosy.
If you can, look at new jobs/companies as opportunities to get deep experience in a new area since over time, stuff you're good at now will sometimes go away.
And cover letters are really good for this sort of thing as it lets you lay out some specifics that make you the type of person who can really help them out.
I realise this sounds basic, but that's the point: almost all of those things are everywhere. Bury yourself in a tiny slice of one of those things and you've become un-or-over qualified for most of the market.
My self esteem and confidence is at an all time low. It is soul-crushing to have had a brilliant career and get barely 1% response rate. I can't only blame it on my CV being terrible (went through half a dozen iterations already)
You can’t take things personally, focus on the process and just understand that things are outside of your control. You’ll get bites eventually but it’s a slog.
The problem though is assuming that the majority of jobs are with small companies. Although 99% of US businesses are SMBs, only 45% of employees in the US (from quick Google checks) work for SMBs. So the majority of jobs are at large companies and I don't think FAANG would be so much a penalty (except for that you might have compensation expectations that don't fit these companies).
"We need two or three seniors who, between them, can handle the fact that our cloud resources are split between AWS and Azure 80/20, who understand security well enough to enforce least privilege for users, can write reliable if inelegant code in bash, python, golang and - when we have embedded stuff - lua. We'd also like people to be cost aware since we aren't made of money, and to be able to take ownership of CI, observability, logging, k8s in the form of EKS, a few VMs, and some difficult to change legacy stuff. Plus, provide the devs with a sensible local environment to work in that is as prod-like as you can make it, mentor a junior or two, wrap everything into some kind of infrastructure-as-code setup, present options to architects who are sometimes operating outside their field of expertise, and run the standups a d retros when your manager is on holiday"
Or as they would call it, "devops".