The Trivia Trap: How Tech Interviews Are Failing Us

Tech interviews have become a farce, with companies more interested in testing candidates' ability to recall obscure trivia than their actual skills. For example, being asked to implement a binary search tree from scratch or explaining the differences between monads and functors has little to do with a developer's ability to write clean, efficient code. This approach is not only frustrating but also ineffective.

The beneficiaries of this system are not the companies or the candidates, but rather the interviewers who get to feel smug about their own knowledge. They're more concerned with showing off their expertise than finding the best fit for the role. Meanwhile, qualified developers are being turned away because they can't recall some obscure algorithm or data structure.

A better approach would be to focus on practical skills, such as coding challenges that mimic real-world scenarios or pairing with a candidate to work on a actual project. For instance, asking a candidate to refactor a piece of code or debug a complex issue would give a much better indication of their abilities. This would not only make the interview process more enjoyable but also more effective.

So, what can developers do to fight back? For starters, they can prepare by practicing coding challenges and reviewing common interview questions. They can also ask questions during the interview, such as what a typical day looks like or what the biggest challenges are in the role. Additionally, developers can look for companies that prioritize skills over trivia, and speak out against the status quo.

Some companies, like Google and Microsoft, are already moving away from trivia-based interviews and towards more practical assessments. It's time for the rest of the industry to follow suit. By doing so, we can create a more inclusive and effective hiring process that benefits both companies and candidates. It's time to stop testing trivia and start testing skills.