Yes. And I tend to use it outside of interviews too.<p>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&#x27;re trying to reach a conclusion on something instead.<p>When I&#x27;m interviewing, I expect candidates to answer in a STAR-style. If I ask something like &quot;Do you use TDD?&quot; I absolutely expect more than &quot;Yes&quot;. I want to know how you used it, what worked well&#x2F;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?<p>More broadly it feels a bit like you&#x27;re demonstrating the PDCA&#x2F;PDSA&#x2F;OODA cycle.