5 ms·
We want to see your solution to a problem that we know REALLY well. Does that give you an expectation of the sorts of things that someone new to the problem wi
by onion2k 11y ago
We want to see your solution to a problem that we know REALLY well.
Does that give you an expectation of the sorts of things that someone new to the problem will spot? If so, how do you manage that expectation - eg if the user misses something in their 3 hour test that you only spotted after using the same problem for 6 months, how can you ignore the fact they still missed something?
- danpalmer 11y agoMissing something doesn't rule them out, nothing in the test is a hard failure. That said, the candidates that really shine are the ones who do spot the things that others don't. It allows for the really good candidates to differentiate themselves. Mostly though, we're focusing on the assumptions that the candidate is making about the problem, and the data structures they use to solve it, we just wouldn't be able to analyse and compare to the same extent between two pieces of portfolio code from two different candidates GitHub profiles.
- taurath 11y agoSounds like the ideal candidate or at least the one most likely to succeed is someone who has seen the problem or a version of it before. Hope your other problems are in the same class.
- danpalmer 11y agoThe problem is sufficiently random and fictional that people won't have seen it specifically before, and a lot of the focus is on code readability and maintainability, and I don't think that's something you can fake having seen a problem before.
- tossaway1 11y agoAs an interviewer you shouldn't compare a candidate's answers/solutions to what you think you would have done, you should conpare them to other candidates. This is the main reason I have a standard set of questions I make sure to cover in an interview -- not because they're awesome questions but because they allow me to "callibrate" my evaluation.