But you will have people watching you work and you will be under time pressure in normal work as well, so if you just turn to spagetti at interview are you actually going to perform any better at day to day?
When was the last time you had to nail out a fully working nlog(n) longest valid bracket sequence in to prod within 45 mins, without spending 3 weeks in meetings, design doc reviews, capacity plannings and allocations and alignments with the said bracket owners?
No one - literally no one - expects perfect implementation of anything in an interview, where are you even getting this notion? What actually *is* expected of you is to describe how you would approach the issue.
So you have never worked in an office with other people?
And yes couple hours of interview is different than two weeks sprint, but you are very naive if you think two week of work days means 80 hours of work. Plus I expect a lot more from you during a sprint than during an interview. During an interview I am fine with pseudo code as long as you can explain what you want to do. During actual sprint I actually expect tested deliverables.
> So you have never worked in an office with other people?
I used to, but even then nobody actively watched me code. Everyone else had their own jobs to do
> During an interview I am fine with pseudo code as long as you can explain what you want to do. During actual sprint I actually expect tested deliverables.
So you're optimizing for the ability to write pseudocode under intense time pressure and social awkwardness. Is that the most important quality you seek in a candidate?
