> I don’t like LeetCode as a post-college SAT, but pass-fail technical screens do filter out candidates who cannot break down and solve problems in the language they will actually use, even with AI.
I strongly disagree. Leetcode-style exercises are detached from the realities of software engineering, and signal ad-hoc preparation over actual competence and skills.
Just because you do not know how to implement a, say, ray search algorithm with optimal complexity that does not mean you cannot implement a background worker, a card with accessibility, a service which securely handle RESTful requests, etc. So why aren't you excluding everyone who is not a ray search experts from your application process? Do you seek to hire competent software engineers, or do you want to have a room of ray search enthusiasts?
Also I doubt that every interviewer making a leetcode interview would necessarily pass it themselves. If you are the interviewer, you can choose the problem, learn the solution, and then profit from the dominant position during the interview.
I have seen colleagues do exactly that: I am fairly sure they would never pass a leetcode interview themselves, and they were not really good coders. But for some reason they really liked making candidates struggle with the one exercise they had learnt by heart.
I have been interviewed (and failed) by people I wish I could have interviewed myself right after. They were very clearly keeping the interview in their comfort zone while feeling superior and making me miserable. I am absolutely convinced that if I had had the chance to invert the roles right at the end and interview them myself, I could have made them miserable just the same.
When you are the interviewer, never forget that you are in a dominant position.
I find the chess comment fairly weak; while chess is a "perfect information" game (in that you have full information about every piece on the board), at every level that chess is played at there will be unknowns about the player you are facing.
At lower levels, you can certainly play sub min-maxed moves that are more likely to confuse or pressure a weaker opponent. You could call these bluffs. Opening theory is also a wonderful game, you're essentially playing a game of "let's bet that you haven't prepared this particular set of lines as well as I have" with the opponent. The same thing goes for game styles, open vs closed, etc.
Last but not least, playing a perfect game of chess is so far out of the realm of possibility for humans, that the entire "there's always a correct move" is completely irrelevant. We are now at a point where 7-piece endgames have been completely solved, and it involves 4.2×10^14 positions. Good luck memorizing that, and the scaling from there on out is not pretty.
In this sense, chess occupies a very interesting spot; somewhat calculatable for a human (and yes, tactics dominate up to say 2000 ELO), but there's plenty of room for creativity and strategy also. It's also played at an insanely high level, which makes it a worthwhile challenge and time investment. What it does NOT have is randomness. I often wonder what the competitive landscape of a chess variant involving some randomness would look like, or if it would fundamentally change the nature of the game.
Considering the mention of AI in job searches and screening, I don’t know if this is actually from 2016. Some fantastic advice in here though, particularly on navigating political / technical landscapes
> I don’t like LeetCode as a post-college SAT, but pass-fail technical screens do filter out candidates who cannot break down and solve problems in the language they will actually use, even with AI.
I strongly disagree. Leetcode-style exercises are detached from the realities of software engineering, and signal ad-hoc preparation over actual competence and skills.
Just because you do not know how to implement a, say, ray search algorithm with optimal complexity that does not mean you cannot implement a background worker, a card with accessibility, a service which securely handle RESTful requests, etc. So why aren't you excluding everyone who is not a ray search experts from your application process? Do you seek to hire competent software engineers, or do you want to have a room of ray search enthusiasts?
Also I doubt that every interviewer making a leetcode interview would necessarily pass it themselves. If you are the interviewer, you can choose the problem, learn the solution, and then profit from the dominant position during the interview.
I have seen colleagues do exactly that: I am fairly sure they would never pass a leetcode interview themselves, and they were not really good coders. But for some reason they really liked making candidates struggle with the one exercise they had learnt by heart.
I have been interviewed (and failed) by people I wish I could have interviewed myself right after. They were very clearly keeping the interview in their comfort zone while feeling superior and making me miserable. I am absolutely convinced that if I had had the chance to invert the roles right at the end and interview them myself, I could have made them miserable just the same.
When you are the interviewer, never forget that you are in a dominant position.
I find the chess comment fairly weak; while chess is a "perfect information" game (in that you have full information about every piece on the board), at every level that chess is played at there will be unknowns about the player you are facing.
At lower levels, you can certainly play sub min-maxed moves that are more likely to confuse or pressure a weaker opponent. You could call these bluffs. Opening theory is also a wonderful game, you're essentially playing a game of "let's bet that you haven't prepared this particular set of lines as well as I have" with the opponent. The same thing goes for game styles, open vs closed, etc.
Last but not least, playing a perfect game of chess is so far out of the realm of possibility for humans, that the entire "there's always a correct move" is completely irrelevant. We are now at a point where 7-piece endgames have been completely solved, and it involves 4.2×10^14 positions. Good luck memorizing that, and the scaling from there on out is not pretty.
In this sense, chess occupies a very interesting spot; somewhat calculatable for a human (and yes, tactics dominate up to say 2000 ELO), but there's plenty of room for creativity and strategy also. It's also played at an insanely high level, which makes it a worthwhile challenge and time investment. What it does NOT have is randomness. I often wonder what the competitive landscape of a chess variant involving some randomness would look like, or if it would fundamentally change the nature of the game.
What font did you use? It is such a beautiful and different than others.
It seems to be "Albura" which I found here: https://fontesk.com/albura-typeface/
This was a great read.
Considering the mention of AI in job searches and screening, I don’t know if this is actually from 2016. Some fantastic advice in here though, particularly on navigating political / technical landscapes
Ok, we'll take 2016 out of the title above. Thanks!
Correct the url has 2026, probably a typo