> I'm really amazed that this "best interview" question really just boils down to leetcode for a _Senior Staff_ level interview. A good interview should involv

> I'm really amazed that this "best interview" question really just boils down to leetcode for a _Senior Staff_ level interview. A good interview should involve more than just a coding problem. But it should absolutely require at least one coding problem. It’s mind boggling the number of “senior” people with good resumes I’ve screened out in interviews over the years because, simple as a problem like this is, they really had no idea how to even start solving it. I don’t know about the poster, but when I’ve done interviews - especially for senior people - there are a lot of different types of assessment I’d want to do before hiring them. I’d also want to assess their social skills somehow (eg get them to present to the team about something interesting). And ask some high level systems architecture questions, talk about their background, and more.