3 ms·

I think it would be interesting to ask a candidate what question they normally ask when they conduct interviews, and have them to walk through the problem. Has

I think it would be interesting to ask a candidate what question they normally ask when they conduct interviews, and have them to walk through the problem. Has anyone here tried that or heard of that being done? I think you could potentially learn a lot more from that than you could with your own problem. First, there would be a lot less stress on them since it would be a problem they're presumably very familiar with. If they do a terrible job coding it up, well, that's a super clear signal. Second, stuff like how well the do setting up the problem, what kind of problem they choose (is it some generic Leetcode problem, or something they came up with themselves), what they look for in a good solution (just that it works/that it's over-optimized/obeys some arbitrary style standard/etc.) would all provide a less clear signal, but still useful information, especially regarding seniority.

LanceH 7y ago
That's such a loaded question, though. It is completely open ended. Will they be judged on the difficulty of the question? Their ability to answer it? Is it even emphasizing the right area for this interview? I strongly believe the candidate should be given every possible direction on what they are being judged on. I'll ask, "What are some of the things you look for in a code review?" If they hesitate or seem unsure about how to answer, I'll help them out with "What are some of the things that will get a PR rejected?" From there I try to open it up to a conversation rather than getting them to list the "correct" five things to cover in a code review.
pmiller2 7y ago
I couldn’t technically answer that question. My company uses a structured interview process, and all our questions fall under NDA.