Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

30 mins chat with a recruiter who'll try to suss out whether they can afford you, make sure you're actually interested, and check you've got the right to work in the country.

1 hour hiring manager interview the first person who actually understands those acronyms on your CV

1.5 hour technical/coding interview, to check you know how to program

1 hour behavioural interview to check if you've ever gotten into a fistfight about database schema design

1 hour chat with your boss's boss's boss, who feels he ought to have a conversation with someone before approving a six-figure paycheck.

This lengthy and bureaucratic process is vital to ensuring prospective hires have the patience needed to get through all the other lengthy and bureaucratic processes their job will entail.



I appreciate your comment as its intended defense and understand why a committee approach is a CYA risk-assessment measure (which ultimately turns job placement into a popularity contest as technical ability and team desiredata take a back seat/lower weight to fisticuffs assessments by HR).

However, parent commentator mentioned wanting to _go deep_, and needed 4-5 hours to do it, indicating that the typical committee pattern is out of alignment with what they were advocating.

Further, your time assessments are too long. You can assess fisticuffs in 10 minutes along with a background check. Technical doesn't have to be 1.5 hours. Also, 90 day probation policies exist to address as well.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: