3 ms·

I feel like the author missed the most critical point: Leetcode style interviews are great at weeding out terrible coders (95% of applicants) early on in the hi

I feel like the author missed the most critical point: Leetcode style interviews are great at weeding out terrible coders (95% of applicants) early on in the hiring process, but don't carry an as strong signal for separating excellent candidates from the good ones. Asking standard array/string manipulation/sorting etc questions in a 30min phone screen is very valuable to save your engineers 5hrs on a poor candidate. Conversely, throwing an NP hard leetcode hard at a senior dev with 20 years of experience and excellent culture fit with your organization in the 9th interview is basically meaningless.

deleted 2y ago
[deleted]
chongli 2y ago
Conversely, throwing an NP hard leetcode hard at a senior dev with 20 years of experience and excellent culture fit with your organization in the 9th interview is basically meaningless. Worse than meaningless, it's a great way to toss away a diamond in the rough. Leetcode problems skew towards competitive programming and grinders. They do absolutely nothing to show real-world programming skills which involve: 1) working within a large, existing codebase, 2) strong code documentation and commit message habits, 3) understanding of coding styles within the company culture so that you don't write in an unintelligible, bespoke style, and 4) communication skills and the ability to work within a team so that the candidate is not fighting strong headwinds.