Tell me about a time you failed at something important to you. What happened, and what did you take from it?
Your answer
I ran for an executive position — VP of programming — in a club I'd been part of for almost two years and genuinely cared about, and I lost the election by a small margin, maybe a dozen votes out of around ninety. At the time it stung more than I expected, partly because I'd assumed I was one of the more visible and active members, so losing felt like it must have been about something I couldn't see. Rather than just moving on, I asked two people who I knew had voted against me — people I trusted to be honest with me rather than just polite — why they hadn't supported me. I braced myself for something about my public speaking or my ideas not landing, since that's the kind of feedback I would have known how to hear. Instead, the answer surprised me: they said I was good at ideas but hadn't actually shown up consistently to the smaller, less visible work the club needed — things like setting up the room before events, following up on vendor emails, or covering someone's shift at the last minute. I'd been reliably present for the parts of club life that were visible and rewarding, and quietly absent for the parts that weren't. I hadn't seen that pattern in myself until it was named out loud, and once it was, I couldn't really argue with it — I went back through the past year in my head and realized I could name several specific instances where I'd let that kind of task slide onto someone else without really registering that I was doing it. The next term, I didn't run again, but I deliberately volunteered for exactly the unglamorous logistics work I'd been skipping — I signed up to handle vendor communication for our biggest event of the year, which meant a lot of repetitive email and follow-up with no real recognition attached to it. I did that specifically because I wanted to find out whether the critique was actually fair, not because I was trying to build a case to run again. It was fair. I found it genuinely harder to stay consistent on boring, unglamorous tasks than I'd assumed about myself — my instinct was always to prioritize whatever felt most engaging that week, and the vendor follow-ups were easy to deprioritize precisely because nobody would notice quickly if I did. I ended up having to build an actual habit around it, a recurring reminder and a fixed time each week to just do the unglamorous work regardless of how I felt about it that day, rather than relying on being enthusiastic enough in the moment to get to it. That's the part I actually carried forward — not just an abstract lesson about reliability, but a concrete system for making sure my follow-through didn't depend on how motivated I happened to feel.
Overall score
3.7 / 5Breakdown
The failure (losing an election by a small margin) is specific and the stakes are immediately clear.
Asking trusted people for honest feedback and then volunteering for the unglamorous work are real actions, though described somewhat briefly.
Clear, concrete outcome: the critique was confirmed to be fair, and it was genuinely harder than expected to stay consistent.
Specific, non-generic reflection — naming a real blind spot (consistency on unglamorous work) rather than a platitude.
Reasonably balanced, though the action section could be more developed relative to the setup and reflection.
Shows real self-awareness and willingness to test an uncomfortable piece of feedback rather than dismiss it.
Notes on your answer
“they said I was good at ideas but hadn't actually shown up consistently to the smaller, less visible work”
This is a specific, non-flattering piece of feedback stated plainly — exactly the kind of detail that makes a failure story credible.
“I found it genuinely harder to stay consistent on boring tasks than I'd assumed about myself”
Strong reflection — it names a real, specific realization rather than a generic "I learned to work harder" close.