Just curious: are you making sure your interviewer are actually first trying to code the project in 3 hours before judging candidates?
I mean, it seems to me that most of my colleagues (and myself) are always very optimistic with respect to "how long it will take". So if you are judging someone based on your expectation without having went through it yourself, it can lead to a perception gap.
This is a good question because I find that my colleagues from previous companies spent a lot of time thinking of 'good ' interview questions and leave it at that.
None of them actually tried solving it within the constrains that a candidate is put through.
