I used to fake stories in job interviews. A lot of them.
When the interviewer asked for an example of a time I handled a tight deadline, or led a team, or worked under pressure, I would reach for something half-true and stretch it into a longer story. I just did not have the experience to back it up.
The real problem was not getting caught. Most of the fake stories were technically plausible. The real problem was that I could never deliver them with confidence. Interviewers cannot always name what is off, but they can feel it. There is a difference in how someone speaks when they are recounting something they actually lived, versus reconstructing a story that was not theirs.
How I changed it
A while back, I came across a YouTube video that said something almost annoyingly simple:
"The key to smashing an interview is to actually do the things you said you did."
It sounded like garbage advice at first. Of course you should have real experience. Telling a final-year student to just "go get real experience" is a fortune cookie, not a strategy.
I thought that initially, but it was a different story when I actually tried it.
The example that changed how I interviewed
During the mid-semester period of my final year, I had to juggle my marketing internship at Nestle with university exams. The workload across both was heavier than usual that fortnight.
Instead of letting it all happen reactively, I built a calendar that mapped out every deadline, exam date, and study block. I then messaged my manager early in the fortnight, before things started overlapping, to communicate about my workload and set realistic expectations for those two weeks. We agreed on a revised plan. I delivered on what I committed to.
A few months later, when an interviewer asked me, "How do you handle tight deadlines?", I had a real, specific story to walk them through. Calendar. Early conversation with the manager. Expectations set. Plan delivered.
I did not have to make anything up. I just described what happened. The confidence in my delivery was not a technique. It was the simple fact that there was nothing to perform.
That single example gave a lot of hiring managers the confidence to hire me.
A reframe I share a lot in mentoring
This is the reframe I keep coming back to in mentoring sessions. If your interview answers are stalling, you are probably not short of capability, you are short of stories you can tell with conviction.
If you want to talk through what is blocking your interview answers, book a free 15-minute call.
Why faked answers fall flat
The reason fake stories never give you confidence in the room is simple. They are not yours. You are reconstructing a moment that did not happen the way you are describing it, so there is no real memory to draw on. The delivery has to be performed rather than recalled. That is the gap interviewers feel.
Real stories work the opposite way. You are not performing. You are remembering. The pace, the small asides, the natural pauses, all of that happens by itself because you actually lived it.
One last thing
I am not telling you to copy what I did at Nestle. The specific example does not matter. The principle does.
I know it is exam season for a lot of you reading this. Whatever you are juggling this semester, you do not need to invent anything. The story you will tell in your next interview is probably already happening to you right now. You just have to start noticing it as you live it.
For more on what Australian employers actually test for in interviews, read: Why International Students Fail Australian Job Interviews (Even With Good English).