Recently I’ve done about 5 onsite interviews and many phone screens. The only people who ask somewhat deep questions about my experience are recruiters and hiring managers during the initial phone screens, but none of the engineers at the onsites did. They may ask for a brief description of what I do, and then its straight into the technical interview. I have 4 YOE and have interviewed with mostly mid-sized companies and some FANGs.
One of the one-hour interviews should be a work experience interview. It should be about the hard problems you've spent months solving. This doesn't appropriately fit under "Culture Fit" or System Design".
Because you can lie
But what if a candidate is complete dead weight on their current team but are good at cracking interviews? Are they just going to eventually get PIP’d?
The probability that someone lies about projects and then end up being dead weight is much higher than the probability of someone who is good at cracking interviews but ends up being a dead weight. If the candidate is good at cracking interviews, then they're probably good at coding. But not always.
It's called task-oriented, resume-blind interviewing. The idea is that you develop an objective rubric with which to assess candidates on a normalized basis, regardless of individual background. If you're capable of doing the job, theoretically your background (how you got there) is irrelevant. Emphasis on "theoretically" - this assumes that the objective rubric is related to, and assesses for ability in, the specific role.
Well said.
It’s true for PM too. We have to do cases and discuss them, and finally interviews are all about working on mock projects with engineers and designers.
Also because many times they can't dig up details , because the candidate could say NDA .
No one cares. Can you solve the interview loop questions is what matters