>On the other hand, hiring gets discussed endlessly on HN and there doesn't seem to be a compelling reason presented for the status quo Disagree. After reading

>On the other hand, hiring gets discussed endlessly on HN and there doesn't seem to be a compelling reason presented for the status quo Disagree. After reading and participating in the endless HN hiring discussions, I'd say I've come to an understanding of why, at least in SF, interviews are done the way they are. It seems to be a lowest-common-denominator approach that serves candidates and companies in different ways. For the candidate, they can do one set of study (leetcode/system design) and that effort is applicable at a wide range of companies. For the company, they are finding the intersection of people who are at least intelligent enough to grok CS fundamentals (I know it's just pattern matching after you've studied it), and willing to jump through enough hoops. Hiring works a very different way outside FAANG leetcode style interviews. It's mostly a chat between a couple devs about what you've worked on in the past and how applicable that experience is and trying to get a sense of where you're at in your career and if you seem like you'd be good to work with. It's a lot less standardized, so it can be very hit and miss sometimes as sometimes you get quizzed on knowledge of their particular stack. Often the study you do for one company isn't necessarily translatable to another.