Comments by "Vitaly L" (@vitalyl1327) on "Rethinking the Technical Interview" video.

@chess_ramone culture fit is not a predictor of engineering abilities. And these days there is an insane amount of impoators, of pseudo-engineers wbo Dunning-Krugered themselves into believing tbey are capable while tbey are very far from it.
4
but how? The problems engineers working on in real life are, normally, quite big, complex and entangled. You cannot give any such problem on an interview and see an engineer devouring it bit by bit in a course of one hour. He'll need 3 to 5 months to simply start getting into this problem at work. So how can we assess an engineer, if not by a smaller scale problems that still, hopefully, have some of the properties of the larger ones?
3
@William Henseley ok, you're looking for an engineer capable of writing long term maintainable code, capable of quickly comprehending, often reverse-engineering legacy code, capable of creating optimal or close to optimal algorithms when requirements are tight or producing reasonable solutions quickly when requirements are lax. Your code base is 40 years old and contains millions of lines of code in multiple languages. How do you test engineers for what they're expected to do at work, see the list above? Small, simple coding problems is pretty much the only way to filter out thosr who cannot even code and cannot solve problems, and only then you can think of a culture fit, of a past track record and all that. I noticed a curious pattern. Those who are vehemently opposed to leetcode style interviews are always ones who are consistently vetted out by such interviews. Guess, for a good reason...
2
@ohgin12345 leetcode is just a first step to weed out the most outrageously incompetent. Of course it is not enough.
1