I'd argue the "presentation and Q&A" format addresses that directly. The candidate gets to pick exactly what the interview is going to be about, at least at the beginning, so they have full control over first impressions. No gotchas at all. Who wouldn't pick something they're confident about?

If someone thinks Cmake is super cool and knows all sorts of great use cases for it, then they should present that. They should also be prepared to answer open-ended follow-up questions like "broadly speaking, how could a project transition from something like Automake to Cmake?" or "what are some footguns in Cmake and how can we avoid them?"