Job interviews look far more alike from the interviewer's side of the table than from the candidate's. Most revolve around the same 10 or 12 questions, with variations in wording depending on the company and the person asking. That repetition is an advantage: it makes it possible to walk in with answers already thought through, and the gap between improvising and bringing a prepared structure shows within the first five minutes.
This guide covers the most common job interview questions, grouped by what the interviewer is trying to find out with each one, along with a simple method for structuring answers without sounding scripted.
In this guide
A method before the answers: situation, action, result
Before going through specific questions, it helps to settle the shape of the answer. Almost every question about past experience (the ones that start with "tell me about a time when...") works well with the same three-step structure, a compact version of the STAR method that many US hiring teams use to score behavioral interviews:
- Situation. The minimum context needed to follow the story, in one or two sentences: where, when, and what was at stake.
- Action. What the candidate specifically did. This is the core of the answer and where most of the time should go, with first-person verbs: "I proposed a new approval workflow," "I negotiated the deadline with the vendor."
- Result. What changed because of that action, with a number when one exists: hours saved, revenue generated, tickets resolved.
An answer with this structure runs 60 to 90 seconds, the comfortable range for the listener. Past two minutes attention starts to drop; under 30 seconds it sounds like there is nothing to tell.
The two most common mistakes are opposites: staying stuck in the situation (a full minute of context and the action dispatched in one sentence) and reporting team results without clarifying the candidate's own contribution. The interviewer wants to know what the candidate did, not what the department did.
Questions about the candidate
These open almost every interview. They are not after facts (those are already on the resume) but after how the person presents themselves, what they prioritize without a script, and how they communicate under mild pressure.
"Tell me about yourself"
What it tests: the ability to summarize and to exercise judgment. The question is deliberately open: what matters is what the candidate chooses to tell and in what order.
How to answer: with a 60-to-90-second professional overview in three movements: what the candidate does today, what led to this point, and what they are looking for now (ideally, something this role offers). No personal biography and no date-by-date recital of the resume. The full answer, with examples by experience level, is in the guide on how to answer "tell me about yourself".
"What are your strengths and weaknesses?"
What it tests: self-awareness and honesty. Strengths show whether the profile fits the job; the weakness shows whether the person knows themselves and works on their weak spots, or will hide them inside the team too.
How to answer: strengths with evidence. "I'm organized" is less convincing than an example where that organization produced a concrete result. The weakness has to be real and not a strength in disguise: "I'm too much of a perfectionist" reads as evasive and works against the candidate. A genuine, contained weakness, paired with what is being done to correct it, works much better. The full breakdown is in the guide on strengths and weaknesses.
"How would your coworkers describe you?"
What it tests: the same thing as the previous question from another angle, plus consistency: if the self-description and the supposed view of coworkers never overlap, something is made up.
How to answer: with two or three traits a reference check could confirm, anchored in situations. "They'd say I'm the person they message when a customer escalates" gives a trait and its evidence in one sentence.
Questions about experience
This is where the situation-action-result method applies in full. These questions most clearly reveal who came prepared, because specific cases do not improvise well.
"Tell me about an accomplishment you're proud of"
What it tests: what the candidate considers valuable and whether they can take credit without inflating it. An accomplishment chosen with good judgment says as much as the accomplishment itself.
How to answer: by picking a case relevant to the role, not the most spectacular one of the career. An achievement from eight years ago in another industry counts for less than a modest, recent one in a context similar to the posting.
"Tell me about a conflict with a coworker and how it was resolved"
What it tests: emotional maturity. Nobody expects a history without friction; what is expected is the ability to work through it without burning the relationship.
How to answer: with a real conflict of moderate intensity (a disagreement over priorities, a misunderstanding about scope), keeping the story centered on the resolution rather than the drama. "I've never had a conflict" is the worst way out: it sounds like evasion or like very little experience working with others.
"Why did you leave your last job?"
What it tests: red flags. Terminations that go unmentioned, patterns of contentious exits, impulsiveness. Also the grace with which the candidate handles uncomfortable topics.
How to answer: briefly, honestly, and looking forward. "I had done what I could in that role and I'm looking for a challenge it no longer offered" works; an honest account of a layoff also works, told without resentment. What never works is the bitter detail.
Speaking badly of a former manager or employer is one of the fastest rejections there is. The interviewer does not know that job, but they are watching how the candidate talks about people who are not in the room.
Questions about motivation
This group measures whether the application is specific or one of fifty identical ones. Candidates who chose the company for a reason accept offers faster and quit less in the first year.
"Why do you want to work here?"
What it tests: whether the candidate did any research before showing up. It separates someone who read two pages of the company website from someone who only read the job title.
How to answer: by connecting one or two concrete facts about the company (a product, a market, a way of working) with the candidate's own background. The generic "because you're a leader in the industry" gets said in every interview and adds nothing in any of them.
"Where do you see yourself in five years?"
What it tests: reasonable ambition and likelihood of staying. Replacing someone who leaves early costs a company several months of salary; the interviewer wants to know whether this role is a destination or a two-month layover.
How to answer: with a direction rather than an exact title: deepening technical expertise, coordinating projects, owning an area. That future has to be reachable from the role on offer; if it is not, the interviewer concludes the departure is only a matter of time.
"Why should we hire you?"
What it tests: the ability to make a concise case. It is the invitation to close the sale, and many candidates waste it on generalities.
How to answer: with two or three strengths mapped against what the posting asks for, in under a minute. If the posting asks for support experience and CRM skills, the answer names exactly that with the candidate's own evidence, not a list of abstract virtues.
The uncomfortable questions
Every serious interviewer asks at least one question designed to take the candidate off script. They are not traps: they yield the most information, because they show how the person reacts when there is no rehearsed answer.
"What are your salary expectations?"
What it tests: market knowledge and confidence. A number far below the range suggests inexperience or desperation; one far above, a disconnect from the role.
How to answer: with a range researched before the interview (Glassdoor, LinkedIn, and salary surveys for the field give a reference in 20 minutes), noting that there is flexibility depending on the total package. In states with pay transparency laws, such as California, Colorado, New York, and Washington, the posting already lists a range and the answer can be anchored to it. A range leaves room to negotiate without being ruled out over a single figure.
"I see a gap on your resume. What happened?"
What it tests: honesty and how a sensitive topic is handled. The gap itself worries interviewers less than a confusing or defensive explanation.
How to answer: in one or two sentences, pivoting to the present: what was done during that time (school, caregiving, a personal project, a selective search) and why this is the moment to come back. A short, calm explanation closes the topic; a long, nervous one makes it bigger.
"Do you have any questions for us?"
What it tests: genuine interest. It closes almost every interview, and many candidates waste it with a "no, everything's clear" that communicates the opposite of what they intend.
How to answer: with two or three prepared questions about the team, the challenges of the role, or how success is measured. What to ask, and what to avoid, is covered in the guide on questions to ask in an interview.
Avoid and better: three answers compared
The difference between an answer that gets a candidate rejected and one that helps rarely lies in the content; it lies in the framing. Three cases, each told two ways:
| Question | Avoid | Better |
|---|---|---|
| "Why did you leave your last job?" | "The environment was toxic and my manager never valued anything I did." | "I learned a lot in three years, but the role had no room left to grow. I'm looking for a team where I can lead projects, like the ones this position involves." |
| "What is your biggest weakness?" | "I'm too much of a perfectionist, I'm really hard on myself." | "I struggled with delegating. I started documenting my processes so others could pick them up, and over the past year I handed two full workstreams to the team." |
| "Why should we hire you?" | "I'm proactive, responsible, and a fast learner." | "The posting asks for support experience and HubSpot. I've spent three years resolving about 40 tickets a day in that CRM, with an average satisfaction score of 4.6 out of 5." |
In every row the version that works replaces adjectives with facts, drops the negative charge, and connects the answer to the role. None requires inventing anything.
Practicing out loud, the step almost nobody takes
Reading model answers gets a candidate halfway there. The other half is saying them out loud, because an answer that reads smoothly can come out choppy the first time it is spoken, and that should not happen in front of the interviewer.
Three ways to practice, in increasing order of realism: alone and out loud (catches sentences that do not flow), with another person playing interviewer (adds social pressure), or with an AI interview simulator that asks role-specific questions, follows up, and delivers feedback. How that works is explained in the guide on mock interviews with AI.
Practicing is not memorizing. An answer recited word for word sounds artificial and collapses at the first follow-up. Memorize the structure and the facts (numbers, names, dates), not the text.
Frequently asked questions
What are the most common job interview questions?
"Tell me about yourself," strengths and weaknesses, why you left your last job, why this company, a notable accomplishment, a conflict you resolved, salary expectations, and whether you have questions. Preparing those eight covers most of any initial interview.
What is the situation-action-result method?
It is a three-step structure for answering questions about experience: the context in one or two sentences, then the specific action the candidate took, and finally the result, with a number when one exists. It keeps answers between 60 and 90 seconds and is a compact version of the STAR method used in behavioral interviews.
How should I answer the salary expectations question?
With a range researched before the interview, drawn from sites like Glassdoor and salary surveys for the field, while noting flexibility depending on the total package. Where the posting already lists a pay range, anchor to it. A range leaves room to negotiate without being ruled out over a single number.
Is it bad to say "I don't know" in an interview?
Not if it is handled well. Admitting that something is unfamiliar and explaining how you would find out conveys honesty and judgment, two traits interviewers value. What gets a candidate rejected is inventing an answer and defending it.
How long should each answer be?
Between 60 and 90 seconds for open-ended questions, and less for factual ones. Past two minutes the interviewer's attention drops and the answer loses force even if the content is good. When in doubt, close early and offer to expand.