Hacker News new | ask | show | jobs
by SatvikBeri 6 days ago
Every interview method has some glaring flaws, and I find you mostly have a choice of which flaws you pick.

On my current team, I care a lot about the ability to write fast code. The most important part of my process is a take-home designed to take 2 hours where the main goal is to solve a relatively easy problem as performantly as possible. Answers have varied from 0.2ms – 50ms.

Take-homes have some obvious disadvantages, but overall I find they're better at finding the people we're looking for than just about every other method. But I'm at a small company, hiring for a fairly specialized team. If the situation was different (e.g. I needed to hire 50 people/year) I'd use a much more standard process.

1 comments

Hmm thats a pretty interesting variant. I dont think it would apply directly to our team, but I like the potential playground it gives for both coming up with solutions as well as being a kickstarter for convos on alternatives.