Yes. And I tend to use it outside of interviews too. It feels like a good way to communicate the context of something and my intent. Those things open up more

Yes. And I tend to use it outside of interviews too. It feels like a good way to communicate the context of something and my intent. Those things open up more avenues of discussion. But it could be annoying if you're trying to reach a conclusion on something instead. When I'm interviewing, I expect candidates to answer in a STAR-style. If I ask something like "Do you use TDD?" I absolutely expect more than "Yes". I want to know how you used it, what worked well/badly. How did it affect your code? Give me an example. How did it affect your company? Less bugs? Faster or slower development? More fun? More arguments? More broadly it feels a bit like you're demonstrating the PDCA/PDSA/OODA cycle.