So what do you ask then? How do you assess the skills of the candidate?
So what do you ask then? How do you assess the skills of the candidate?
If you care about performance and data structures you can dig in, you can ask what bottlenecks they had, what structures they used. I've had a lot of success just asking in the middle something like "why not use a list or vector?" (in C++), the discussion that follows tells me already if this person knows how memory works, how algorithms scale, etc and this are things I really care about in my industry, not just random trivia.
All of this is done as a conversation, I want to minimize their nerves as that just obfuscates the real person I'd be working with.
I get none of that info asking someone to invert a binary tree on a whiteboard.
Building out a great team is more art than science, and you won't ever hone that craft by throwing coding challenges at your applicants - you just end up with a group of people who are a bit more likely to be very good at jumping through arbitrary hoops.