Every interview feels unique when you're in it. Stepping back, though: the questions are almost never unique.

Across industries, seniority levels, and countries, interviewers cycle through the same roughly 20 questions. Some phrased differently. Some dressed up as "behavioral." Same questions underneath.

Prepare these 20 and you're ready for 80–90% of what any interview throws at you. Here they are, with the frameworks to answer each cleanly.

First, the Framework Every Behavioral Answer Needs: STAR

Before the questions — one framework. Most interview questions are behavioral ("Tell me about a time when…"). They're asking you to describe a real past situation. The structure that wins every time is STAR:

Situation: Set the scene in one or two sentences. What was happening, when, with whom?
Task: What was your specific responsibility or challenge?
Action: What did you (not your team — you) actually do? This should be the longest part.
Result: What was the outcome? Quantify where possible.

Don't label the sections when you speak. Just flow through them. And keep each answer to 90 seconds or so. Beyond that, interviewers tune out.

The Questions

1. "Tell me about yourself."

Not a biography. A 60-second professional summary that positions you for this specific role.

Structure: Present (current role + what you do) → Past (two or three career highlights that led here) → Future (why you're now looking, why this role).

Avoid: starting with where you grew up, what your parents did, or your college major. Interviewers want your professional arc, not your life story.

2. "Why are you interested in this role?"

Two things to show: (1) you actually understand the role, (2) you have a specific reason you'd thrive in it.

"Your posting mentions building out the analytics function from scratch. At my last company, I was the second analyst hired and built that team's tooling and process. That specific greenfield challenge is exactly what I'm looking for next."

3. "Why do you want to work here?"

Reference something specific about the company. Their product, their strategic direction, their engineering culture, a recent announcement, a team member you respect. Not "I admire your mission" — that's generic enough to apply to 500 companies.

4. "Why are you leaving your current role?" (Or "Why did you leave X?")

Honest, forward-looking, short.

✅ "I've outgrown the technical scope and I'm looking for something with more complexity."
✅ "The company's strategy shifted away from the work I was hired for."
❌ Anything negative about your current employer, your manager, or your team. Interviewers interpret that as a flag, even when it's warranted.

5. "What's your biggest weakness?"

The cliché answer ("I'm a perfectionist") is dead. Interviewers want honesty.

Pick a real weakness that's not disqualifying for the role, describe what you're doing to address it, and show self-awareness.

"I used to struggle with delegating — I'd hold onto work because I wanted it done my way. My manager flagged it two years ago and I've been consciously pushing work down. I still catch myself sometimes, but it's improved a lot."

6. "What's your biggest strength?"

Pick one. Be specific. Back it with evidence.

"Pattern recognition across complex data. At [company], I spotted a customer behavior pattern that had been sitting in our analytics for two years. We built a retention campaign around it that cut churn by 9%."

7. "Tell me about a time you failed."

They're not testing whether you've failed — everyone has. They're testing whether you can:

Own it honestly.
Explain what you learned.
Show you've applied the lesson since.

Pick a real failure that wasn't catastrophic. Don't pick something that makes you look incompetent for the role. Don't pick something that was entirely someone else's fault (even if it was).

8. "Tell me about a time you handled a difficult colleague / conflict at work."

STAR method. Pick a situation where the conflict was real, your actions were reasonable, and the resolution was constructive. Avoid anything that makes you look vindictive or politically aggressive.

Key move: show empathy for the other person's perspective, even if you ultimately disagreed with them.

9. "Tell me about a time you led a team / project."

If you haven't formally managed people, lead with project leadership, technical leadership, or mentoring. Describe your responsibility, the scope, the team size, what you did, and the outcome.

Don't say "we" the whole time. Interviewers are trying to figure out what you did. Be specific.

10. "Tell me about a time you had to make a difficult decision with incomplete information."

Shows judgment. The structure:

The decision you faced
The information you did have
How you weighted the risks
What you decided
What happened

A good answer admits you weren't 100% sure. That's the point — interviewers are checking your reasoning under ambiguity, not your batting average.

11. "How do you handle stress / tight deadlines?"

Don't say "I thrive under pressure." Everyone says that. Describe what you actually do:

"I break the work into blocks, communicate what I can and can't deliver early, and protect focus time. At [company], I had 48 hours to deliver a board deck and a client presentation. I renegotiated the client deadline by two days, blocked out the morning for the board work, and delivered both on time."

12. "Where do you see yourself in five years?"

Not a trap if you answer honestly. Show that your five-year arc is compatible with this role.

"I want to be leading a team of 4–6 by then, ideally in a senior IC role or first-line manager position. This role's scope is a strong stepping stone — I'd grow into the next level from here."

Don't say "I want your job" (too aggressive) or "I'm not sure" (too passive).

13. "Why should we hire you?"

Your 60-second closer. Pick the two or three strongest matches between your experience and their needs. Make the pitch.

"Three reasons. One, I've led this exact kind of migration before — same tools, same scale. Two, I've mentored junior engineers, which you mentioned is important for this role. Three, I'm genuinely interested in the problem space, which means I'll ramp faster than an external hire who sees it as just another job."

14. "What are your salary expectations?"

Research first. Know the range for this role, in this city, at this seniority level.

Three approaches, depending on the stage:

Early (screening call): "I want to learn more about the scope of the role before committing to a number. Could you share the budgeted range?"
Middle: Give a range, not a point. "Based on my research and experience, I'm targeting €X to €Y."
Offer stage: This is where you negotiate — see our salary negotiation guide for scripts.

15. "Do you have any experience with [specific technical skill / tool]?"

Answer honestly. If yes, give a quick example. If no, say so — and describe the closest thing you do have experience with, and how quickly you've picked up similar tools in the past.

Lying here catches up to you within a week on the job. Don't.

16. "Describe a time you went above and beyond."

Specific. Quantified. The action you took that wasn't in your job description, and what changed because of it.

Avoid: vague claims about "always giving 110%." That's a platitude, not an answer.

17. "What motivates you at work?"

Authentic is better than impressive. Some good directions:

Solving hard technical problems
Shipping things that real users actually use
Mentoring and helping others grow
Building from zero / greenfield work
Impact on a mission you believe in

Pick one or two that are actually true. Don't list everything.

18. "How do you handle receiving difficult feedback?"

Interviewers want to know you're coachable. Describe a specific instance where you received critical feedback, processed it, and acted on it.

"My previous manager told me I was over-explaining in stand-ups and it was slowing the team down. I was defensive at first, then I watched myself in the next few and saw she was right. I cut my updates to 30 seconds and it made the meetings much better."

19. "Do you have any questions for us?"

You must have questions. "No, I think you've covered everything" is a silent red flag in most interviewer rubrics.

Good questions:

"What does success look like in this role at the 90-day and 1-year mark?"
"What's the biggest challenge the person in this role will face in the first six months?"
"How does the team measure impact — what metrics matter?"
"Why is this role open? Is this a new position or a backfill?"
"What's the team's biggest frustration right now?"

Avoid: salary and benefits at early stages, questions you could have answered from their website, anything that sounds like you're not sure you want the job.

20. "Anything else you'd like us to know?"

Your second chance at a pitch. Use it if there's something important that didn't come up. If not, reinforce why you're a fit and express clear interest in moving forward.

"I just want to say — this is the clearest fit I've seen in my current search, and I'd love to move to the next stage. Thanks for a great conversation."

The Three Things Every Answer Should Have

Regardless of the specific question, recruiters are listening for three things:

Specificity. A specific situation, a specific action, a specific result. Not generalities.
Ownership. What you did, not what your team did.
Self-awareness. Understanding the context, the other people involved, and what you'd do differently next time.

Generic answers lose. Specific, honest, self-aware answers win — in almost any interview, almost anywhere.

The Preparation That Actually Works

Don't memorize answers. Memorization makes you sound rehearsed, and interviewers catch it.

Instead:

Prepare 3–4 STAR stories from your career that you can adapt to different questions. A time you led a project. A time you failed. A time you handled conflict. A time you made a tough decision. Most of the 20 questions above can be answered from one of these stories.
Record yourself answering five of these questions out loud. Listen back. You'll hear every filler word, every hedge, every time you go too long. Fix the top three patterns you notice.
Know the company and the role cold. Ten minutes on their website and blog. Five minutes on the team members you can find on LinkedIn. The effort is visible.

The AI Interview Prep Shortcut

If you'd rather prep with a coach who knows the specific role and company you're interviewing for, Appliqu's AI Interview Prep is built for exactly this. After Appliqu lands you an interview, the agent switches into prep mode — generating likely questions based on the role, the company, and the interviewer if known, and coaching your answers with specific feedback.

It's not a replacement for your own prep. It's a faster version of it.

Appliqu lands you the interview — then helps you prep for it. Start free at appliqu.com →

20 Interview Questions You'll Definitely Be Asked (and How to Prepare)