[some-guy]

I've done over a hundred interviews now. One of the most valuable engineers I hired had an interview that steered off course from the original algorithm question I had in mind. I opened with a "what's the most challenging part of your job currently?" and he responded "Upgrading our monolith front-end from Angular 1 to Angular 2".

We spent the entire hour discussing back and forth all of the challenges not just for him but the team in great detail and how they went about doing the upgrade. I'm glad the interview didn't go as planned because he's still here and he's great.

[danielvaughn]

Yep, I love doing interviews this way - we just talk shop. It shows way more about the candidate than any abstract problem I could devise.

Doing leetcode in interviews is like if the NBA drafted players based on trick shots.

[flimsypremise]

This is how I mostly do interviews. Get the candidate talking about their previous roles and see how they talk about the problems they've solved and what that reveals about how they see the job.

[diffxx]

I personally would make something like this the default interview approach for anything but entry level positions.