If you keep getting interviews but no job offers, the problem usually isn't how good your answers are. It's that you're answering the interviewer's surface-level question, instead of the real question they're actually asking, so you never prove you can solve the problem they're hiring for.
The candidates getting hired faster than you aren't giving better answers. They're finding out the real question first, and answering that.
In this article, I'll show you the GAP method. It's three steps that hundreds of my clients have used to find and answer the real question, and get hired faster than 99% of professionals.
Why do I keep getting interviews but no job offers?
You keep getting interviews but no offers because you're treating the interview as an interrogation, rushing to answer each question, when it's really a consultation. You answer the question they asked, but not the problem behind it.
Let me show you what I mean. Imagine you go to see a doctor and tell them you've been suffering from headaches.
The first doctor immediately says, "Take these pills, you'll be fine."
The second doctor asks questions first. "How long has this been going on? Is it worse in the morning or the evening? What else have you tried?" Based on those answers, he gives you a more specific diagnosis.
Which doctor do you trust more? The second one, right? Because he took the time to find out what was actually wrong.
Interviews work exactly the same way. The candidate who asks the right questions is the one they trust, and the one they trust is the one they see as the solution.
It's not an interrogation. It's a consultation. And you're the doctor.
What is the interviewer really asking?
The interviewer is really asking whether you can solve the specific problem they're hiring for, but they rarely say what that problem is. So they ask a there-or-thereabouts question that roughly covers it.
After 10,000 interviews, I can tell you that nine times out of ten, hiring managers are asking questions on autopilot. That doesn't mean there's no reason behind them. They've got a very specific reason for hiring, they just don't tell you what it is.
Has their top performer just resigned? Have they landed a massive expansion project and need people for it? Or is the current team overworked and super stretched?
Unless you find out that specific reason, you'll never be able to show you've done the thing they actually care about.
Take "Why are you leaving your last job?" Nobody really cares about the surface answer. They're assessing your motivations and behaviour.
Were you forced out? Are they going to inherit someone who blames and criticises everybody from their last company? Or are you someone looking for a role where you can build a team from the ground up, which happens to be exactly what they need for that expansion project?
Here's the thing. Interviews aren't a talent competition where they're looking for the best candidate. They're looking for the lowest-risk hire.
And that risk is the gap between what they really need, their real reason for hiring, and what they think you can do. Unless you ask questions, you'll never know what that gap is.
So you walk out assuming you gave a good answer. Objectively, it could have been the best answer in the world. But to that person, with that hiring problem, it didn't close the gap, and that's what stops you getting hired.
What is the GAP method for interviews?
The GAP method is Daniel Langley's three-step interview technique: Get the context, Align to their problem, and Prove you've done it, so your answer closes the gap between what the hiring manager needs and what they've seen you do.
This is exactly what helped my client Anil. He'd spent more than six months on interviews that went okay, but he kept getting ghosted and wasn't landing the offers he wanted.
After a few conversations, we realised he was only ever answering the surface question. He never found out the deeper question he was being asked, so he never got to show what he'd actually done before. Once he changed that, he landed a $110K software developer role.
- G: Get the context. Find out the real problem the role is being hired to solve.
- A: Align to their problem. Pick the story that matches that problem, not your favourite one.
- P: Prove you've done it. Show what you did and connect it back to their problem.
How do you find out the real reason a company is hiring?
You find out the real reason a company is hiring by asking the recruiter or internal talent team four questions before the interview, then confirming it with probing questions in the interview itself. That's the G in GAP: get the context.
Most candidates walk into an interview thinking their only job is to answer questions. It's not. Your job is to prove you can close the gap you'd be hired to fill, and you can't present yourself as the solution if you don't know the problem.
So getting the context starts in your preparation. When you speak to the recruiter or the internal talent team, ask them:
- How long has the role actually been open?
- Why are they hiring right now?
- What challenges have they had filling this position so far?
- What's the real problem this role is being hired to solve?
The answers tell you the gap before you've even met the hiring manager.
But some of you will only be able to find this out in the interview, and that's where probing comes in.
You already know how to do this. When your partner says "I'm fine", you don't take that at face value. You ask a question, because you know "I'm fine" isn't the real answer.
An interview works the same way. What they ask isn't always what they want to know.
What questions should you ask before answering an interview question?
Before answering, ask one short qualifying question that turns their question into their problem. The right question depends on which of the four types of interview question you're facing.
- Behavioural ("Tell me about a time when..."). Ask: "Is this coming from something the team's dealing with right now?"
- Situational ("What would you do if..."). Ask: "Can I just check a couple of things first? How big is the team, and who owns the decision currently?" Now you know whether they need a leader, or someone who'll roll up their sleeves and get their hands dirty.
- Competency ("How do you manage stakeholders?"). Instead of the textbook answer, ask: "Which stakeholders are the hardest to manage in this role?" Now you're talking about their stakeholders, not stakeholders in general.
- Technical ("How would you solve this?"). Ask: "What's the setup today, and what have you already tried?" The last thing you want is to pitch a fix they've already tried and binned.
Every one of those questions does the same thing. It turns their question into their problem.
One question, maybe two. You're just gathering context. You're not interviewing them back.
I know what some of you are thinking. "But Dan, won't they find it odd if I start asking questions?"
The questions you ask show them you've got the right skills and experience, and that you've been there before. If you hadn't, you wouldn't know to ask them.
An amateur rushes in to give an answer. Whereas a professional asks probing, qualifying questions, because that's how you show your experience, your judgement and your expertise before you've even answered.
If you want the full breakdown of what they're really asking in the most common questions, grab the free interview guide here.
How do you tailor your answer to the interviewer's problem?
You tailor your answer by choosing the story that matches the problem they've just told you about, not the story you're most proud of. That's the A in GAP: align to their problem.
Most people have a favourite go-to story, and they'll tell it whatever the question. But the best answer is the one that closes the gap, because it shows you've already done the thing they care about.
Let me tell you something I saw happen recently. I was working with two candidates, both going for the same six-figure head of operations role.
Both had around 15 years of experience and both had run sites. On paper, there wasn't much to split them.
The hiring manager asked them both the same question: "Tell me about a time you turned around a failing team."
The first candidate went straight in with their favourite story, a system rollout they'd led across three sites. It was impressive, well rehearsed and well told. And it had nothing to do with why the hiring manager was hiring.
The second candidate asked one question first: "Is this coming from something the team's dealing with right now?"
The manager leaned in and said:
"Honestly, one of our sites is missing every target. Output's down, we've lost three supervisors this year, and our biggest customer is starting to lose patience."
Now the second candidate knew exactly which story to tell:
"In that case, the one that springs to mind is from my last role. I took over a site that was bottom of the group on every KPI. Output was down, we were losing good people, and we were on a final warning with our biggest customer."
Same experience. Same question. But one of them answered the problem, not just the question.
How do you prove you can solve their problem in an interview?
You prove it by walking them through what you did, the result you got, and then connecting it directly back to their problem. That's the P in GAP: prove you've done it.
The second candidate carried on like this:
"I spent my first two weeks on the floor with every supervisor, found the three things killing our output, and fixed those first. And I got on a weekly call with that customer, so they heard it from me, not from a report. Within six months, we were back on target, we stopped losing people, and that customer renewed. Which sounds a lot like where you are right now."
See that last line? It's the one most people miss. They tell a great result and then stop.
You have to connect it back to their problem.
Now the manager doesn't have to imagine whether you could do it. You've already shown them.
What are the most common mistakes that stop interviews turning into offers?
The most common mistakes all come from answering before you understand the problem. Here are the ones I see most, with the fix for each.
- Answering the surface question. Fix: ask one qualifying question to find the real one first.
- Telling your favourite story every time. Fix: pick the story that matches the problem they've just described.
- Skipping the prep questions. Fix: ask the recruiter or talent team the four context questions before you walk into the interview.
- Stopping at the result. Fix: finish with a line that connects your result to their situation.
- Turning it into an interrogation of them. Fix: one question, maybe two. You're gathering context, not interviewing them back.
The bottom line
If you're getting interviews but no offers, stop answering their surface-level questions and find out why they're asking them. Get the context, align to their problem, and prove you've done it.
An amateur gives the best answer they can. A professional gives the right answer, because they asked first.
What's your next step?
If you want to see how your CV holds up before your next interview, try the free Six Figure CV tool. Upload your CV and get an instant score with specific fixes.
And if you want to work on this with me directly, here's where to start.