Hacker News Reader

Comment by dakiol | Hacker News Reader

> I was told recently that one reason I wasn't shortlisted was because I didn't have 10+ years of experience with Angular 12+. For those who don't realize, Angular 12 was released in mid-2021, less than three years ago.

In my experience those are not the kind of requirements I deal with. I have to deal with:

- Senior software engineer position requiring: knowledge of X programming language + Y framework + sql + git + linux + DDD + TDD + BDD + OS + networking... until here everything OK. But on top of that companies also ask: monitoring and observability (because of the stupid "you build it you run it"), docker, k8s, kafka/sqs/sns/rabbitmq, microservices, aws/gcp/azure, event sourcing/event driven archs, and a long etc.

I mean, what the actual fuck.

View on HN

It's either a job ad because they legally need to advertise it before getting a visa for a specific person they're already talking to, or a silly job ad where they don't get realise they can't pay for someone who actually matches those requirements.

Either way, you may as well just apply. In the first case you won't get an interview, in the second things may get more normal once you talk to the tech people.

Or they’re looking for someone with a few of the listed skills.

I’d be totally on board with job ads saying “the team’s tech stack includes A-Z. No one is expected to be an expert in all of these but if you have experience with some of them or equivalent tech, we could be a good fit for each other.

Depending on circumstances, the ad could go on to say stuff like “we’d love to boost our capabilities in these particular skills” to call out anything that’s an area they want to focus on improving with the new hire, if there is one.

That's not "stupid requirements" the just the scope for backend engineer job nowadays.

Also, you might get the job if you don't match the requirements 100%. There are so many permutations of backend technologies nowadays that pretty much no one has familiarity with exactly the one they're looking for, so they have to compromise.

Hahaha that's so fucking relatable. I saw an ad that was hiring for company X and would prefer candidates that actually been previously working at company X.

> you build it you run it

Huge fan of this model. And fwiw, aside from not being strong with aws but still familiar, I tick all the qualifications you listed and I would expect most of that list to be valid for someone to claim to be a senior. That person should have some experience in nearly all of that. Specific frameworks should allow for more wiggle room if you are familiar with the given language.

The bigger problem is "senior" developers with 4 years experience who don't know half of that and are mostly familiar with crud apps.

A real senior has 20 years and stays away from buzzword tech. I have nothing against tdd but its a techique that is not that popular. Why would everyone have experience rabbitmq. Some might know aws or azure or google cloud or vercel or oracle cloud or 50 other vendor solutions. Why need to know them all or any? These things can be learned and past learnings transferred.

Reply on news.ycombinator.com