2 ms·
The coding tests in many places no longer test coding. They test algorithms, dynamic programming, or how to deal with ambiguity for an incredibly under specifie
by seanmcdirmid 7y ago
The coding tests in many places no longer test coding. They test algorithms, dynamic programming, or how to deal with ambiguity for an incredibly under specified problem. They are useful in weeding out 80% of the candidates who are clueless, but they don’t provide much reliable distinguishing signal for the 20% that remain. The coding interview isn’t going to tell you the difference between a junior or senior dev. Heck, given that universities prep kids these days for google style leetcode interviews while a senior dev lacks the time for full time prep, junior devs are likely to do better on it.
- zimpenfish 7y ago> They test algorithms, dynamic programming, or how to deal with ambiguity for an incredibly under specified problem. I've been doing this for 25 years now and I've never had to implement an algorithm[1] from scratch or do any dynamic programming. I'm not entirely sure I'd consider myself "clueless" because of that. [1] In the traditional computing sense of the word
- leethargo 7y agoI've been implementing Dynamic Programming, from scratch, just yesterday. But it wasn't for work either.
- danpalmer 7y ago> Heck, given that universities prep kids these days for google style leetcode interviews while a senior dev lacks the time for full time prep, junior devs are likely to do better on it. This depends on what the exercise tests. For datastructures and algorithms, yes maybe. We use a test where the most advanced data structures you will likely use are dictionaries and sets, and even those aren't necessary. The main thing the exercise tests is how do you structure a chunk of non-trivial business logic such that other engineers can understand it and reliably contribute to it. We assess this through code review, looking at the architecture and abstractions used.