Practice. You're telling a story, it can be prepared, you don't have to relive it every time. Understand why they're asking. It's easy to talk about your suc

Practice. You're telling a story, it can be prepared, you don't have to relive it every time. Understand why they're asking. It's easy to talk about your success, and to idealize how we got to an outcome, but in reality it's more like: 1) search for something on StackOverflow, 2) figure out you should be searching for different terms, 3) try some off-the-shelf software recommended in a buried comment, 4) fail to compile it from source, 5) try a buried answer in a related question; etc. Those are all "failures" in that you weren't born knowing the correct answer, and being able to describe how you got to an outcome fully is valuable. Ask them the value they're getting so you can characterize the experience appropriately. We were hiring a senior designer to work with a particularly internally contentious product and development team. We were concerned they hadn't discussed any grit during the interview process, only happy paths. We call them up and say, tell us about a time you fought with someone and lost. They respond, "uh, am I going to have to actually fight people in this job?" No, your PM might be a real pain in the ass and we can't seem to get them replaced so you're going to have to stick up for yourself, and we'd like to hear about a time you did that and it still didn't work out for you, and what happened next. And, they did, and we hired them, and they worked out well.