Imagine you’re about to go on Jeopardy!
You know there will be questions about history, so you memorize the answers to 50 history questions.
You study them relentlessly. You know exactly what you’ll say when they come up.
Then you get to the show.
None of those questions are asked.
Well, crap.
That’s essentially the problem with preparing for a job interview by Googling “most common interview questions” and rehearsing answers.
Sure, you can reasonably expect some version of “Tell me about yourself.” There are other questions that come up frequently enough that it makes sense to understand how you’ll approach them.
But you don’t know what they’re going to ask.
So why make predicting the questions the foundation of your preparation?
Instead, prepare the thing you do know: your experience.
Build an Evidence Bank
In Nail Job Interviews, I teach clients to develop what I call an evidence bank: a repository of career experiences that demonstrate the value you can bring to the new role.
This isn’t a collection of polished scripts.
It’s your proof.
You’ve led teams, solved problems, dealt with difficult people, made mistakes, figured things out, improved processes, persuaded skeptics, learned new skills, managed crises, delivered results, and navigated situations that did not go according to plan.
Those experiences are sitting somewhere in your brain.
The problem is that when someone puts you on the spot and says, “Tell me about a time when…” your brain may suddenly decide it has never experienced anything.
I see this all the time.
Someone with 20 years of impressive experience is asked for an example of how they handled conflict and thinks, “Conflict?” Have I ever experienced conflict?
Of course you have!
You just haven’t organized your experiences in a way that makes them easy to retrieve under pressure.
That’s what we’re going to fix.
Start With What This Job Requires
Don’t begin by randomly cataloging everything you’ve ever accomplished.
Remember the foundation we’ve established throughout this series: start with them.
Go back to the core responsibilities you identified in the job description. What will this person actually need to accomplish? What problems will they need to solve? What skills and behaviors seem particularly important to success?
Now look back and find the experiences that provide evidence.
If the role requires you to lead a team through change, when have you done that?
If you’ll need to influence people who don’t report to you, when have you done that?
If the company needs someone who can walk into ambiguity and create structure, what’s your best example?
If you’ll be responsible for improving revenue, retention, efficiency, customer satisfaction, quality, or another measurable outcome, where have you moved the needle before?
You’re building a bridge between what they need and what you’ve done.
That’s the point of the evidence bank.
One Story Can Do a Lot of Work
Here’s where this becomes much more efficient than preparing individual answers.
Imagine you led the implementation of a new CRM system.
The project involved Sales, Marketing, Operations, and IT. Sales initially resisted the change. The implementation fell behind schedule. You had to convince a senior executive to approve additional resources, resolve interdepartmental disagreements, adjust the rollout plan, and train 60 employees.
Ultimately, the new system launched successfully and improved some important business metrics.
That’s one experience.
But think about how many interview questions it could help you answer.
Tell me about a time you dealt with resistance.
Tell me about a conflict with a stakeholder.
Tell me about a project that didn’t go according to plan.
Tell me about a time you influenced someone.
Tell me about a time you demonstrated leadership.
Tell me about a mistake you made.
Tell me about a time you had competing priorities.
Tell me about a difficult decision.
Same experience. Different lens.
You wouldn’t tell the story exactly the same way each time. You’d emphasize the parts that are relevant to what the interviewer is trying to understand.
That’s why I don’t want you memorizing a story word for word.
I want you to know the experience well enough to use it.
What Should Go Into Your Evidence Bank?
Your evidence bank will depend on the job, but there are some areas worth exploring because they come up frequently in interviews.
Think about experiences involving leadership, problem-solving, conflict, collaboration, failure, change, ambiguity, influence, innovation, difficult decisions, learning, resilience, and measurable results.
Then go beyond the obvious wins.
What went sideways?
When did you have to change course?
When did someone disagree with you?
When did you make the wrong call?
When did you inherit a mess?
When did you have to learn something quickly?
When did you have too much to do and not enough time to do it?
When did you have to deliver something without the resources you wanted?
These experiences are interview gold because they reveal much more than what you accomplished. They show how you operate.
And that’s something the employer needs to understand.
Don’t Just Remember What Happened. Find the Proof.
For each experience, jot down enough information to easily reconstruct it later.
What was happening?
Why did it matter?
What specifically did you do?
What obstacles did you encounter?
What happened as a result?
What did you learn?
And whenever possible, get specific about the outcome.
“Increased sales” isn’t nearly as useful as “increased sales 27% in nine months.”
“Improved the process” doesn’t tell us as much as “reduced processing time from five days to two.”
“Helped retain an important client” isn’t as compelling as explaining that the account represented $1.2 million in annual revenue.
Numbers aren’t appropriate for every story, but specificity creates credibility.
Remember what we discussed in the last post: employers are trying to reduce the risk of hiring you.
Evidence helps.
This Same Specificity Wins on Your Resume
This exact discipline of trading “increased sales” for “increased sales 27% in nine months” is the difference between a forgettable resume bullet and one that gets you the interview. My guide on how to write powerful resume bullets uses the same before-and-after logic.
Your Failures Belong in the Bank, Too
People naturally fill their evidence banks with their greatest hits.
Don’t.
You also need the blooper reel.
Some of the most difficult interview questions ask about failure, weakness, conflict, feedback, mistakes, or situations you would handle differently today.
If you haven’t thought about those experiences before the interview, you’ll end up blurting out something bizarre or reaching for the dreaded fake weakness.
“My biggest weakness is that I care too much.”
Please don’t.
Instead, identify genuine experiences where something didn’t work. The objective isn’t to find a catastrophic failure that makes the interviewer wonder whether you’re legally allowed near a computer.
Find experiences that demonstrate self-awareness.
What did you get wrong? How did you respond? What did you learn? What do you do differently now because of it?
Your evidence bank isn’t supposed to prove that you’re perfect.
It’s supposed to help the interviewer understand how you work.
Please, Not the Fake Weakness
If “I care too much” is currently your answer, or you’ve been drawing a total blank on this question, you’re far from alone. I’ve written an entire post dedicated to how to actually answer the weaknesses question well, with a process for finding something real instead of something safe. A genuine answer, chosen from your evidence bank, will always beat a rehearsed non-answer.
Preparation Is Bigger Than Your Evidence Bank
I want to make one thing clear: building your evidence bank is a major part of interview preparation, but it’s not the entirety of it.
Preparing means creating the conditions that allow you to perform at your best.
Have you deeply researched the company? Do you understand the role? Have you thought about what this particular interviewer may need to know? Do you know who you’re meeting with and what their role is?
If the interview is virtual, what’s behind you? Is your camera at a flattering angle, or are we looking up your nose? Does your microphone work? Is your lighting decent? Are notifications going to start dinging halfway through your answer?
What are you wearing? Where are your notes? Do you have water? Have you thought through the questions you want to ask?
And, perhaps most importantly, what are you telling yourself before you walk into the room?
All of those things affect how you show up.
Interview preparation isn’t writing answers to questions you hope they’ll ask.
It’s creating the scene and preparing the raw materials you’ll need for the conversation you’re actually going to have.
If Your Interview Is Virtual, Prepare the Room Too
That list of virtual-interview logistics deserves more than a passing paragraph I’ve watched good candidates lose ground to bad lighting and worse camera angles. I’ve put together a full guide on how to dress to impress for a virtual job interview, and for a cautionary tale about what happens when the logistics fail mid-conversation, see a Zoom interview that went sideways.
Don’t Over-Rehearse
There’s a sweet spot here.
You want to know your experiences well enough that you can access them easily, but you don’t want to polish them into little speeches.
An interviewer may interrupt you. They may ask for more detail about something you considered unimportant. They may approach the topic from an angle you didn’t anticipate.
That’s okay.
A conversation is supposed to move.
If you’ve memorized your answer, an interruption can completely derail you. If you understand the experience, you can adapt.
Think of it like telling a friend about something that happened at work. You know the story. You don’t need a teleprompter.
That’s the level of familiarity we’re after.
Prepare for the Interview, Not the Questions
Go back to our poor Jeopardy! contestant.
The mistake wasn’t preparing.
The mistake was preparing for a specific set of questions instead of building the knowledge needed to respond to whatever questions appeared.
Your interview works the same way.
You don’t need 30 perfectly rehearsed answers.
You need to understand what the company needs, identify the experiences that demonstrate your ability to provide it, and become familiar enough with those experiences that you can access the right evidence when you need it.
Then, when the interviewer asks something you didn’t anticipate, you don’t have to panic because it wasn’t on your list.
Listen to the question. Think about what they need to understand. Reach into your evidence bank and pull out the experience that helps them understand it.
Don’t prepare your answers. Prepare your proof.
That’s one of the core strategies I teach in Nail Job Interviews, and it can completely change the way you prepare.
In the next post, we’ll look at a part of the interview that candidates frequently squander: the moment when the interviewer stops asking the questions and says, “What questions do you have for me?”
Because the questions you ask can tell an interviewer quite a bit about you, too.
Want Help Building Your Evidence?
Learn more about Nail Job Interviews and working with me, Kyla Duffy, at kyladuffy.com. You can find more strategies like this one on the blog.
