E.g. "Describe your experience with software operations and running services in production" is a really bad question as it is too open ended and leads to name dropping. Asking for "engaging answers" judges the persons ability to write interesting novels instead of ability to solve (or avoid) problems.
Ditto with “How would you approach the design and implementation of new features for a production service?”. This question is way too generic and a proper answer could fill many books. There is so many different ways of doing this and depends a lot on what the software is used for. When benhoyt says "In short, don’t be generic" then at least he could take his own advice into account when writing questions.
An example response like "At Shopify [...] doubled click rate, from 15% to 27%" likely violate NDAs. I don't think companies like you to tell this to their competitor.