Common Interview Questions (and How to Answer Them)

Many interview questions fall into a handful of categories: your fit for the role, your past behavior, your motivation, and what you want next. Prepare one strong answer for each category, apply a simple structure, and you can handle almost anything the interviewer asks.

Key takeaways

Expect questions about opening, experience, behavior, motivation, and salary; prepare one answer per category.
Answer the question in the first sentence, then support it with one example and a result.
Use STAR for behavioral questions and keep each answer to about 60–90 seconds.
Pick one or two strengths with evidence, and one real weakness plus how you manage it.
Rehearse out loud; memorize the shape of the answer, not the wording.

What are the most common interview questions?

Interview questions look varied, but they sort into a few jobs. The New Jersey Department of Labor’s interviewing assistance page lists common questions such as “tell me about yourself” and “why should I hire you,” and recommends preparing examples of your skills before the conversation.

The U.S. Office of Personnel Management explains that structured interviews ask every candidate the same preset questions in the same order and score answers against the same criteria, so the format is designed to compare people fairly rather than to surprise anyone. Harvard Business Review’s 2021 roundup of common interview questions (subscription) starts from the same premise: interviews are stressful, and practice and preparation help.

Category	Typical questions	What the interviewer is testing	Answer shape
Opening	“Tell me about yourself.” “Walk me through your resume.”	Whether you can summarize yourself in the employer’s terms	Present, proof, why this role
Experience	“Tell me about a project you’re proud of.” “What was your role on that team?”	Depth and ownership	Context, your actions, result
Behavioral	“Tell me about a time you disagreed with a manager.”	Evidence of how you actually work	STAR
Motivation	“Why this job?” “Why are you leaving your current role?”	Whether you understand the role and will stay	Reason, evidence, forward
Strengths and weaknesses	“What are you best at?” “What is your biggest weakness?”	Self-awareness and fit	One or two strengths with proof; one real weakness with a fix
Salary	“What are your salary expectations?”	Budget fit and whether you did your research	Ask for the range, then give a researched range
Your questions	“What questions do you have for us?”	Preparation and genuine interest	Two or three prepared questions

“Tell me about yourself” — what structure works?

Answer in three moves and stop: what you do now, one piece of proof that you are good at it, and why this role is the logical next step. That is a 30–60 second answer. It is not your life story, and it is not a repeat of your resume line by line.

Save the details for follow-up questions; the interviewer will ask about the part they find interesting.

Hypothetical example — “Tell me about yourself”

“I’m a marketing coordinator with three years of experience running email and social campaigns for a regional retailer. Most recently I owned our weekly email program from planning through reporting, and I moved it from an occasional send to a weekly schedule the whole team plans around. I’m looking for a role where I can own lifecycle strategy for a larger list, and this position is that step up.”

“Why do you want this job?” and “Why this company?”

This question tests whether you understand the role and whether you will still want it in a year. “I’m passionate about your company” does not answer it. A specific reason does: the work the role owns, a change the company is making, or a problem you have already solved somewhere else.

Connect the reason to evidence. Say what the role involves, then say what you have done that is close to it. Gallup’s Called to Coach webinar (2022) makes a related point about interviews: learn what the role, the culture, and the hiring team need before you describe your strengths, so your answer connects to their problem instead of your resume.

Hypothetical example — “Why do you want this job?”

“Two reasons. First, the role owns onboarding and lifecycle email for a product I already use, which is the work I have been doing at a smaller scale for two years. Second, the team is rebuilding its lifecycle program after a product change, and that rebuild is the part of the job I find most interesting. I want to do that work with better data and a bigger audience than I have now.”

Avoid reasons that are about you only — the commute, the title, the salary. One honest personal reason is fine if you pair it with a reason that serves the team.

“What are your strengths and weaknesses?”

For strengths, pick one or two and go deep. Gallup’s guidance on strengths questions, updated in January 2025, recommends picking one or two strengths, connecting them to what the role and team need, and explaining them in concrete terms rather than listing every strength you have. “I’m a strong communicator” is a label; “I turn messy handoffs into short written updates the team actually reads” is evidence.

For weaknesses, name a real one that is not central to the job, then say what you do about it. Gallup frames the answer around self-awareness: the interviewer is checking whether you can see yourself accurately and whether you have a system for the gap. A disguised strength (“I care too much”) reads as evasive.

Hypothetical example — strengths and weaknesses

“My strongest skill is turning a messy process into one the team can repeat. In my last role, campaign requests arrived by email and chat with no priority, so I built a simple intake form and a weekly prioritization meeting; turnaround went from about a week to two days. My weakness is impatience when decisions stall. I’ve learned to write up the options with a recommendation before the meeting, so people have something specific to react to instead of another round of discussion.”

“Tell me about a time when…” — how do you use STAR?

Behavioral questions are the ones that start with “tell me about a time.” They are not asking for a philosophy of teamwork; they are asking for one real event, with enough detail to judge how you work. Harvard Business Review’s 2025 article on the STAR method (subscription) describes the problem well in its public summary: hiring managers ask behavioral questions, and candidates struggle to decide which details matter. STAR is how you decide.

Use situation, task, action, result in four sentences: set the scene, say what you were responsible for, describe two or three specific actions, and give the outcome. Then stop talking. The interviewer will ask for the part they want to hear more about.

For more behavioral questions and a reusable story bank, see the guide to behavioral interview questions.

Hypothetical example — “Tell me about a time you had to influence without authority”

“Situation: last year I led a pricing update that depended on the sales operations team, which did not report to me. Task: I needed their data by Thursday for a Monday launch. Action: I wrote a one-page brief with the two fields I needed, met their analyst for 20 minutes, and offered to pull the data myself if they gave me access. Result: we had the data by Thursday afternoon, the launch held, and their analyst and I set up a standing 15-minute handoff for the next update.”

Note

Keep a behavioral answer to about 60–90 seconds and expect one follow-up. “What would you do differently?” is not a trap; it is how the interviewer checks whether the story is real. Have a second genuine detail ready for each story rather than improvising.

“Where do you see yourself in five years?”

Answer with growth in scope, not a title you looked up. The interviewer wants to know whether this job fits a direction you actually want, and whether you are likely to stay long enough to be worth hiring. Talk about the skills you want to own, the kind of team you want to work on, and how this role gets you there.

Keep it short and grounded. A five-year plan delivered with too much certainty sounds rehearsed; a plan with one clear direction and one honest unknown sounds like a person who has thought about it.

Hypothetical example — “Where do you see yourself in five years?”

“In five years I’d like to own lifecycle marketing end to end, ideally leading a small team or the equivalent scope. This role is the piece I’m missing: I’ve done the execution well, and I want responsibility for the strategy and the results. I’ve been deliberate about the next step rather than chasing a title.”

“Why are you leaving your current job?”

Answer forward, not backward. The interviewer is checking for risk: will you badmouth this employer the way you might badmouth your last one, and is your reason consistent with the job you are applying for? Keep the answer factual, brief, and pointed at what you want next.

Never criticize a named manager or teammate, even if the story is fair. A short, neutral explanation followed by what you are looking for reads as professional. If you were laid off or fired, say so plainly, then say what you did with the time and what you learned — one sentence each is enough.

Your situation	What to say	What to leave out
You want more scope	“I’ve grown as far as the current role allows, and I want responsibility for X.”	Complaints about your manager
You were laid off	Say it plainly, then what you did next and what you learned.	Blame and speculation about the company
Your team changed	“The team’s priorities shifted, and my role moved away from the work I do best.”	Criticism of named people
You are changing fields	“I want to move from A to B, and this role is the bridge.”	Apologizing for the move
You need better pay	“I’m looking for a role that matches the scope I’ve taken on.”	Money as the only reason

How do you answer “What are your salary expectations?”

Do not give a single number before you know the range if you can avoid it. Ask what the role is budgeted for, then answer with a range whose bottom is a figure you would accept. If the interviewer insists on a number first, give one supported by market research and say what it is based on. The full scripts, including how to handle the question when a recruiter pushes early, are in the guide to negotiating salary.

Keep the tone collaborative. A number is information, not a demand, and the interview is not the place to negotiate hard. Your goal here is to stay in the process without anchoring yourself below the band.

Hypothetical example — “What are your salary expectations?”

“I’m flexible and still learning the full scope of the role. Could you share the range budgeted for this level? I’ve been researching the market for this role in this area, and I’m confident we can find a number that works within your band.”

What should you ask the interviewer?

“What questions do you have for us?” is a real question, and a blank answer costs you. Prepare three to five that you can ask any interviewer, then pick the one that fits the conversation. Good options: what success looks like in the first 90 days, what the biggest challenge for the team is right now, and what the next step in the process is.

Ask about the work, not about perks, in a first interview. Perks questions are fine later, once the employer has decided it wants you. The interview-preparation guide has a full table of questions to ask at each stage and who to ask them.

The guide to questions to ask the interviewer covers what to ask each type of interviewer and what the answers reveal.

What should you do when you don’t know the answer?

Say you do not know, then show how you would find out. Bluffing is transparent to an experienced interviewer, and a wrong answer repeated with confidence is worse than an honest one. The honest move buys you credibility: you name the gap, then demonstrate the process you would use to close it.

Bridge to something adjacent that you do know, if the connection is genuine: a similar problem, a related system, or a time you learned a new tool quickly. Then stop. Over-explaining the gap turns one missing fact into the story of the answer.

Hypothetical example — when you don’t know the answer

“I don’t know the answer to that one. Here’s how I’d approach it: I’d pull the last two quarters of data, talk to the person closest to the process, and come back with a recommendation by the end of the week. Is that the kind of question that comes up in this role?”

What belongs on an interview answer prep checklist?

Before the interview, check that each of these is ready. If one is missing, fix that item and leave the rest alone; you do not need a perfect answer to every possible question.

One answer ready for each category: opening, experience, behavior, motivation, strengths, salary.
“Tell me about yourself” fits in about 30–60 seconds and ends with why this role.
One or two strengths, each with a concrete example and a result.
One real weakness, plus the system you use to manage it.
Five STAR stories: conflict, failure, leadership, deadline, and a piece of work you are proud of.
Two specific reasons you want this job and this company.
A short, honest answer for why you are leaving your current role.
A salary answer that asks for the range before giving a number.
Three to five questions to ask the interviewer.
A plan for what to say when you do not know the answer.

After the interview, send a short thank-you email — the guide to writing a thank-you email after an interview has templates and a timeline. Then write down the questions you were asked while they are still fresh — that list is the best preparation you can have for the next round. If the interview is on video, run the setup checklist in the guide to video interview tips first.

How we researched this guide

We build interview guides from official and practitioner sources. This page draws on the New Jersey Department of Labor’s interviewing guidance, the U.S. Office of Personnel Management’s explanation of structured interviews, Harvard Business Review’s 2021 roundup of common interview questions and its 2025 article on the STAR method (both subscription), and Gallup’s guidance on strengths questions (updated January 2025) and its 2022 Called to Coach webinar. We attribute each source beside the advice it supports and mark time-limited or paywalled material.

Example answers on this page are hypothetical. We review the guide when the underlying sources change and show the last-updated date at the top. For how we choose, cite, and correct sources, see our editorial policy.

Frequently asked questions

How many interview questions should you prepare for?

Prepare one strong answer for each category rather than hundreds of individual questions: an opening, an experience example, a few behavioral stories, your motivation, strengths and weaknesses, and salary. Five STAR stories usually cover many behavioral questions because the same story can answer different prompts. Then practice out loud so the structure holds under pressure. Quality matters more than volume here.

What if you blank during an interview?

Pause, take one breath, and ask the interviewer to repeat or rephrase the question. Then answer the part you do know, or ask for a moment to organize your thoughts — saying “let me think about the best example for a moment” buys time without sounding lost. If you truly have no example, say so and describe how you would handle the situation instead.

Should you memorize your interview answers?

Memorize the structure, not the sentences. Word-for-word answers sound recited and collapse when the interviewer asks a follow-up you did not script. Learn the beats of each story — the setup, your responsibility, the actions, the result — and say them in fresh words each time. Practicing out loud three or four times is enough to make the answer feel natural.

How should you handle salary questions in an interview?

Ask what range is budgeted for the role before you name a number, then answer with a researched range whose bottom you would accept. Avoid giving your current salary as a shortcut, and keep the conversation collaborative rather than negotiatory at this stage. The full scripts, including what to say when a recruiter pushes early, are in the guide to negotiating salary.

Do interviewers ask every candidate the same questions?

In a structured interview, yes. The U.S. Office of Personnel Management describes structured interviews as using the same preset questions, in the same order, scored against the same criteria for every candidate. Many employers use a mix of set questions and follow-ups, so prepare for both: fixed questions reward prepared stories, and follow-ups reward knowing your own examples well enough to go deeper.

How do you answer “Why should we hire you?”

Answer with a short value statement and two pieces of evidence: what you can do for this team, one example that proves it, and a sentence connecting both to the role’s priorities. Avoid generic claims like “I’m hardworking.” The interviewer is asking whether you understand the job well enough to know which of your strengths matters most here.

How do you answer “Tell me about a time you failed?”

Choose a real failure with a modest but real consequence, own your part in one sentence, and spend most of the answer on what you changed afterward. Interviewers are testing self-awareness and learning, not perfection. Avoid failures that reveal a core weakness for the job, and avoid the disguised strength (“I care too much”). End with the system or habit you now use.

Should you ask questions at the end of an interview?

Yes. Prepare three to five questions and ask two or three about the work, the team, or next steps; if the interviewer is short on time, one good question is enough. A blank answer wastes the part of the interview you control. Skip anything whose answer is on the company website, and listen to the answers rather than reading your list. Questions about salary and benefits can wait until the offer stage.

Sources and further reading

We link to primary and official sources so you can verify the details yourself.

How this guide was written. This page is part of Role Handbook, an independent career publication. We research each guide against primary and official sources, use worked examples and scripts instead of vague advice, and update pages when the underlying rules or practices change. Every page lists its sources. See our editorial policy for details and corrections.