3 ms·
I was rejected by a pretty well-known DB startup over a fizzbuzz-level coding assignment. I didn't blow it off because of its triviality--quite the opposite, I
by throwaway1928 7y ago
I was rejected by a pretty well-known DB startup over a fizzbuzz-level coding assignment. I didn't blow it off because of its triviality--quite the opposite, I gold-plated it with spec comments, code comments, computational complexity comments, unit tests, type annotations, etc. I showed it to some friends at FAANG companies and they couldn't understand why it was rejected either. It was just really weird and unsettling to be rejected over a trivial test when I know I'm capable of so much more (I've eg implemented major features in a production MPP database engine). It might be partly due to their resume-blind process, which I support in principle, but it seems weird to disregard 20 years of mostly non-trivial software development when evaluating someone on a trivial test.
- watwut 7y agoPossibly they did not considered you fit. If they want to hack around (which plenty of teams want), someone who polishes things looks like odd one and is just annoyance to them. Startups are unpredictable in their expectations. What you consider good code they consider bad code. I have seen startup where long variable names were wrong. So "nameFilter" would be wrong and "flt" would be correct. Seeing one as stupid overengineering and the other as smart.