Had a similar experience at an on-site coding interview. I was handed a single file of about 5000 lines of code and told "please note down what you would impro

Had a similar experience at an on-site coding interview. I was handed a single file of about 5000 lines of code and told "please note down what you would improve, just everything from formatting consistency to architecture". I got through around 1000 lines in the given time (can't recall how long that was) and had to tell them "I found too many things wrong with it, here is the gist". I went on to work on internal architecture and code quality in that position. So yeah, not all tests are made to be passed with flying colors, and not all tests are made to be flunked. Anything in between will still give you valuable output.