5 ms·
We're a 70 employee B2B startup in NYC that uses something similar. We have a set of problems that we actually solved as we were building out the company - we
by mason55 13y ago
We're a 70 employee B2B startup in NYC that uses something similar. We have a set of problems that we actually solved as we were building out the company - we now give them out as take home interview questions (different questions for different roles). Instead of brain teasers it's testing for real world coding abilities that apply to the job the person will be doing.
Assuming the code comes back ok we then use it as the basis for one of the interviews on site. I usually discuss design decisions and then make some changes to the requirements to see how they react.
- danielweber 13y agoDo you measure to see how well this works?
- mason55 13y agoWe honestly haven't hired enough engineers to make any sort of statistical measure on it but anecdotally it seems to be effective. We've yet to end up with a false positive and I know that we've hired at least two engineers who are awesome that I don't think we would have hired based solely on an "algorithms at the whiteboard" interview. Plus our engineer-time-invested per declined candidate is way down. Rather than spending 60 - 90 minutes watching a candidate flounder at the whiteboard we can axe them in a 2 minute code review.