3 ms·

I don't typically whiteboard. I'll write the prompt on the whiteboard, but otherwise it's a tool. The candidate has a computer, either their own or we provide o

I don't typically whiteboard. I'll write the prompt on the whiteboard, but otherwise it's a tool. The candidate has a computer, either their own or we provide one, with whatever tools they requested or want to use. Yes, plenty of candidates with otherwise amazing track records can't code comically simple functions (not dumb questions) together, with tons of help and hints and direction provided. They can't articulate their thought process, can't describe what they're doing, can't ask for help or get combative or aggressive or entitled. The question is entirely not the point. It's everything else that is signal. Could I work with this person? Could I give them a task and have confidence?

gopher_space 5y ago
Think about what your interview process would look like if it was a normal day at work. You show up out of the blue with a task that isn't connected to anything the org does and with all the decisions made already. I cannot search the internet, but you do not explain why. You sit down across from me and stare.
- xyzzy_plugh 5y ago
  You're describing something else. In my interviews you can use the internet. I don't stare, I'm mostly taking notes and answering questions, either listening to the candidate explain things or explaining things. No decisions have been made. I describe a problem, we solve it together. Just like we might on the job.
  - jjeaff 5y ago
    I can't do something as simple as empty my bladder while someone is watching. I certainly can't code something complex with someone watching me. Luckily, I have never had a coding job where I had to be watched while working.
gmac 5y ago
plenty of candidates with otherwise amazing track records can't code comically simple functions Sadly, this rings true. In a non-whiteboarding context I’ve sometimes asked JS/TS candidates something that I originally though was a nice easy, practical sort of algorithm question: how would you find the intersection of two string[] arrays? Even with plenty of hints probably the majority don’t get beyond a nested loop (sometimes they progress to [].filter and [].includes, which just hides it).

gopher_space 5y ago

Think about what your interview process would look like if it was a normal day at work. You show up out of the blue with a task that isn't connected to anything the org does and with all the decisions made already. I cannot search the internet, but you do not explain why. You sit down across from me and stare.

xyzzy_plugh 5y ago
You're describing something else. In my interviews you can use the internet. I don't stare, I'm mostly taking notes and answering questions, either listening to the candidate explain things or explaining things. No decisions have been made. I describe a problem, we solve it together. Just like we might on the job.
- jjeaff 5y ago
  I can't do something as simple as empty my bladder while someone is watching. I certainly can't code something complex with someone watching me. Luckily, I have never had a coding job where I had to be watched while working.

gmac 5y ago

plenty of candidates with otherwise amazing track records can't code comically simple functions Sadly, this rings true. In a non-whiteboarding context I’ve sometimes asked JS/TS candidates something that I originally though was a nice easy, practical sort of algorithm question: how would you find the intersection of two string[] arrays? Even with plenty of hints probably the majority don’t get beyond a nested loop (sometimes they progress to [].filter and [].includes, which just hides it).