3 ms·
And with a work sample, how do you know: 1) how well they work with others? 2) how long it took them to come up with the solution? 3) if they actually came u
by misingnoglic 9y ago
And with a work sample, how do you know:
1) how well they work with others?
2) how long it took them to come up with the solution?
3) if they actually came up with the solution themselves
- kafkaesq 9y ago1) how well they work with others? Whiteboard sessions don't tell you that either. Only whether they got lucky, and you picked a problem they already know (so they can breeze through the solution in front of strangers with confidence). Or if they can at least suck it up, and pretend they enjoy this nonsense for 45 minutes (or 4-6 hours, depending how crazy your company is about this stuff) to get a job. 2) how long it took them to come up with the solution? Does it matter? Really now. What matters on the job is did you go the last mile, think about the corner cases and pitfalls, and make sure your solution was cleanly coded and documented for the next guy or gal. Not whether you solved that silly HackerRank problem in 35 minutes as opposed to 45. 3) if they actually came up with the solution themselves This one's pretty simple to sniff out, actually: "So I'd just be curious, why you did X here and not Y?" There's pretty much no way a bullshitter can answer that question.