> Maybe I'm naive but I think an interview should be an honest exchange of what you actually know, not what you crammed for before the interview.
All the way back in ~2012, Amazon's own recruiters were recommending candidates cram "Cracking the Code Interview" (to the surprise of the actual interviewers, who didn't want you doing that). This is the way things have been for a long time now.
Maybe it's time to question it. I don't think there's anything wrong with the now traditional whiteboard interview as such, but the notion that the same questions are all just as relevant to disparate teams is highly questionable. Technical questions should be based on the actual codebases or systems, IMO. I would also question the Hogwarts style approach of interviewing the candidate as a generic dev and then sorting them to the right team.
All the way back in ~2012, Amazon's own recruiters were recommending candidates cram "Cracking the Code Interview" (to the surprise of the actual interviewers, who didn't want you doing that). This is the way things have been for a long time now.