3 ms·
I worked in a company which was hiring tech folks without coding interviews. I am glad I left.
by gizeta 5y ago
I worked in a company which was hiring tech folks without coding interviews.
I am glad I left.
- rimliu 5y agoI also worked at two companies like this. Both rank as #1 and #2 best places to work. A bunch of very competent people.
- wdb 5y agoThe company didn't use the three or six month probation period?
- obviouspenguin 5y agoIn my experience, getting a bad hire is worse than not hiring at all. It takes a huge amount of resources to properly onboard a new team member, and then if they are not performing well the work they were doing ends up becoming a liability instead of an asset to the team.
- wdb 5y agoYes, sure but if it's a bad hire. You would dismiss within the probation period, right?
- handrous 5y agoI think part of the problem is that places with coding interviews usually pay better than those without, and the ones with the really painful, idiotic, grueling interviews that everyone hates offer the top pay, so the system ends up sorting all the worst candidates to the companies that don't do "normal" coding interviews. In fact, I think that effect is exactly why the top-paying places do it, because it makes their hiring easier. At this point, if any of them unilaterally drops the hellish, silly, hazing-interview process, they'll be inundated with good candidates they've been excluding plus a shitload of bad ones who'd already been filtered out by the fact that their process is hellish and silly. So none of them will.
- onlyrealcuzzo 5y agoSomeone wrote a really great article for how you should play this as a company if you can't pay the best. Unfortunately, don't have the link. The premise is: you should be aware that there's a large subset of good engineers who aren't particularly great at coding interviews - and you should set up your interview process to select for those candidates.
- handrous 5y agoHahaha, like Moneyball for programmers. I like it.