There are literally dozens of reasons that tech interviews suck. However, they all mostly boil down to the same root cause: there's very little correlation betw

There are literally dozens of reasons that tech interviews suck. However, they all mostly boil down to the same root cause: there's very little correlation between the content of most interviews and the jobs people will perform. Some real life situations that I've been on one side or the other of: * Companies doing a "centralized" process that ignores the candidate. The questions are always overly generic and it really boils down to, "You need to want to work here enough to basically take any job we'll throw at you." Sorry, I don't want to work any company enough to just take any random job. * Coders asked to complete academic problems that will NEVER come up for them in their real work. * Coders not being allowed to leverage external resources like they will literally do EVERY DAY in their real jobs. * Managers being asked to be coders in interviews. * Questions that have binary "right" and "wrong" answers. * Asking questions that have a million ways to do it and then honing in on one specific disagreement the interviewer and candidate had. * Interviews that are more about the interviewer stroking their own ego and proving that they are smarter than the candidate. * Completely ignoring that the absolute best indicator of future performance is past performance; not, "what quiz could this person solve in 45 minutes in an interview."