What Stories Should I Tell in a Job Interview?

SHOW NOTES:

WorkLife Stories from School of WorkLife Episode: What Stories Should I Tell in a Job Interview?

What stories should I tell in a job interview is a question every candidate asks — and the answer is three: a success story, a failure story and a passion story, because they help the panel truly meet you.

Emeka had earned his place in a final round of five, every candidate at the top of their game. This is the story of the six evenings he spent looking for what only he could say — a success nobody had witnessed, a failure faced and owned, and a quiet passion that was his alone.

RESOURCES MENTIONED

Get the Job — Professional Self-Coaching for Job Interviews Tell the Three Stories That Reveal Your Professional Value, Character and Potential

Work With Me: Commissioned learning resources, speaking engagements, and organisational partnerships.

The stories I write are based on real WorkLife challenges, obstacles, failures and successes. Persons and companies portrayed in the stories are not based on real people or entities. Carmel O’ Reilly  schoolofworklife.com 

Transcript

Speaker 0:07

Emeka had six days. Final round. Head of engineering — the role that comes up once in a career at the right moment, and this was the right moment. Twenty years, plant floor to management, a track record he didn't need to inflate. He'd earned his place in that room. That wasn't the problem. The problem was the room itself — four other candidates, every one of them at the top of their game. The first evening, he reviewed his prepared answers — and read them back slowly, out loud. / And that was when he heard it. / Any one of the five could deliver them. Welcome to WorkLife Stories from School of WorkLife. I'm Carmel O' Reilly. And today's episode is What Stories Should I Tell in a Job Interview? — a question every candidate asks, answered by a man who discovered that being excellent was only the price of entry. This story is about Emeka. And about six evenings, a forty-minute drive, and the search for what only he could say. The Field Emeka had six days. Final round. Head of engineering — the role that comes up once in a career at the right moment, and this was the right moment. Twenty years, plant floor to management, a track record he didn't need to inflate. He'd earned his place in that room. That wasn't the problem. The problem was the room itself. Final round meant a shortlist — four others, and he knew exactly what they'd look like, because he'd sat on enough panels himself. People like him. Twenty years, real deliveries, strong references. The technical filtering had happened two rounds ago; nobody in that room would be anything less than excellent. The first evening, he did what a serious candidate does. He reviewed his prepared answers — the transformation programme, the safety record, the plant turnaround. Accurate. Substantial. Verifiable. He read them back slowly, out loud, the way he'd learnt to review anything that mattered. And that was when he heard it. Any one of the five could deliver these answers. Different plants, different programmes, the same shape. Strip the names out, and nothing in them was his alone. Twenty years of being at the top of his game, and he'd prepared answers that made him interchangeable. He sat back from the laptop and asked himself the only question that mattered now — the one he'd be silently asked in that room, whatever the actual questions were: Of five people who can all do this job — why you? A Different Question The second evening, Emeka didn't touch the prepared answers. They weren't wrong. They were just the entry fee, and everyone in the field had paid it. He opened a blank document and typed a different question at the top: What do I have that no one else in that room can say? Not better. Not bigger. His. He went back through the twenty years — not the CV version, the real version. The moments. The ones that stayed with him, whether or not anyone had noticed them at the time. An hour in, he typed a line that surprised him: The audit. Nobody ever knew that was me. Three years ago, a compliance audit the whole site had been braced to fail. It passed — cleanly. Everyone remembered the relief. Nobody knew about the eight weeks before it, when Emeka had quietly rebuilt the maintenance records system on his own time, because he'd seen what was coming and couldn't watch it arrive. His first instinct, even now, was to set it aside. It had never appeared on any CV. Nobody saw it. He looked at that instinct for a long moment. Then he typed underneath it: Nobody saw it — which is exactly why no one else can claim it. And it shows the thing my prepared answers don't: I see what's coming, and I fix it before it lands, whether or not anyone is watching. The transformation programme proved he was capable. Every candidate had one of those. The audit was his alone. The Story He'd Never Said Aloud The third evening was the hard one. He knew the failure question would come — at this level it always did, and at this level everyone would have a polished answer for it. A calculated risk that didn't land. A market shift nobody saw coming. A restructure that arrived before the results could.  Emeka knew what his real failure was. He'd just never said it aloud. Seven years ago, he'd made a hire he believed in — and kept believing long after the evidence had stopped agreeing. Ten months of covering, coaching, hoping. By the time he acted, the team had paid for his hope, and two good people had nearly walked. He typed it plainly. What happened. His part in it, without softening. And then — because a failure without its learning is just a confession — what changed: I still back people. But now I back them with evidence — honest check-ins at thirty days, real ones, where we both say what's working and what isn't. Hope is not a development plan. He read it back and felt the thing he'd been avoiding for seven years: exposed. Then he read it again, this time as the panel would hear it. A real failure, plainly owned — what he got wrong, his part stated without softening, and the way he works rebuilt because of it. A story only he could tell, because it had only happened to him. At final round, Emeka realised, that is what a story is for. The Quiet Passion The fourth evening, Emeka nearly set the third story aside. Passion. He knew what was expected, because it's what strong candidates say: driven by excellence, energised by building great teams, passionate about engineering. All true. All identical. He didn't do dramatic enthusiasm. He'd spent twenty years being the calm one  — the same quiet nature that had once rebuilt a records system over eight weeks and never mentioned it to anyone. So he asked the question the way he'd learnt to ask it this week: not what am I passionate about — but what can I not leave alone? The answer arrived with a specific memory attached. The intermittent line fault, years ago, that everyone had learnt to work around — restart the system, lose twenty minutes, carry on. It had bothered him for months. Not because anyone asked him to fix it. Because unexplained problems itched at him. He'd spent lunch breaks with the diagnostic logs until he found it: a sensor misreporting in cold weather, once a fortnight, for four years. Nobody had asked. That was the point. He typed: I'm drawn to the problems everyone else has learnt to live with. That's where I do my best work — and it's usually where the biggest gains are hiding. Quiet. Specific. His alone — because it wasn't a quality he was claiming. It was his character, showing itself in a passion only he could own. His Own Words The fifth evening, he didn't write anything new. He had a forty-minute drive to the site each morning, and he'd started using it. A voice memo, one story at a time, told out loud to the windscreen. The first tellings were stiff — he could hear the document in them. By the third morning, something had shifted. He wasn't reciting the stories. He was telling them, the way he'd tell them to someone he trusted. Words dropped away. Better ones arrived on their own. The audit story found its natural opening — "The proudest I've been at work is of something nobody knew I did" — and he heard, in the car, that it was a first line a panel would look up from their notes for. That evening he trimmed each document to match how he actually spoke. What remained didn't sound like a candidate. It sounded like him. Which, he now understood, was the entire strategy — the one position in that field no other candidate could occupy. The Night Before On the sixth evening, Emeka did very little. He read each story through once. He didn't rehearse. He'd told them enough times to trust them now. His prepared answers were still there — the programme, the safety record, the turnaround. They'd carry the questions about capability, as they should. But when the real question came — the one beneath all the others, of five people who can do this job, why you? — he had three answers no one else in that room could give. A success nobody had witnessed. A failure faced and owned. A quiet passion that was his alone. He had made himself one promise for that morning: whatever they decide, they will have met me — not a candidate. And that promise, he kept. The Outcome Emeka got the job. What the chair of the panel told him afterwards is worth reading twice: "It was the hardest decision this panel has made. All five of you could do this role — we knew that before anyone walked in. What we couldn't have written down was what we were looking for beyond that. You showed us. By the end of your interview, we weren't comparing candidates anymore. We'd met the person the role needed." Five people deserved it. The one who got it was the one they had truly met. Why These Three Stories What Emeka found isn't a technique for strong interviews. It's how people at the top of their game distinguish themselves among others at the top of theirs. A success story demonstrates your value. At final round, everyone's achievements are impressive — that's how they got there. What can't be compared is what your achievements reveal about you. Which is why the question that finds this story is never "what have I achieved?" It's "what am I genuinely proud of?" — because pride points at the moments that reveal your character and capabilities, whether or not anyone was watching. Emeka's audit had no audience. It was still his strongest story, precisely because it was his alone. A failure story reveals your character. Interviewers ask about failure deliberately — they're testing for self-awareness, judgement and maturity, because something always goes wrong in every role, and they need to know who you'll be when it does. A failure story only undermines you if you share the failure without the learning. Owned plainly — your part stated, the learning named, the changed practice still running — it shows them who you are when it goes wrong. The learning is the story. The failure is only the doorway to it. A passion story communicates your motivation. Every candidate at this level claims drive, excellence, commitment — all true, all identical. Passion becomes credible the moment it becomes specific: a passion in your real experience, with a memory attached — one you can show them, because you lived it. And it's allowed to be quiet — right up until something that matters depends on it being heard. Some roles come up once in a career, at the right moment. That is the moment to own your full truth out loud. Emeka had carried the audit quietly for three years. He told it when it counted. One of these alone is a partial picture. Together they answer the question beneath every interview question — who are you, and why should we believe in what you'll do here? Then it comes down to who they're really looking for. Help them see your value, your character and your potential. Because experience can be compared. Stories cannot. You Already Have These Stories Twenty years of work contained every story Emeka needed. He didn't create them in six evenings — he found them, dug past his first dismissals of them, shaped them into his own words, and made them ready. Yours are there in the same way. The success you're genuinely proud of, whoever noticed. The failure that changed how you work. The passion that shows itself quietly, in what you can't leave alone. CLOSING That's today's story — What Stories Should I Tell in a Job Interview? And if you want to go deeper, my first Professional Self-Coaching resource — Get the Job, for anyone preparing for a job interview that matters — is there when you're ready. All the details and links are in the show notes, or you can find everything at www.schoolofworklife.com. Remember: Experience can be compared. Stories cannot — and yours are already in your experience, waiting to be recognised. Thank you for listening.