[AnimalMuppet]

We talk to them (phone screen). If we bring them in, we just talk to them for a half hour about what's on their resume and stuff.

Then we give them a code sample, a single function that fits on half a sheet of paper. We ask them what it does. We ask about ways it could break, corner cases. We ask them what they would name the function.

Then we give them a small coding problem. They can solve it in any language they want. It's not as trivial as FizzBuzz, but it's not very complex. It's certainly not leetcode. We watch them think through how to write code that would do what we asked. We aren't really watching for syntax errors, but if the code was full of them it would be a concern.

Then we give them a small design problem, one that's not all that clear-cut. We push them on some of the corner cases of the design, and watch them try to adapt the design to cover them.

Total time: Two hours.

This approach has gotten us a pretty solid, competent team.

[100-xyz]

Thanks. It sounds like a solid plan.

Out of curiosity, how big is your company? How often do you interview? Approx what % of the candidates get an offer?