3 ms·
I've hired maybe 30 to 40 people over the past 15-20 years and interviewed atleast an order of magnitude more. I don't claim to have things figured out but I c
by chollida1 10y ago
I've hired maybe 30 to 40 people over the past 15-20 years and interviewed atleast an order of magnitude more.
I don't claim to have things figured out but I can create a list of things that owrk and things that don't work.
Things that work:
- white board interviews, they let you get a dialog going with the candidate,
- take home work, they let the candidate work at their own pace
- showing work samples, whether that's a hacker rank type thing or github repo or open source work that you use.
Things that don't work:
- white board interview, some people just aren't good at them and they don't map well to real world work
- take home work, its insulting to candidates that you expect them to do something on their own time without pay
- showing work samples, github repos, etc. To easy to fake or take others work as their own, some people don't work on open source-able code, etc
Hmm, so we can establish that no matter how you interview you'll cut out some good candidates. I think we've all come to the conclusion that there is not global maximum on how to hire. In my opinion, you're really just going to have to pick one option and stick with it.
As an aside, as a candidate that kind of sucks, if you don't like white board interviews then you're probably not going to work at a company like Google, Microsoft or Facebook. Your choices are to accept that you won't wokr there or to get better at white board interviews.
Well then we could start by looking at what really successful companies do.
The worlds most successful hedge funds tend to not allow people to really apply, instead they look around for who is doing great research and then reach out to them.
Now its easy to start by saying this isn't applicable to most other companies and you'd be right, your company probably can't have their pick of MIT professors, but it does open up an interesting line of thinking.
What are you looking for in a candidate and how do you find people who are doing great work in that area.
Honestly, I think finance has this area figured out better than tech does. They either hire new grads by doing very heavy university recruiting or they hire from competitors.
In finance the saying is that by the time you are 30 you don't need a resume anymore as wall street is so incestuous that everyone knows everyone else. You are only 1-3 degrees of freedom away from any other person, which means that to hire someone, I just need to pick up a phone and ask the 5 people I know that the candidate has worked with to see if a candidate is worth hiring.
- mrfusion 10y agoCan't you tell if someone is taking someone else's work as their own? It seems like they wouldn't be as familiar with the code and wouldn't be able to explain why things are done certain ways. I feel like I'd be able to tell.
- wapz 10y agoIf they show you a mid-sized project it would be very hard to look at it and have a better understanding than someone who intentionally ripped it off and read up on it themselves. That being said, I'm sure if you really grilled them on specifics you might be able to catch them off guard. The problem though is that is showing that you don't trust them from the start as opposed to showing them that you are interested to see what kind of coder they are. I would leave an interview if the interviewer seemed to only be asking questions to throw me off intentionally (I've done it once before).
- zerr 10y agoWhat about discussing past experience, previous projects? Are you unable to detect if the candidate is lying/faking? Additionally, if unsure after this discussion, what about proposing small, relevant to the job paid project? Can't you afford this?