Most candidates prepare for interviews by rehearsing what they want to say. That's the wrong move. The best interviewers aren't listening for your prepared speech they're watching how you think under pressure, how self-aware you are, and whether you actually understand the role you're applying for. That gap between what candidates prepare and what interviewers actually want is where offers get lost. These 15 questions are the ones that trip people up most consistently, and here's exactly how to handle each one.
The Questions That Seem Simple But Aren't
"Tell me about yourself."
This is not an invitation to recite your resume. The interviewer has your resume they just read it. What they want is a coherent narrative: who you are professionally, what's driven your career, and why you're sitting in front of them right now. Think of it as a 90-second professional story with a clear beginning, middle, and landing point.
A strong structure: start with your current role and core strength, briefly trace back to what led you there, then pivot to why this specific opportunity makes sense right now. "I've spent the last six years in B2B SaaS sales, most recently leading a team of eight at a mid-stage startup where we grew annual recurring revenue from $4M to $11M. Before that I was in individual contributor roles, which gave me a real foundation before I moved into management. I'm looking at this role because you're at a similar growth stage and the problems you're solving in the healthcare vertical are exactly where I want to be building."
That's it. Concise, specific, forward-looking. You're not telling your life story you're making a case.
"What's your greatest weakness?"
I've watched candidates torpedo otherwise strong interviews with two kinds of bad answers here: the fake weakness ("I work too hard!") and the confession booth (listing three real problems in painful detail). Neither works. Interviewers have heard the fake ones a thousand times, and the confession approach just creates doubt.
What actually works is naming a real, plausible weakness one that isn't catastrophic for the role and then showing what you've done about it. "I've historically been reluctant to delegate. I'd rather do something myself than risk it being done poorly. Over the last year I've been deliberate about it I actually started using a simple framework where I evaluate which tasks only I can do versus which ones are growth opportunities for my team. It's changed how I manage, and honestly, my team's output has improved because of it." Real, self-aware, with evidence of growth. That's the target.
The Behavioral Questions That Require Real Stories
Behavioral questions anything that starts with "Tell me about a time when..." or "Give me an example of..." are the most predictable part of any interview. They're also where candidates most consistently underperform, because they answer in vague generalities instead of specific stories. Using the STAR method for behavioral questions gives you a reliable structure: Situation, Task, Action, Result. It keeps your answer focused and ensures you actually land the story somewhere meaningful.
"Tell me about a time you failed."
The failure question is really an accountability question. The interviewer isn't hoping you'll confess to something catastrophic they want to see that you can own a mistake without making excuses, and that you extracted something useful from it. Pick a real failure (not a minor hiccup), own your role in it clearly, and be specific about what you learned and changed afterward. Candidates who deflect or minimize failure almost always come across worse than candidates who tell a genuine story with clarity and maturity.
"Describe a conflict with a coworker and how you handled it."
Two traps here: making yourself sound like a saint who's never had a real conflict, or making your former colleague sound like a villain. Neither is credible. A good answer names an actual disagreement ideally a substantive professional one, not a personality clash describes how you engaged with it directly rather than avoiding it, and shows a resolution that was at least somewhat constructive. You don't have to say it ended perfectly. Saying "we didn't fully resolve the underlying tension, but we agreed on a working approach that let us ship the project" is honest and still demonstrates maturity.
Questions About Your Motivations and Fit
"Why are you leaving your current job?"
Here's the thing interviewers know most people leave for a mix of push factors (something isn't working) and pull factors (something better is available). You don't have to pretend it's only the latter. But you do need to keep it professional. Venting about your manager is a hard no. So is being so vague that you sound evasive.
The honest-but-professional version might sound like: "I've learned a lot in this role, but the company went through a reorg last year and the path forward became less clear. I've also hit a ceiling in terms of scope I'm ready to take on a larger book of business than my current structure allows." That's real. It doesn't throw anyone under the bus. And it pivots naturally into why this opportunity makes sense.
"Where do you see yourself in five years?"
Nobody has a perfectly mapped five-year plan and interviewers know that. What they're actually probing: Are you ambitious enough to have goals? Are those goals compatible with what this company can offer? Do you have self-awareness about your trajectory?
You don't need to say you want the interviewer's exact job (that reads as flattery). You do need to connect your goals to something the company can plausibly offer. "In five years I'd like to be leading a team and owning a larger strategic function either product development or go-to-market strategy. Given where you're headed in the mid-market segment, that feels like the direction this role could grow." Ambitious, grounded, company-aware.
"Why do you want to work here?"
If you can't answer this with specifics, you haven't done enough research and interviewers can tell. Generic answers like "I love your company culture and innovation" are completely worthless. Researching the company culture beforehand gives you the ammunition to give an answer that actually distinguishes you. Reference a product decision, a strategic shift, something the CEO said publicly, a recent funding round and what it signals anything that shows you engaged with the company as a real entity before walking in the door.
The Salary and Negotiation Questions
"What are your salary expectations?"
This question is an anchor-setting exercise and the person who names a number first often loses ground. If you're early in the process, it's reasonable to defer: "I'd want to learn more about the full scope of responsibilities before naming a number can you share the budgeted range for this role?" Most companies have a range; asking for it is not unreasonable.
If you're pushed to answer, come in with a researched range based on market data use sources like the Bureau of Labor Statistics, LinkedIn Salary, Levels.fyi for tech roles, or Glassdoor, and be able to say where your number comes from. Anchoring with data is far more persuasive than anchoring with a wish figure.
"Are you interviewing with other companies?"
Yes, if you are, say so diplomatically. "I'm in conversations with a couple of other companies, though I'm being selective. This role is genuinely at the top of my list because of X." It creates honest urgency without manufactured pressure. If you're not interviewing elsewhere and the silence would feel awkward, you can simply say you're being thoughtful and focused rather than casting a wide net.
