Hacker News new | ask | show | jobs
by fridif 1808 days ago
The only algorithm for hiring someone should be as follows:

if (candidate.canCode && !candidate.isAsshole) return true; return false;

2 comments

I agree with you, those are absolutely fundamental. The bar should be set higher though, especially for senior engineers.

https://benjiweber.co.uk/blog/2021/04/10/dont-hire-top-talen...

This is why I stress the importance of culture. I got into engineering because I loved coding, I loved problem solving, I loved writing programs and making things happen on the screen. It's so easy for the team sport aspect of software engineering to become a blindspot if it's something you're not interested in.

What about candidate.can_work_in_a_team? Or follows_requirements_instead_of_doing_their_own_thing? It's a huge problem and there are so many difficult personalities out there that one has to look at "culture" and personality.
you clearly can not work in a team as the original codebase was in camel case and yet here you are pushing snake case. /s
are your requirements written as test cases? cause if so, there's no arguing about if the work is done or not

(except for performance requirements, sonar qube, etc)

> What about candidate.can_work_in_a_team? Or follows_requirements_instead_of_doing_their_own_thing?

In a way, all these are part of `!candidate.isAsshole`