30 Common Interview Questions and How to Answer Them
The 30 most common interview questions, grouped by what they test, each with a one-line answer strategy. Includes a worked STAR example, a table of interviewer intent, and how to practice with mock interviews built from the real job description.
The most common interview questions and answers fall into five groups: about you, behavioral, role and company fit, tricky questions, and the questions you ask them. Answer behavioral questions with STAR — situation, task, action, result — and answer everything else with a short, specific claim followed by one piece of evidence.
What is the STAR method and how do you use it?
STAR is a four-part structure for answering behavioral questions: Situation, Task, Action, Result. You describe the setting in one sentence, state what you were responsible for, explain what you actually did in two or three sentences, then give the outcome. It works because it forces the answer to end on evidence instead of trailing off into context.
Spend one sentence on Situation and Task, most of the answer on Action, and finish with a Result that has a number, a decision or a visible change. If the answer is mostly background, the interviewer learns what happened around you, not what you did.
A worked STAR example
Question: "Tell me about a time you missed a deadline." A weak answer apologizes and explains how busy the team was. A STAR answer sounds like this:
"Situation: I was leading the migration of our billing reports, and the finance team needed the new format before quarter close. Task: I owned the delivery date and had two engineers helping part-time. Action: three days before the deadline I realized the reconciliation check was failing on about a fifth of accounts, so I told my manager and the finance lead the same day, cut the release to the largest accounts first, and booked two hours each morning with the engineer who knew the legacy query. Result: the priority accounts shipped on time, the rest went out six days later with a written explanation, and I added the reconciliation check to our pre-release checklist so the same surprise could not repeat."
No excuse about workload, no blame, and no claim that everything went perfectly. The answer shows judgement under pressure, which is what the question is really about.
Where STAR answers go wrong
- The story has no result, or the result belongs to the team and you cannot say what you contributed.
- The action section is a list of meetings. Describe decisions and work, not attendance.
- The example is too old or too small to support the level of the role you are applying for.
- You reuse one story for every question. Prepare three or four, each covering a different theme: conflict, failure, leadership, pressure.
- You invent details to make the result sound bigger. Interviewers ask follow-ups, and a fabricated detail is hard to sustain for three questions.
What do the most common interview questions and answers test?
Each question type is a different test. Knowing which one you are being given tells you how long the answer should be and what evidence belongs in it.
| Question type | What the interviewer tests | What a strong answer includes |
|---|---|---|
| About you | Whether you can summarise your own experience clearly and see the logic of your career | A short narrative, one proof point, and a reason this role is the next step |
| Behavioral | How you actually behaved in a real situation, and whether you can reflect on it | A STAR story with your specific actions and a result you can defend |
| Role and company | Whether you understand the job and have done enough research to choose it deliberately | Their problem, your matching evidence, and a sensible first-90-days view |
| Tricky | Composure and honesty when the topic is uncomfortable | A factual answer, no blame, and a short statement of what you learned |
| Questions you ask them | Whether you are evaluating the job seriously and will be engaged if hired | Two or three specific questions about the work, the team or the process |
Questions about you (6)
These are warm-ups with a purpose: the interviewer is checking whether you can describe your own work without rambling. Keep each answer under two minutes.
- Tell me about yourself — give your current role, one relevant proof point, and why this job is the logical next step.
- Walk me through your resume — move chronologically in two or three sentences per role, and end at the reason you applied.
- What are your strengths? — name two strengths that the posting asks for, each with a short work example.
- What is your biggest weakness? — choose a real, contained weakness and describe the system you built to manage it.
- Why do you want to leave your current job? — give a forward-looking reason about the work, not a complaint about people.
- Where do you see yourself in five years? — describe a direction that fits this role, without claiming to know your exact job title.
Behavioral questions (8)
Behavioral questions assume past behavior predicts future behavior. Use STAR, keep the situation short, and choose examples from the last few years that match the seniority of the role.
- Tell me about a time you handled conflict with a colleague — show that you raised the issue directly, with evidence, and preserved the working relationship.
- Tell me about a time you missed a deadline — own it early, explain the repair, and name the change you made afterwards.
- Tell me about a time you failed — pick a real failure with a real cost, then show what you understood and did differently.
- Tell me about a time you disagreed with your manager — explain how you made your case, and what you did once the decision was made.
- Tell me about a time you worked under pressure — describe how you prioritised and what you deliberately let slip.
- Tell me about a time you led a project or a team — state the scope, the decisions you made, and the outcome.
- Tell me about a time you had to learn something quickly — name the method you used and the deadline that proved it worked.
- Tell me about a time you received difficult feedback — say what the feedback was, what you changed, and what happened next.
Role and company questions (6)
These test preparation. Connect something specific about the company to something specific in your history.
- Why do you want this job? — connect a problem the team has to a piece of work you have already done.
- Why should we hire you? — take three requirements from the posting and give one proof point for each.
- What do you know about our company? — mention the product, the customer and one recent change, then ask a question about it.
- How would you approach the first 90 days? — describe listening first, then one priority, then how you would measure progress.
- What are your salary expectations? — give a researched range, say it is negotiable, and ask about the band for the role.
- Do you have any questions for us? — never say no; keep two or three specific questions ready from the next section.
Tricky questions (5)
Tricky questions are not traps. They check that you can stay calm and factual about something awkward, so short and honest beats long and defensive.
- Why is there a gap in your resume? — give the factual reason in one sentence, say what you did during it, and stop talking.
- Why were you let go? — state what the company said, avoid blame, and add what you learned or changed.
- Are you interviewing elsewhere? — answer honestly about the stage you are at, and do not use it as pressure unless you mean it.
- What would your last manager say about you? — give a balanced answer with one strength and one area you are still working on.
- Why haven't you been promoted yet? — explain the structure or timing, then describe the scope you have taken on anyway.
Questions to ask the interviewer (5)
The questions you ask are part of the interview. Ask about the work, the team and the process, and avoid questions whose answers are on the company website.
- What does success look like in this role after six months? — reveals the real expectations behind the posting.
- What is the biggest challenge the team is facing right now? — shows you are thinking about the job, not just the offer.
- How does the team make decisions when people disagree? — tells you whether the culture matches how you work.
- What happened to the last person in this role? — a fair question about a role you may take.
- What are the next steps in the process, and when should I expect to hear? — closes the interview cleanly and removes ambiguity.
How do you practise mock interviews from the real job description?
A mock interview is only useful if the questions come from the posting you are applying to. A mock built from the job description tests whether you can defend your resume against its requirements.
- Take the posting and underline every requirement the role is really hired for — usually four to six lines, not the whole page.
- For each requirement, write the question an interviewer would ask to verify it. A requirement about stakeholder management becomes "Tell me about a time you had to align people who did not report to you."
- Record yourself answering out loud, one question at a time, without notes. Reading an answer silently hides the pauses and the rambling.
- Check each answer for the three failures: no result, no personal action, or a claim you cannot support with a detail.
- Redo the weak answers, then rehearse the two questions you will ask them.
LiveHint's AI mock interview builds a voice interview from the real job description and your own resume, then gives you a scored debrief and a full transcript. The transcript is the useful part: you can see where an answer lost its result or drifted into background. It is practice, not a script to read in the real interview, and it cannot tell you what a specific company will ask.
If your resume is the weaker half of the application, fix that first with this guide to tailoring your resume without lying. Interview answers can only defend claims that are already on the page.
Paste a job description and your resume, then practise the questions that role will actually ask. You get a scored debrief and a full transcript after each run.
Try a mock interviewAfter the interview, write down the questions you were asked and how each answer went. That record is more valuable than another list of tips, and it fits naturally into an application tracker where you already keep notes on each role.
You do not need perfect answers for all thirty. You need a clear summary of your experience, four honest stories, a reason for wanting this job, and two questions worth asking.
Frequently asked questions
- How many interview questions should I prepare for?
- Prepare four or five stories plus a short summary of your experience, not thirty separate scripts. Most interviews draw from the same handful of themes: conflict, failure, leadership, pressure and motivation. One well-rehearsed story can answer several behavioral questions, and a clear two-minute summary covers most of the questions about you.
- Is the STAR method still recommended in 2026?
- Yes. STAR is a structure, not a trend, and interviewers still use it because it produces answers with a clear ending. The common failure is spending too long on the situation and rushing the action and result. Keep the setup to one or two sentences and spend most of the answer on what you personally did and what changed.
- What is the best answer to tell me about yourself?
- Give your current role, one relevant achievement with a concrete result, and the reason this job is the next step. Keep it to about ninety seconds. The mistake is retelling your whole resume chronologically, which uses up the interviewer's attention before they have asked a real question.
- How do I answer questions about a weakness or a gap?
- Be brief and factual. For a weakness, name a real one, describe the system you use to manage it, and give an example of the improvement. For a gap, state the reason in one sentence, say what you did during that time, and stop. Long explanations sound defensive and invite more questions than the facts require.
- Can an AI mock interview really help me prepare?
- It helps with the parts that are hard to judge alone: whether your answer has a result, whether you ramble, and whether you can defend the claims on your resume. A mock built from the real job description is more useful than a generic list because it tests the requirements you will actually be assessed on. Treat the score as feedback, not a prediction.
- What should I ask the interviewer at the end?
- Ask two or three questions about the work itself: what success looks like after six months, the team's biggest current challenge, how decisions get made, and what the next steps are. These show genuine interest and give you information you need to decide whether to accept an offer. Avoid questions whose answers are easy to find on the company website.