The Most Common Interview Questions & How to Answer Them (with examples)

There are roughly two hundred questions an interviewer could ask you. In practice, they ask about twelve. The same twelve, in slightly different costumes, across every company from a Riyadh startup to Google. If you can answer those twelve well — really answer them, out loud, in under ninety seconds each — you are prepared for the behavioral portion of almost any interview you will ever take.

This is the hub. Below are the questions that come up in nearly every interview, the single framework that structures most of the answers, and a worked example for each. Where a question deserves its own deep dive, there's a link to it. Read this end to end once, then use it as the index you come back to before each interview.

Why the same questions keep coming back

Interviewers are not trying to surprise you. They have a job to fill, a short window to assess you, and a hiring committee they have to convince afterward. The "common" questions survive because each one extracts a specific signal efficiently:

• "Walk me through your resume" tests whether you understand what matters about your own career.
• "Tell me about a time you failed" tests self-awareness and whether you learn.
• "Why do you want to work here" tests whether you did the work to understand them.
• "Where do you see yourself in five years" tests whether your trajectory fits the role they're filling.

Every common question is a proxy for a hiring decision: Can this person do the job? Will they make my team better? Are they going to leave in eight months? Once you see the question behind the question, your answers stop being recitations and start being evidence.

The most common mistake is treating these as trivia to memorize. They aren't. They're prompts to demonstrate judgment. The framework below is how you demonstrate it consistently.

The one framework that answers most of them: STAR

Most behavioral questions start with "Tell me about a time…" or "Give me an example of…". For all of those, use STAR. It's not a gimmick — it's the structure that forces you to include the parts interviewers are actually scoring, and cut the parts they aren't.

S — Situation (10–15 seconds). The minimum context needed to understand the stakes. Where you were, what the problem was, why it mattered. Not the company's founding story. Two or three sentences.

T — Task (5–10 seconds). What you specifically were responsible for. This is where most people stay vague ("we needed to fix it"). Say what you owned.

A — Action (30–45 seconds). The heart of the answer. What you did, the decisions you made, the trade-offs you weighed. Use "I," not "we." The interviewer is hiring you, not your old team. This section should be the longest.

R — Result (10–15 seconds). The outcome, with a number where one exists. Then one sentence on what you learned or would do differently — this is what separates a senior answer from a junior one.

STAR in practice

Question: "Tell me about a time you had to deliver under a tight deadline."

(S) "Last year our biggest client threatened to churn unless we shipped a reporting feature they'd been promised, and we had three weeks. (T) I owned the delivery end to end as the lead engineer. (A) I cut the scope to the two reports that actually drove their renewal decision and deferred the rest, paired with our designer to lock the spec in two days instead of two weeks, and ran a daily 15-minute sync to catch blockers early. When QA found a data bug four days out, I made the call to ship behind a feature flag and roll it out to that one client first. (R) We delivered in 19 days, the client renewed a 240K contract, and we kept the feature-flag rollout pattern as the team's default for risky launches."

That's about 60 seconds. Notice the trade-off (cut scope), the judgment call under pressure (feature flag), the number (240K), and the durable lesson (new default). That's a senior answer.

The common failure is spending 40 seconds on Situation and 5 on Action. Invert it. The Action is the only part that's actually about you.

The questions you will almost certainly be asked

1. "Walk me through your resume" / "Tell me about yourself"

This is the opener in roughly 90% of interviews, and the first thirty seconds set the frame for everything after. The mistake is reciting your resume chronologically. The fix is a 90-second narrative: a one-line theme, two or three proof points with numbers, and a bridge to why you're in this room.

Full breakdown with a worked rebuild from four minutes down to 87 seconds: How to Answer "Walk Me Through Your Resume" in 90 Seconds.

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

Tests whether you did the homework or you're spraying applications. "I admire your culture" is a non-answer. A strong one connects a specific thing about the company — a product bet, a market position, a problem they've publicly said they're solving — to something specific about you.

The structure that avoids sounding rehearsed: How to Answer "Why Do You Want to Work Here" Without Sounding Rehearsed.

3. "Why should we hire you?"

This is your closing argument, not a humility contest. The interviewer is asking you to make their decision easy. The move is to map your two or three strongest, most relevant proof points directly onto the requirements they care about most — and to say it with the confidence of someone who's already done the job.

How to land it without arrogance or apology: How to Answer "Why Should We Hire You" Without Bragging or Begging.

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

A trap disguised as small talk. They're not asking for your life plan — they're checking whether you'll grow into the role or use it as a stepping stone and leave. The strong answer shows direction and ambition that the role itself can satisfy.

The senior-candidate version that signals commitment without boxing you in: How to Answer "Where Do You See Yourself in 5 Years" as a Senior Candidate.

5. "Tell me about a time you failed" / "What's your biggest weakness?"

The single most fumbled pair. "I work too hard" is an immediate red flag — it signals you either lack self-awareness or won't be honest. The winning structure: a real failure or weakness, owned without excuses, followed by the concrete system you built to fix it and the evidence it worked. The growth is the answer, not the flaw.

Use STAR for the failure question and put the R — what you learned and changed — at the center. For weakness, name a genuine one that isn't core to the job, then show the correction in motion.

6. "Tell me about a conflict with a coworker"

They're assessing whether you're someone the team can work with under stress. The trap is making your coworker the villain. The strong answer is balanced: you describe the disagreement fairly, show that you sought to understand their position, explain how you de-escalated or found common ground, and end with a constructive outcome. STAR fits perfectly here — and keep the "R" about the working relationship, not just being proven right.

7. "Why are you leaving your current job?" / the career-gap question

Both are landmines because honesty and tact pull in opposite directions. Never badmouth a current employer — it tells the interviewer how you'll talk about them one day. Frame the move toward something (growth, scope, a problem you want to solve), not away from something.

If you have an employment gap, the worst move is hiding it or apologizing for it. Own it in one calm sentence and pivot to what you did with the time and what you bring now: How to Explain a Career Gap Honestly in an Interview.

8. "Tell me about a time you led / influenced without authority"

The leadership signal, asked at every level above entry. Even individual contributors get a version of it. Use STAR, and make the Action section about how you moved people who didn't report to you — building the case with data, addressing the skeptic directly, trading something to get buy-in. The result should show the team outcome, not just yours.

9. The curveball you didn't prepare for

"How many gas stations are in Riyadh?" "Sell me this pen." "What would your worst manager say about you?" Curveballs aren't testing the answer — they're testing how you behave when you don't have one. The skill is staying composed, thinking out loud in a structured way, and showing your reasoning instead of freezing or bluffing.

The tactics for handling anything you didn't see coming: How to Handle Curveball Interview Questions Without Freezing.

A quick-reference table

The mistakes that sink otherwise strong candidates

Rambling. The number-one killer. A 45-minute interview has room for maybe six to eight real answers. A three-minute answer to a 90-second question burns the time you needed for your best story. Brevity reads as seniority.

"We" instead of "I." Interviewers hire individuals. If every sentence is "we," they can't tell what you did. Use "we" for context, "I" for your actions.

No numbers. "We improved performance" is forgettable. "We cut page-load time from 4.2 seconds to 900 milliseconds, which lifted checkout conversion 11%" is a hire signal. Quantify everything you can.

Memorized scripts. A word-for-word recited answer sounds robotic and falls apart the moment the interviewer asks a follow-up. Memorize the structure and the proof points, not the sentences.

Treating it as a quiz. The questions are prompts to demonstrate judgment, not facts to retrieve. The candidate who shows how they think beats the one who recites the "right" answer every time.

How to actually prepare (not just read)

Reading this list is the easy 20%. The hard 80% is saying the answers out loud, with a timer, until the cadence is natural and the numbers come automatically. Here's a prep sequence that works:

1. Build your story bank. Write 6–8 STAR stories from your real experience — one each for failure, conflict, leadership, tight deadline, ambiguity, and your single biggest win. Most behavioral questions are answerable by reframing one of these.
2. Map stories to questions. For each common question above, note which story you'd reach for. You want flexibility, not a memorized script.
3. Time yourself out loud. Reading isn't practice. Speaking is. Almost everyone runs 40% longer than they think. Record yourself or run a live mock.
4. Get the follow-ups. The real test is the second and third question after your prepared answer. That's where unprepared candidates unravel.

This last part is exactly why a live mock matters more than a written script. IntervYou puts you in front of a three-voice panel — an HR recruiter, the hiring manager, and a future peer — tuned to the exact role and seniority you're targeting, in English or Arabic. It asks the common questions cold, follows up like a real interviewer, and gives you transcript-grounded feedback on where you rambled, where you said "we," and where you forgot the number. You get three full interviews free, no card required.

After the interview, don't forget the part most candidates skip — the follow-up. A good note keeps you top of mind without looking anxious: How to Follow Up After an Interview Without Seeming Desperate. And remember the interview runs both ways: the questions you ask at the end are part of how you're scored. The sharp ones signal seniority: The 5 Questions to Ask Your Interviewer That Show You're Senior.

Frequently asked questions

What are the most common interview questions?

Across almost every interview, the recurring ones are: "Walk me through your resume" (or "Tell me about yourself"), "Why do you want to work here?", "Why should we hire you?", "Where do you see yourself in five years?", "Tell me about a time you failed," "What's your biggest weakness?", "Tell me about a conflict with a coworker," "Why are you leaving your job?", and at least one curveball. If you can answer those nine well, you're prepared for the behavioral portion of most interviews.

What is the STAR method and when should I use it?

STAR stands for Situation, Task, Action, Result. Use it for any question that starts with "Tell me about a time…" or "Give me an example of…". Keep the Situation and Task short, make the Action the longest part (using "I," not "we"), and end the Result with a number plus what you learned. It works because it forces you to include exactly the parts interviewers are scoring and cut the rest.

How long should my interview answers be?

For the "tell me about yourself" opener, aim for 70–90 seconds. For behavioral STAR answers, 60–90 seconds is the sweet spot. Most candidates run far longer than they realize, which burns the limited time in the interview and reads as an inability to prioritize. Time yourself out loud — brevity consistently signals seniority.

The questions are predictable. Your answers shouldn't be generic. Pick three of the questions above, write the STAR version, and then — this is the part that matters — say them out loud against a real interviewer that pushes back.

Start a free mock interview →

Keep preparing

• How to Answer "Walk Me Through Your Resume" in 90 Seconds
• How to Answer "Why Do You Want to Work Here" Without Sounding Rehearsed
• How to Answer "Why Should We Hire You" Without Bragging or Begging
• How to Answer "Where Do You See Yourself in 5 Years" as a Senior Candidate
• How to Explain a Career Gap Honestly in an Interview
• How to Handle Curveball Interview Questions Without Freezing
• How to Follow Up After an Interview Without Seeming Desperate
• The 5 Questions to Ask Your Interviewer That Show You're Senior