The original article [1] describes new process in the context of PM interviews, which are different from software developer interview, no matter how technical PM is.
The changes that I particularly like are: improvement in coordination between interviewers themselves, and stop sharing feedback between themselves until the very end. The latter really affects how next interviewers view the interviewee.
After reading about wisdom of the crowds, we started doing this with estimates. We always break up the project into small tasks together then seperate and estimate them individually.
We've found we're a lot more accurate because we don't influence each other, as well as don't go into autopilot on an estimate assuming someone else has it under control, or someone just deferring to the more Sr. Dev when the more Sr. Dev made a mistake.
I could see how this would also work well with interviews.
Well, FB did that at least 6+ months ago when I got trained for interviewing.
As for the questions asked, there is an internal tool with various questions you are supposed to ask, with info about what signals you can get, how to extract more info and how to formulate your feedback.
I was always told that I need to help the person I'm interviewing solve the problems.
The changes that I particularly like are: improvement in coordination between interviewers themselves, and stop sharing feedback between themselves until the very end. The latter really affects how next interviewers view the interviewee.
[1] https://blog.usejournal.com/rethinking-how-we-interview-in-m...