Mock Interview Copilot Interview questions by type
Behavioral interview questions and the STAR method
Behavioural (or behavioral) questions ask about something you actually did: "Tell me about a time you…". The idea is that how you handled a real situation predicts how you will handle the next one. The standard way to answer is STAR: the Situation, your Task, the Actions you took, and the Result, with most of the time spent on the actions.
Write yours step by step with the free STAR answer builder: a box for each part, word counts, a speaking-time check and these questions to pick from.
How the interview usually runs
Almost every interview includes behavioural questions, and some employers run whole interviews of them, scored against a list of competencies such as teamwork, problem solving or leadership. The interviewer often has a scoring sheet: they are listening for a specific, real example, for what you personally did, and for an outcome. A hypothetical answer ("I would…") usually scores lower than a real one, even a modest one.
The good news is that the questions repeat. If you prepare six to eight solid stories from your work, studies or volunteering, each one can answer several questions: a project that went wrong can cover failure, pressure, and learning from a mistake.
Common questions and what the interviewer is checking
Tell me about a time you worked with a difficult colleague.
What they are checking: That you can disagree without drama, see the other person's point of view, and still get the work done. Avoid stories where the moral is that the other person was the problem.
Describe a time you failed or made a mistake.
What they are checking: Honesty and learning. They want a real mistake, your share of the blame, what you did to fix it, and what you now do differently.
Tell me about a time you had to meet a tight deadline.
What they are checking: How you prioritise, what you dropped or negotiated, and whether you told people early when something was at risk.
Give an example of when you showed leadership.
What they are checking: Influence, not job title. Leading a project, a change or a group of peers with no formal authority counts.
Tell me about a time you had to persuade someone.
What they are checking: Whether you understand what the other person cares about and use evidence, rather than repeating your view more loudly.
Describe a time you went above and beyond for a customer or colleague.
What they are checking: Judgement as well as effort: that the extra work mattered, and that you did not break rules to do it.
Tell me about a time you had to learn something quickly.
What they are checking: How you learn: what you read, who you asked, how you tested your understanding, and how fast you became useful.
Give an example of a decision you made without all the information.
What they are checking: That you can act under uncertainty, explain what you assumed, and check the decision afterwards.
Tell me about a time you received critical feedback.
What they are checking: Whether you can hear it without getting defensive, and show a concrete change you made because of it.
How to answer with STAR
STAR stops the two most common problems: rambling through background, and finishing without saying what happened. Aim for about two minutes. Keep Situation and Task short, spend over half the answer on Action, and always land on a Result, even if the result was a lesson.
- Situation: where you were and what was going on, in one or two sentences.
- Task: what you were responsible for, or what had to change.
- Action: the specific steps you took, in order, and why. Say "I", not "we".
- Result: what happened, ideally with something you can measure, plus what you learned.
Example answer
Tell me about a time you had to meet a tight deadline.
Situation: in my last job, a client moved a product launch forward by two weeks, and the onboarding guide I owned was only half written.
Task: I had to deliver a guide the support team could use on launch day, without dropping my other work.
Action: I listed every section and asked the support lead which ones customers would need in the first week. That cut the list nearly in half. I wrote those first, booked two short review slots with an engineer instead of waiting for one long one, and told my manager on day one which smaller task would slip and when I would pick it back up.
Result: the essential guide went out a day before launch, the rest followed the week after, and the support lead said the first-week questions matched what we had covered. I now ask "what do people need first?" at the start of every project, not when a deadline moves.
Mistakes to avoid
- Answering a "tell me about a time" question with what you would do in theory.
- Spending a minute on the background and running out of time before the action.
- Saying "we" all the way through, so the interviewer cannot tell what you did.
- Stopping at the action, with no result and no lesson.
- Choosing a "failure" that is really a boast, such as working too hard.
- Reusing the same story for every question instead of preparing several.
Frequently asked questions
What does STAR stand for in an interview?
Situation, Task, Action, Result. It is a way of structuring an answer to a behavioural question so that you give the context briefly, explain what you personally did, and finish with the outcome.
How long should a STAR answer be?
Around two minutes when spoken is a good target. Keep the situation and task to a few sentences each, spend most of the time on your actions, and finish with a clear result.
What if I don't have work experience for a behavioural question?
Use examples from study, part-time jobs, volunteering, sport or family responsibilities. Interviewers are scoring the behaviour, such as handling conflict or a deadline, not the setting it happened in.
Can I use the same example for more than one question?
Yes, a strong story can answer several questions by highlighting a different part of it. Try not to repeat the same story within one interview, though, so prepare several.