3 ms·
And then when you try to design an interview process that mimics the conditions on the ground you get people decrying it (sometimes rightly, sometimes wrongly)
by pc86 3y ago
And then when you try to design an interview process that mimics the conditions on the ground you get people decrying it (sometimes rightly, sometimes wrongly) as too hard, or too long, or whatever.
- red-iron-pine 3y ago"ive been in the industry 15 years, doing this shit is an immediate no!" then you try to get them to explain TCP/IP or fix a for-loop and they're stumped.
- neumann 3y agoSo this. We always give realworld actual mini 'regular day at the office' assignments, and it was a great filter. We ended up giving it a lot because people would ghost or give up after days of (fundamentally bad) work, then the right candidate would arrive and nail it in hours. We had recruiters tell us not to do tech interviews, nobody likes them, etc, but our team was so strong for it. And really, we were mostly testing generics. Use stack overflow by all means, but just know what you are copying and how to modify it!