Imagine you’re driving somewhere you’ve never been before.
Your GPS tells you to turn left, so you turn left. Then right. Then right again. You follow every instruction perfectly until you lose service.
Now what?
You have no idea where you are because you learned the turns, not the route.
That’s what can happen when you memorize answers to interview questions.
You prepare the perfect response to “Tell me about yourself.” You polish your weakness until it sounds sufficiently weak but not alarmingly weak. You memorize a failure story and practice your answer to “Why should we hire you?”
Then the interviewer rephrases the question, asks a follow-up you weren’t expecting, or takes the conversation in another direction.
Suddenly, you’ve lost GPS service.
This is why, in Nail Job Interviews, I don’t want you memorizing scripts for difficult questions. I want you to understand why the interviewer is asking the question in the first place.
Once you understand what they need to know, it’s much easier to determine what information to provide.
Stop Trying to Find the “Right” Answer
Remember the mindset we’ve been developing throughout this series: me to you.
Candidates often hear a difficult question and immediately think, What should I say?
Try changing the question in your head:
What does this interviewer need to know?
That little shift can make even the most annoying interview questions easier to navigate.
The interviewer generally isn’t asking questions for entertainment. They’re trying to gather information to understand whether you can do the job, how you work, how you think, and whether your approach fits what their team needs.
Your job isn’t to crack the secret code and produce the magical answer.
Your job is to understand what information would be useful and provide it.
Let’s look at a few of the questions that tend to make candidates squirm.
“Tell Me About Yourself.”
This question sounds incredibly broad, which is why people struggle with it.
Where do you start?
Childhood?
College?
Your first job?
Please don’t make the interviewer regret asking.
“Tell me about yourself” isn’t an invitation to narrate your autobiography. It’s an opportunity to give the interviewer a useful framework for understanding who you are professionally and why you’re sitting in front of them.
So, go back to our core question:
What do they need to know about you?
They need the parts of your professional story most relevant to this role.
If you’re interviewing for a Director of Operations position, you don’t need to walk the interviewer chronologically through every job you’ve held since you worked the register at Dairy Queen.
Instead, give them the through-line.
Maybe your career has increasingly focused on stepping into growing organizations, identifying operational bottlenecks, and building the systems and teams needed to scale. Briefly explain how that theme developed, give them a sense of where you are now, and connect it to why this opportunity makes sense.
Think of your answer as orientation.
You’re giving the interviewer a map that says, “Here’s the part of my background that’s most important for understanding why we’re having this conversation.”
Your answer should help them know where to dig next.
If “Tell Me About Yourself” Makes Your Mind Go Blank
If you read that question and immediately felt your mind go empty, that reaction is far more common than it feels in the moment. I’ve written a whole post about that exact freeze-up feeling — you probably know more than you think you do; you just haven’t practiced pulling it out on demand yet.
“What’s Your Greatest Weakness?”
Oh, this one.
Candidates have been trying to outsmart this question since the beginning of time.
“I’m a perfectionist.”
“I work too hard.”
“I care too much.”
Please stop.
The interviewer knows what you’re doing. You know what you’re doing. Everyone in the room knows what you’re doing.
Instead of trying to find a weakness that secretly makes you sound amazing, think about what the interviewer may actually need to understand.
Can you recognize where you’re less effective?
Can you talk about it without falling apart?
Do you take responsibility for improving?
Have you actually done something about it?
That’s a much more interesting conversation than whether you’ve successfully disguised a strength as a weakness.
Choose something real, but use common sense. If you’re applying to be an accountant, this probably isn’t the moment to confess that details aren’t really your thing.
Then explain what you’ve learned and what you do differently because of that awareness.
For example, earlier in your career, you may have tended to hold on to work too long because you believed doing it yourself was faster than delegating. As your responsibilities grew, that stopped working. You had to become more deliberate about setting expectations, handing off ownership, and allowing other people to solve problems differently than you would.
That’s a weakness with a story attached.
More importantly, it demonstrates self-awareness and growth.
You’re not claiming to have conquered your weakness forever and emerged as a flawless human being. You’re showing that you understand yourself well enough to manage it.
A Deeper Dive on the Weakness Question
This question comes up so often, and trips up so many otherwise strong candidates, that it earned its own full post: how to actually answer the weaknesses question. If you want more examples beyond the framework above, that’s the place to go.
“Tell Me About a Time You Failed.”
This question makes people nervous because they assume the objective is to find a failure that doesn’t sound too much like failure.
That’s how we end up with stories like:
“I set an incredibly ambitious goal of increasing revenue by 75%, but unfortunately, I only increased it by 70%.”
Come on.
If an interviewer asks about failure, give them a failure.
Again, think about what they need to know.
Everyone screws up. What matters is what happens next.
Do you recognize your role in what went wrong? Can you take responsibility without spending ten minutes explaining why everyone else was actually to blame? Can you learn from the experience? Did that lesson change how you operate?
Choose a real example with enough substance to demonstrate those things.
Explain what you were trying to accomplish, what went wrong, and what part of the outcome you own. Then spend meaningful time on what happened afterward.
What did you learn?
What did you change?
How has that lesson affected decisions you’ve made since?
In many cases, the most useful part of your failure story isn’t the failure at all.
It’s the evidence that you became better because of it.
“Why Should I Hire You Over Someone Else?”
This question can feel uncomfortable because you probably don’t know the other candidates.
So don’t pretend you do.
You can’t credibly say you’re more experienced, strategic, collaborative, innovative, or better-looking than people you’ve never met.
Instead, bring the question back to what you do know.
You know what this employer needs, or at least you should by this point in the interview.
You know your experience.
You know the evidence you’ve prepared.
Connect them.
You might say that you can’t speak to the qualifications of other candidates, but based on what you’ve learned throughout the interview, it sounds like the company particularly needs someone who can do X, Y, and Z. Then briefly explain the experiences that demonstrate your ability to do those things.
You’re not declaring yourself the winner of a competition whose other contestants you’ve never seen.
You’re making the case that you actually have evidence to support it:
Here’s what I understand you need, and here’s why I believe I can help.
That’s a much stronger answer.
Use a Framework, Not a Script
Notice what’s happening with each of these questions.
I’m not giving you a paragraph to memorize.
I’m giving you a way to think.
For “Tell me about yourself,” orient the interviewer around the parts of your professional story that matter to this role.
For a weakness, demonstrate genuine self-awareness and show how you manage or improve it.
When you fail, own what happened and demonstrate what you learned and how you changed.
For “Why should we hire you?”, connect what you’ve learned about their needs to the evidence from your background.
Frameworks give you structure without trapping you inside specific words.
That’s important because interviews are conversations.
The interviewer may phrase the question differently. They may interrupt you. They may ask a follow-up. Something they said ten minutes earlier may change the example you want to use.
If you’ve memorized a script, those changes can throw you.
If you understand the purpose of your answer, you can adapt.
Your Evidence Bank Makes This Much Easier
This is also where the evidence bank we discussed earlier in this series becomes incredibly useful.
If you’ve already thought through experiences involving leadership, conflict, failure, change, influence, difficult decisions, learning, and results, you don’t have to invent examples while someone watches you think.
You have raw material ready.
The question simply tells you which material might be useful.
Maybe one experience could answer a question about failure, conflict, or leadership depending on which part of the story you emphasize. Because you know the experience rather than a memorized speech, you can shape it around what the interviewer actually needs to understand.
That’s preparation.
Not predicting exactly what someone will ask, but knowing your own evidence well enough to use it when you need it.
Listen Before You Answer
There’s one more piece of this that matters.
Don’t become so focused on delivering the prepared framework that you forget to listen.
The same question can mean something slightly different depending on the context.
If the interviewer has spent 20 minutes talking about a team struggling with accountability and then asks about your leadership style, that context matters.
If they’ve repeatedly emphasized how quickly priorities change and then ask about one of your failures, that context matters.
The interview is giving you information.
Use it.
Instead of thinking, Oh! Leadership question! Time for my leadership answer!, ask yourself what this particular person is trying to understand about your leadership.
Then answer that.
Learn the Route, Not the Turns
Go back to our GPS.
If you know where you’re going, losing the turn-by-turn instructions is inconvenient but not catastrophic. You can orient yourself, adjust, and keep moving toward the destination.
That’s what I want for you in an interview.
I don’t want you dependent on the interviewer asking exactly the question you practiced in exactly the way you practiced it.
I want you to understand the destination.
What does this company need?
What does this interviewer need to understand about you?
What experiences provide evidence?
What information will help them see the connection?
Once you understand those things, even difficult interview questions become less intimidating because you’re no longer searching desperately for the “right” answer.
You’re figuring out what information would be most helpful to the person asking.
That’s why Nail Job Interviews teaches frameworks and patterns instead of handing you canned responses to memorize.
Because your goal isn’t to become great at answering interview questions.
It’s to become great at understanding what the person across the table needs to know and giving them the information that helps them see whether you’re a good fit.
Want Help With the Questions That Make You Nervous?
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.
