4 ms·

You're right. If someone thinks that writing code for an hour is a tedious act of desperation, they are not the right candidate for us.

• abbasmehdi 15y ago
  Boom! goes the dynamite... Loved your response. What exactly are you testing? What are you looking for, traits wise, and which aspects of the test reveal the said traits? I am not planning on applying, but am I just interested in learning more about your methodology. On the surface, it seems way better than those silly "how many potholes in America" or those memorizable algorithms.
  • whit537 15y ago
    :) With the first round of hiring I looked at how far the candidate got in fixing the bug. There was a workaround and then there was a fix for the root cause. If the candidate found the workaround quickly then that was equal to fixing the root cause less quickly. Almost no-one actually fixed it though, so mostly it was a measure of progress. How efficient are you at developing hypotheses and testing them? How good are your hypotheses? Now in this round I can't cross-compare as easily, so I'm expecting it to be more subjective. Basically I'm looking for people that I have a hard time keeping up with.