[simonbarker87]

One of the things I’ve written in my book on coding interviews is around expectations and covering off any shortcuts/interview specific things you are doing. It’s annoying but asking: 1. Is there a specific approach or methodology you would like me to take in this test? 2. Saying stuff like “I’m going to do this in functional/OOP”, “I’ll use print for debugging”, “I won’t be using a testing library” etc with a quick explanation goes along way to ironing out these differences

[ellard]

I agree that the above is what we should do as individuals to make our own interview experience smoother. It's a shame that we have to though, considering that the interviewers all have been interviewees themselves in the past and should recognize this issue.