4 ms·
> These sorts of bizarrely complex and specific code challenges would at least serve to greatly reduce the number of resumes you have to review. So that is one
by AnthonyMouse 3y ago
> These sorts of bizarrely complex and specific code challenges would at least serve to greatly reduce the number of resumes you have to review. So that is one upside. Unfortunately what that selects for is probably not as obvious as it would seem as many of their candidates would spend that full week on the problem and I wouldn't apply for fear of a workplace culture that values their employees time that little.
It also adversely selects for something else.
In general it doesn't matter what specific technologies someone has used in the past, if they do the same thing. When you hire someone their first few weeks/months are going to be less productive because they have to learn your internal systems and even if you use AWS and they've used AWS, that doesn't mean it will be the same subset of AWS. Whereas by the time they've been there a year they'll have learned the relevant systems regardless of whether it's cosmetically different than the one they used before.
Selecting for the exact set of technologies your company currently uses is going to filter out attractive candidates. Worse, it selects for a monoculture. The last thing you want is to spend two years building something in Golang that exists in the Rust standard library because none of your engineers are aware of that.
And it's simple enough to ask the same question without explicitly specifying specific technologies.
- deleted 3y ago[deleted]
- gafferongames 3y agoIf somebody applied, and had strong opinions about a particular stack or approach, I would offer that they could choose to use their existing stack to solve the problem, if they wish.
- cryptonector 3y agoDo you review their submissions? Do you use the problem to probe the applicant's thinking? Your blog's focus on the details of the task make it sound like you're more interested in using the task as a filter than anything else, but surely there's more to it.
- gafferongames 3y agoThe problem is usually solved in tandem with myself or another full-time engineer. We offer hints and use it to watch the candidates thinking. The best candidates usually surprise us with their solution. Do we use it as a filter? Only to the extent that it filters out candidates who don't want to put in the work, or who can't actually code.
- gafferongames 3y agoPerhaps it also filters out candidates who want to rewrite everything in rust.
- cryptonector 3y agoThat's pretty funny. ISTM that now that you have HN commentary you're thinking a bit more expressly about what you're really trying to achieve with this interview question.
- gafferongames 3y agoTo be clear, this is actually a historical interview question that we've used successfully in the past. We're no longer hiring for this specific role, but I figured writing a blog post to share the solution to help people who for one reason or another, find themselves needing to implement a highly scalable UDP backend, they would now hit this article and at least have some pointers about SO_REUSEPORT and so on as well as increasing socket send and receive buffer sizes, ulimits and so on. btw. This question actually comes out of a core part of the Network Next backend, which was problematic for us and a thorn in our ass in various ways over a period of 5 years. It took us an extremely long time as engineers not familiar with everything needed to solve this question, to correctly solve it and scale up past 25M+ clients. As such it feels like information worth sharing, after all is said and done.
- cryptonector 3y ago