That design interview checklist seems on-point to me. I almost only conduct PM / technical design interviews now, so I rarely get to go into that much depth wi

That design interview checklist seems on-point to me. I almost only conduct PM / technical design interviews now, so I rarely get to go into that much depth with candidates (don't expect PM candidates to get nearly as far as dev candidates), but that looks like an ideal breadth and depth. > Reverse Questions > > But IMO this is only for you, not to impress the interviewer. In my experience, asking no questions didn't affect the result. For example, by the time I did the 3 coding interviews at Google I was mentally exhausted and couldn't muster the energy to ask them anything. I still got an offer. Your mileage may vary. Correct this should absolutely be true. Unless your question is something blatantly offensive, it doesn't matter one way or the other. That time is for you, and has no affect on your feedback. I say should, because, well... people are people.