In this article
Introduction
Behavioural interview questions expose a simple problem. Faced with a request to describe past behaviour, many candidates either waffle through generic stories or offer highly rehearsed answers that collapse under probing. Interviewers need evidence you can perform the role, not a platitude about being a team player.
The STAR interview technique gives you a reliable structure to present concise, relevant and verifiable examples. Used well, it keeps your answers focused on what you personally did, why you chose that approach, and what followed. That approach matters to hiring managers because it turns subjective claims into assessable evidence.
What recruiters actually look for
Interviewers use past examples to predict future performance. We listen for three things.
- Clear demonstration of the skill or competency named in the question. A suitable example should map directly to the requirement on the job description.
- Personal ownership. We want to know what you did, not what the team or the organisation achieved. Use precise verbs and quantify your input where possible.
- Outcome and reflection. A result, especially one supported by figures, shows impact. Honest reflection shows professional judgement and ability to improve.
Recruiters are trained to probe beyond the headline claim. If you say you led a turnaround, expect questions about timescales, budget, stakeholder management and obstacles. Answers that lack specific actions or measurable outcomes fail to convince.
Why candidates struggle with behavioural questions
These questions are harder than they seem because they test both recall and judgement under pressure. Common reasons for poor answers are practical rather than psychological.
- Example selection mismatch. Candidates pick an interesting story that does not actually answer the competency asked for. This wastes time and weakens credibility.
- Too much background, too little action. Candidates spend the whole answer setting the scene and end with a vague statement about contributing. Interviewers leave unclear what the candidate actually did.
- Over rehearsed responses. A word perfect answer will sound polished, but it can fail follow up questions. If you cannot explain details, an interviewer will assume you did not own the work.
- Missing outcome or vague metrics. Without a result, the example reads like activity rather than impact.
Build strong answers with the STAR interview technique
The STAR interview technique is simple. It stands for Situation, Task, Action, Result. Use it as a frame, not a script. Keep each element tight, then be ready to expand when asked.
- Situation: Give only the context needed to understand the challenge. One or two sentences is enough.
- Task: State your responsibility and the objective. Make clear what success looked like.
- Action: This is the core. Explain the specific steps you took, why you took them, and how you handled obstacles. Use first person verbs, and mention tools or methods if they are relevant.
- Result: Describe the outcome, with figures where possible. If numbers are not available, give concrete qualitative results and what you learned.
Practical preparation reduces pressure in the interview. Before you walk in, analyse the job description for likely competencies. Prepare a bank of six to eight concise STAR examples that map to business analysis, stakeholder management, problem solving and leadership, depending on the role.
When practising, time each answer to roughly two minutes. Longer answers often hide weak action or absent outcomes. Then practise follow up questions. If an interviewer asks for evidence, be able to supply dates, people involved and specific techniques you used.
Real world examples and how to adapt them
Transforming a broad claim into a STAR answer is straightforward with a small adjustment to focus and ownership. Below are three templates you can adapt.
Customer service exampleBad claim, common: "I always handle complaints well and customers leave happy."
STAR response, concise:
- Situation: A key client threatened to leave after repeated delivery delays during a product launch.
- Task: I was asked to prevent churn and restore confidence within two weeks.
- Action: I set up daily updates with the client, mapped the delivery chain to identify the bottleneck, and negotiated revised interim delivery dates with the operations team. I also introduced a single point of contact to streamline communication.
- Result: Client retention was secured, we reduced complaints by 60 percent over the following quarter, and the account increased spend by 8 percent six months later.
Bad claim, common: "We improved project delivery times."
STAR response, concise:
- Situation: A cross functional project lacked clarity on decision rights, delaying delivery.
- Task: As the project manager I needed to re-establish governance and deliver the next milestone within four weeks.
- Action: I redefined decision authorities, created a fortnightly decision log, and ran a workshop to align stakeholders on priorities. I personally managed the log and chased pending approvals.
- Result: The milestone was delivered on time, approval cycles shortened from an average of ten days to three, and the team adopted the decision log for future projects.
Honesty sells when paired with learning. A poor result can be valuable if you explain corrective action.
- Situation: I led an initiative to replace our CRM, but the initial rollout failed to meet adoption targets.
- Task: I had to diagnose the failure and restore user confidence within six weeks.
- Action: I ran targeted user interviews, identified training gaps, and introduced role specific guides. I also established a feedback loop to capture ongoing issues and prioritised fixes with the vendor.
- Result: Adoption rose from 42 percent to 87 percent within two months, and the process improvements reduced support tickets by half. The key lesson I communicated was to secure user champions before rollout.
Recruiter insights from real hiring situations
These are practical observations from screening hundreds of candidates across UK and Middle East markets.
- When candidates use "we" repeatedly, I probe who did what. If responsibility is unclear, the candidate loses credibility. Employers hire individuals, not teams.
- Numbers matter. A vague "improved performance" will not pass a competent interviewer. Even conservative, verifiable figures are more persuasive than grand, unsupported claims.
Both points influence hiring decisions immediately. A candidate who presents a clear, personal action and backs it with an outcome moves to the top of the shortlist.
See how your CV performs with recruiters
Upload your CV for a free review and get a score out of 100 based on ATS and recruiter expectations.
Actionable checklist: prepare your STAR answers
Use this checklist in the week before an interview. Prepare, practise and verify.
- Highlight the competencies named in the job description, and map each to one or two STAR examples.
- Select examples with a clear personal contribution, not just team achievements.
- Write brief notes for Situation, Task, Action and Result, no more than four lines each.
- Check that each answer directly addresses the likely question you will be asked.
- Verify any figures or claims and be ready to explain how you calculated them.
- Practise aloud, time your answers, and trim unnecessary background detail.
- Prepare short follow up evidence points, such as tools used, stakeholders involved and obstacles overcome.
- Have one honest setback story ready, focussing on learning and corrective action.
Summary: make every example relevant and credible
Strong behavioural answers show what you did and what happened as a result. The STAR interview technique gives you a compact, interviewer friendly way to present evidence. Recruiters will test details, so choose examples you can defend and quantify.
Prepare adaptable examples rather than memorised scripts. That approach keeps your answers natural and credible, and it makes follow up questions straightforward to handle.
Check the CV behind your interview examples
Interview stories must match what your CV claims. Recruiters and hiring managers compare examples you give to the achievements on your CV. Discrepancies raise questions about authenticity and attention to detail.
Use a CV to present the evidence that your STAR answers will reference. List responsibilities and outcomes in the same language you use in interviews, and include concise figures where appropriate. That alignment makes your case stronger and shortens the screening process.
Call to action
If you would like a recruiter to review how your CV presents the achievements you plan to discuss, request a Free CV Review. Automated tools identify formatting and ATS issues, but an experienced recruiter spots positioning, phrasing and credibility problems that software misses. Send your CV for a practical, recruiter style assessment and clear recommendations you can apply before your next interview.
Common Mistakes
Using the same example for every question. This suggests a thin experience base and frustrates interviewers. Fix this by preparing multiple examples mapped to different competencies.
Describing team achievements without clarifying your role. Interviewers cannot assess your skill if your actions are buried in team narratives. Fix by explicitly stating your tasks and decisions.
Claiming results you cannot explain. If asked for detail and you cannot supply it, trust collapses. Fix by verifying figures beforehand and choosing examples you can defend.
Treating STAR as a rigid script. Stiff, memorised answers break rapport. Fix by using STAR as a scaffold, then speak conversationally and adapt to the question.
See how your CV is likely to be assessed in a competitive market.
Upload your CV and receive a structured recruiter review with a clear first read on positioning and fit.
See how your CV is likely to be assessed in a competitive market.
Upload your CV and receive a structured recruiter review with a clear first read on positioning and fit.

