> Interviews are weird: the pressure of time, and not being able to look things up, distorts the code.
In the interviews I do, I tell the candidate that:
1. There is no time pressure. Work at a normal pace, as if you were working here. This is not a speed test. I don't expect you to finish. I mainly want to know how you think.
2. You should look things up. Behave the same way you would when coding at home. Use Google, Stack Overflow, documentation, etc.
This probably works better for the interviews I give because the problem is not implementing an existing algorithm. It's a realistic task, something that we've actually built on-the-job.
In the interviews I do, I tell the candidate that:
1. There is no time pressure. Work at a normal pace, as if you were working here. This is not a speed test. I don't expect you to finish. I mainly want to know how you think.
2. You should look things up. Behave the same way you would when coding at home. Use Google, Stack Overflow, documentation, etc.
This probably works better for the interviews I give because the problem is not implementing an existing algorithm. It's a realistic task, something that we've actually built on-the-job.