How to answer interview questions: any type, with examples
Answer in three parts: a direct answer, one piece of proof, and a link back to the job. This guide shows how that works for behavioral, weakness, conflict and technical questions, what to say with no experience, and what to do when your mind goes blank.
How to answer interview questions: the three-part answer
Most weak interview answers ramble without answering, or answer in one vague sentence ("I'm a good communicator") with nothing behind it. A simple shape fixes both.
- Answer. One sentence that responds to what was asked. "Yes, I've led a team through a tight deadline."
- Proof. One concrete example: what happened, what you did, what changed. Tools, rough sizes and real outcomes make it believable.
- Tie-back. One sentence that connects the example to the role. "That is the kind of ownership I'd bring to this team."
Say the answer first because the interviewer is deciding in the first few seconds whether you heard the question. Put the proof in the middle because that is what they will remember, and end on the job.
How long should an answer be?
For a behavioral answer, Indeed's guide to the STAR interview technique suggests roughly 1.5 to 2 minutes, noting that shorter answers keep you precise and the interviewer engaged (Indeed). For a factual question, one sentence is enough. If you have talked for two minutes without reaching the result, finish your sentence and go straight to the outcome.
Behavioral questions: use the STAR format
Questions that start "Tell me about a time when..." are behavioral questions. The interviewer wants evidence from your past, so a story works better than a claim. Answer them using the STAR method:
- Situation: the context, in a sentence or two.
- Task: what you were responsible for.
- Action: what you did, step by step. This is the longest part.
- Result: what happened, with a number if you have one, and what you learned.
Indeed's guide advises keeping the situation to two or three key details and using "I" rather than "we" so your own contribution is clear. The two common mistakes are spending most of the time on the situation and saying "we" for everything. For complete answers across ten jobs, see STAR method interview examples.
"Tell me about yourself"
This is the one question you can be sure of, so script it. A reliable shape is present, past, future, in about a minute:
- Present: what you do now, with one achievement.
- Past: the one or two steps that brought you here and matter for this job.
- Future: why this role is the sensible next step.
Do not recite your CV or resume line by line. For a wider list to practice with, see common interview questions, and prepare your own questions to ask the interviewer.
For full sample answers, including freshers, experienced hires and no experience, see how to answer tell me about yourself.
Interview weakness answer: what to say
"What is your biggest weakness?" is not a trap. The interviewer wants self-awareness and to see whether you act on your flaws. Three rules cover it:
- Choose a real weakness that is not central to the job. A salesperson who is "slow to update the CRM" has a fixable habit.
- Say briefly what it cost you, so it sounds honest.
- Spend most of the answer on what you are doing about it, and the evidence it works.
Avoid the disguised brag ("I work too hard") and the empty non-answer ("I can't think of one").
Example (illustrative): "I tend to hold on to tasks instead of delegating them. On a launch last year I stayed late finishing work a teammate could have done, and the team ended up waiting on me. Since then I start every project by listing what only I can do and handing off the rest, and my last two launches shipped without overtime."
Interview conflict question: how to handle it
"Tell me about a disagreement with a coworker" tests how you treat people when you are annoyed. Good answers describe a real but not catastrophic conflict, treat the other person fairly even if they were wrong, and show something specific you did to resolve it. Do not pick a story where you were simply right. A better pattern is: we wanted different things, I asked questions to understand why, we found a way that met the real goal.
Example (illustrative): "A designer and I disagreed about shipping a feature with a known rough edge. I wanted to hold the release. They wanted to keep the date for a customer demo. I asked what the demo needed, and only one flow had to be polished. We shipped that flow on time and fixed the rest the following week."
How to answer interview questions with no experience
To answer interview questions with no experience, use what you have done instead of what you have been paid for. Say plainly that you are new, then give one real example from study, volunteering, a part-time job or a personal project, and show that you learn fast and turn up reliably. Interviewers hiring for a first job expect this and listen for attitude as much as history.
Early-career candidates and career changers often hear "tell me about a time you led a team" and think they have nothing. Usually they do: university projects and societies, volunteering and sports teams, part-time jobs such as retail and hospitality, or personal projects like a site you built or an event you organized.
Be honest about the setting ("In a university group project..."), then use the three-part answer or STAR as normal. If nothing matches, say so, then answer the nearest thing: "I haven't managed people yet. The closest is when I coordinated five volunteers for a charity event." In the UK these are often called competency based questions, and the advice is the same.
"I don't have experience but I'm willing to learn"
Saying "I don't have experience but I'm willing to learn" is honest, but thin on its own. Pair it with proof that you do learn: name one thing you taught yourself, how long it took and what you can do now. Then say what you will do in the first weeks.
Example (illustrative): "I haven't done this job before, so I'll be straight about that. What I can show you is how I learn. Last year I taught myself [a skill] in [a period of time] and used it to [result]. In my first month here I would ask for feedback early and often until I'm useful on my own."
Why should we hire you with no experience?
Give three honest reasons: you are reliable, you learn quickly, and you want this particular job. Support each with one short fact. Do not apologize for your background and do not oversell. Our guide to why should we hire you has more versions.
Example (illustrative): "I don't have paid experience in this field yet, but I have what a new person needs. I'm reliable: I [ran a weekly volunteer shift for a year without missing one]. I learn fast: [a short example]. And I chose this role because [one specific reason]."
First job interview questions: interview answers with no experience
These first job interview questions come up most often. Write a four-line answer to each and say it aloud.
- Tell me about yourself.
- Why do you want this job, and why this company?
- What are your strengths? What is your weakness?
- Tell me about a time you worked in a team.
- How would you handle a difficult customer or a busy shift?
- When can you work, and where do you see yourself in a few years?
For tips on the day itself, see job interview tips.
What are the best 3 strengths to say with no experience?
Pick three strengths a new starter can prove: reliability, willingness to learn and working well with others. Give each one a half-sentence of evidence, such as "never missed a shift in a year" or "taught myself spreadsheets in two weeks". Then link to the job. What is your greatest weakness also covers the matching strengths answer.
What counts as a red flag when you have no experience?
Having no experience is not a red flag. The red flags are claiming skills you do not have, blaming a lack of chances, giving no example at all and asking no questions. End by asking one or two, such as "What does a good first month look like?" More are in questions to ask the interviewer.
Situational and "what would you do" questions
For hypotheticals such as "What would you do if a client asked for something outside the scope?", lay out your reasoning in order: say what you would clarify first, name the options and trade-offs, then say what you would do and how you would tell the other person. If you have faced something similar, add a one-line real example ("I did this at my last job when...").
Technical questions
Technical questions need a different habit: think out loud. Restate the problem, ask a clarifying question, describe your approach before you start, and explain trade-offs. Interviewers listen for how you reason, and silence hides that. See technical interview tips.
If you do not know something, say what you do know, how you would find out, and your best guess. "I haven't used that library. I've used a similar one, and I'd check how it handles X first" beats bluffing.
What to do when your mind goes blank in an interview
It happens to experienced people too. Two things help: a way to buy a few seconds, and a way to start without the whole answer.
Pause lines that sound natural
- "That's a good question. Let me think about the best example for a second."
- "Let me make sure I answer the right thing. Are you asking about...?"
- "A couple of situations come to mind. Let me pick the most relevant."
Each gives you three to five seconds and makes you look thoughtful rather than lost. Practice one until it sounds like your own voice.
Start with the direct answer
You only need the first sentence. "Yes, I have, on the payments migration" is enough to get going, and the details tend to follow once you are talking.
Keep a story bank
Blanking is mostly a retrieval problem. If you have six to eight stories written down, each with a one-line headline, you only need to remember the headline. Write each as a few lines: situation, what you did, the result, and the skills it shows. Review the list the night before.
Practicing out loud
Reading answers silently is not practice. The skill is speaking in sentences under mild pressure. A routine that works:
- Pick ten questions: yourself, strengths, weakness, conflict, failure, leadership, a deadline, why this company, why this role, your last job.
- Answer each out loud, with a timer. Aim for under two minutes. Record on your phone if you can stand to listen back.
- Check three things. Did you answer in the first sentence? Is there a specific example? Did you say what you personally did?
- Repeat on two more days. The second and third attempts are where answers become fluent without sounding memorized.
Memorize the shape and the key facts, not the words. A memorized answer collapses when the question is phrased slightly differently.
Common mistakes at a glance
| Mistake | What it sounds like | Fix |
|---|---|---|
| Burying the answer | Two minutes of background before the point | Say the answer in the first sentence |
| Saying "we" throughout | "We rebuilt the checkout..." | Say what you personally did, then credit the team |
| No result | The story just stops | End with an outcome and what you learned |
| Vague claims | "I'm a strong leader" | Replace with one specific example |
| Bluffing | Guessing at a technical question | Say what you know, how you'd find out, your best guess |
A one-page checklist for the night before
- Six to eight stories written down, each with a one-line headline.
- A 60-second "tell me about yourself" you can say without notes.
- A real weakness with a real fix.
- Two pause lines you are comfortable saying.
- Three questions to ask them.
If you want live help on a call, Hintly is a desktop app for Mac and Windows that shows a suggested answer in a small overlay, built only from your own notes. It is pre-launch, so the way in is the waitlist. Check the employer's rules first, and read our guide to using AI in interviews or see how Hintly works for interviews.
The system is deliberately small, and it is how to answer interview questions confidently. Answer first, prove it with one example, tie it to the job, and stop.
Questions
How long should an answer to an interview question be?
Aim for about one to two minutes for most questions. Indeed's guide to the STAR method suggests roughly 1.5 to 2 minutes for a behavioral answer. A factual question ("Are you available to start in March?") needs one sentence. If the interviewer wants more, they will ask.
What if I don't understand the question?
Say so, and check your reading: "Just to make sure I answer the right thing, are you asking about a time I disagreed with a manager, or with a teammate?" Interviewers treat this as a good sign. Guessing and answering a different question is worse.
Is it okay to pause before answering?
Yes. A pause of a few seconds feels long to you and normal to the other person. Take a breath, repeat the question back in your own words if that helps, and start with your direct answer.
How many stories should I prepare?
Six to eight real stories from your CV or resume cover most behavioral questions, because one story can answer several questions. Cover teamwork, conflict, a mistake, a deadline, leading others, and something you are proud of.
Can I use notes in a video interview?
That depends on the employer and the format, so check any rules you were given. Plenty of people keep prep notes beside the screen, and some people use an AI interview assistant that works only from their own notes. Our guide to using AI in interviews covers the etiquette.