Average job posting
Average job posting
Have deep experience in 3 different job fields and, in 2 years, learn 5 languages.
You're viewing a single thread.
Most people don't realise this but it says "what we're looking for" not "our minimum requirements". And even when they do say they are minimum requirements, they aren't really.
Whoever gets this job is absolutely not going to have all this. You can still apply.
That said it doesn't seem totally unreasonable. I have used all those languages and have at least medium understanding of them (haven't written any Go or Java for a while).
I've used MySQL and Postgresql, and Mongo mercifully briefly.
I've used some of the AWS stuff. Enough to bullshit about the rest.
I haven't ever really designed a fault tolerant scalable system but I could definitely bullshit about it.
You don't need to get 100%.
Bullshit rarely passes technical interviews at places with low turnover.
I've done some cloud stuff on AWS and GCP and thought I knew enough to pass interviews, then they started asking me about stuff I hadn't even heard of anywhere I'd worked.
Started a new job 3 months ago, 80% of our stack/frameworks are technologies I've never heard of before. Tekton, Firestore, Cypress, 42Crunch, Conformance, Cloud Functions (I think that's just GCP Lambda), some front end testing frameworks I don't know (more of a backend guy though I know raw JavaScript/TypeScript, HTML, and CSS really well from back in the day), Hoppscotch instead of Postman for some reason... and other stuff I'm forgetting now.
I thought because I'd written applications that ran in a cloud environment and understood Jenkins, I was all set. Nope. 28 years I've been doing this and I still feel like a newbie outside of the Java web services ecosystem. And it doesn't matter how good I am in that arena because the code is shit almost beyond repair. Half of our tools are flat out being lied to. Our endpoints are written to detect our testing frameworks and just respond with 200 and a blank payload. Our Swagger is useless because everything returns Result<?> so you can't see the DTOs because 42Crunch gives like 600+ errors because of how garbage the API is written...
Man, I drifted there. Point is, you need to know enough to get the job in order to bullshit your way into it.
My secret? I'm in a high turnover position in the Midwest market (not competing with the glut of tech workers in major hubs, nor drawing their kind of pay) and the technical interview was pretty laughable. Now I have to try to prove myself and get hired in as a full employee rather than contractor. Then I'll have some job security and maybe a path forward that isn't just keep taking Sr. Dev, Team Lead contracts.
Yeah AWS has so many solutions, when quizzed about a tool I haven't used, I honestly say "can you describe it's use? I've built a lot in AWS/gcp/azure but haven't used that tool. I'll describe how I'd do it with tools I'm familiar with". Normally goes over well.
For example, if they really wanted amplify experience for some reason, and I would instead describe how I'd set things up with ec2 / ecs / fargate, etc.
Yeah but these show up somehow at some point in the tech interviews rounds and if you fumble to strengthen your experiences you will get rejected