Stop Interviewing with Leet Code (fev.al)

Article summary

The article argues that using LeetCode-style questions in technical interviews is not an effective way to assess a candidate's skills and potential for success in a job. The author suggests that these types of questions are often irrelevant to the day-to-day work of a developer and can discriminate against certain types of thinkers. Instead, the author proposes using more realistic and relevant exercises, such as reviewing code or completing a task similar to what the candidate would be doing on the job. This approach can provide a more accurate assessment of a candidate's abilities and potential for success.

Main themes

• ineffective hiring practices
• LeetCode-style questions
• realistic assessments
• developer skills
• hiring process reform
• candidate experience

What commenters say

• Some commenters argue that LeetCode-style questions are useful for filtering out unqualified candidates, while others believe they are ineffective and can lead to false negatives.
• There is disagreement about the value of using real-world problems or code reviews as an alternative to LeetCode-style questions.
• Some commenters believe that the ability to perform well under pressure is an important aspect of a developer's job, while others argue that this is not a relevant factor.
• The use of LeetCode-style questions may be perpetuating a flawed hiring process that prioritizes theoretical knowledge over practical skills.
• Some commenters suggest that the hiring process should focus on assessing a candidate's ability to learn and adapt, rather than their existing knowledge.
• There is a concern that the over-reliance on LeetCode-style questions may be driving away qualified candidates who are not proficient in these types of problems.
• The article's criticism of LeetCode-style questions is seen as a call to action to rethink the hiring process and prioritize more relevant and effective assessment methods.