An engineer at a whiteboard, mid-way through writing a function by hand alongside a worked example of index lookups.

Code REVIEW challenges should replace coding challenges in engineering hiring processes. Here's why:

Even though their shortcomings are known, coding challenges are common in the industry as companies don't know of a better mechanism for filtering candidates. The key issue is that coding challenges aren't good analogues for how developers actually work. In more than a decade as an engineer I've never needed to code a recursive sorting algorithm in 10 minutes (any day now?). Actual work is characterized by specific and unique problems that can be solved in whatever the appropriate time might be, all while assimilating whatever third party information might already exist (hello Stack Overflow!).

Code review on the other hand, is a more natural test of how engineers actually work, especially in a team situation. Code is more often read than written, so understanding code is a key skill. We can learn about how candidates might relate to others by how they give feedback on someone else's code. Are they dogmatic or open minded, specific or vague, uplifting or dismissive? Evaluating what code to keep or what might be better refactored is an everyday on the job challenge for any developer. Fibonacci is not.