Hacker News new | ask | show | jobs
by Izmaki 2760 days ago
When companies list many seemingly silly requirements (example, why do I need experience with database x, when I can pick it up in less than a week?), at least two types of candidates will be likely to apply: those that know all of it and possibly more, and those that don't check off all boxes but had the guts to attempt to convince them to pick them anyway.

The one type is going to fit right in and be ready to contribute quickly. The other has the drive to get up to speed and further. Both are much desired people.

4 comments

I can tell you right now that I do not want to hire the people that show up to my interview without checking at least some of the boxes, guts or no.

It’s a (senior) programming job, why are you here if you have barely 2 months of experience...?

For sure you need them to for sure meet certain requirements.

My current job was listed as full time (Entry/mid level) but I'm a student and in my phone interview told them that - guess they wanted me anyway. My biggest value IMO is that I've dabbled with a lot of stuff. Okay I haven't worked on a personal project in Django, but I'm at the point where the exact language/framework is semi-irrelavant. I was confident I could, and was able to be semi-fluent with Django for example in a few weeks (only 25 hours a week).

My point is that what GP is trying to say is more about "Oh we listed postgres but they've only used mysql" if the person is motivated they should have no issues picking up postgres

They shouldn’t have listed a database if they don’t require a specific vendor of DB for operation.

Jusging by what you are saying you’d probably have a problem telling the two apart, while they will have many differences when run at scale.

why do I need experience with database x, when I can pick it up in less than a week

You can use a serious database like Postgres or SQL Server or Oracle for 5 years or more and still not see more than a fraction of it or its surrounding ecosystem. MongoDB sure, you can know everything you need to know in a day.

By “use” you mean is when that database size fits in a single page of memory, right?
Maybe an unfulfillable set of requirements is the point? That way they've got a bulletproof reason to reject you, and if you do get hired it's negotiating leverage
There are way too many of the latter for the signal to be important.