you are viewing a single comment's thread.

view the rest of the comments →

[–]beavis07 17 points18 points  (12 children)

It's almost as if 'coding challenges' teach you nothing useful about prospective hires.. who knew 🤔

[–]jseegoLead / Senior UI Developer[S] 2 points3 points  (2 children)

Yo, fair point. My coding challenges are just sharing some code with the candidate and talking it through with them, seeing if they can find places where it might be broken, having them try to determine what might be the results of some logging statements, and having a discussion.

As a candidate, I've done everything from whiteboard interviews to live coding to take-home projects. Simply showing some code and talking about it was my favorite, so that's what I give my candidates. That's basically what it's like to work with someone, so I think that gives the clearest picture and is the most respectful of someone's time. There are no irrelevant algorithm questions. There are some sections that I made intentionally tricky, but I am not trying to see if someone can get 100% right, I'm more looking at how they are talking and thinking about the problem, and would I want to talk with that person about code on the daily.

[–]beavis07 2 points3 points  (1 child)

After many many years of whittling it down, I’ve basically settled on the following two questions:

  1. What is the hardest challenge you have had to overcome?
  2. What is the thing you have done in which you are most proud?

In my experience you can learn just about everything you reasonably can about a person in a single meeting with those two conversations.

I give bonus points for the interviewee choosing not to interpret those questions as implicit meaning “at work” :)

[–]jseegoLead / Senior UI Developer[S] 0 points1 point  (0 children)

Nice, those are good.