Answering behavioural IT interview questions with the STAR method
Behavioural questions ask for a real example of something you did, and STAR (Situation, Task, Action, Result) is the simplest way to answer them. Keep the situation short, spend most of the answer on what you did, and finish with what happened and what you learned.
The section on Success Profiles describes UK Civil Service recruitment.
"Tell me about a time when..." questions want a real example of something you did, told so the interviewer can follow it and score it. The STAR method is the simplest way to do that: Situation, Task, Action, Result. Prepare a small bank of true stories before the interview, keep the situation brief, spend most of each answer on what you personally did, and always finish with the outcome and what you learned. In IT interviews they often sit alongside technical questions, so prepare for both.
What the four parts are for
The National Careers Service defines the parts like this. Situation is the situation you had to deal with. Task is what you were given to do. Action is the action you took. Result is what happened because of your action and what you learned from it.
The parts don't deserve equal time. The situation and task are there so the interviewer understands the problem; a sentence or two each is usually enough. The action is what they are scoring, so it should be the longest part and the most specific: what you checked, what you said, what you decided and why. The result closes the story. Say what changed, give a number if you genuinely have one, and say what you would do the same or differently now. It is easy to stop after the action, and a story with no ending is hard to score.
The same page gives four habits worth keeping: use examples that work for you, which can come from work, home or volunteering; keep them short and to the point; get your points across conversationally so you don't sound rehearsed; and be ready for follow-up questions about the examples you give.
Building a bank of stories
Start with the job description. The National Careers Service's interview tips put reading it carefully first in its preparation list, followed by researching the company, looking over your CV for what the interviewer might ask, and preparing examples from your past experience. For an IT role, the skills an advert lists usually map onto the same handful of themes: dealing with people, fixing problems, learning, working under pressure, working with others and making things better.
Write one story for each theme, then check what you have. A good bank has at least one story where something went wrong and it was your fault, one where you changed someone's mind or they changed yours, and one where you learned something quickly. Most stories can answer more than one question, so you don't need dozens.
If you haven't worked in IT yet, use what you have. A retail job gives you difficult customers and busy Saturdays; a call centre gives you calm explanations to upset people and targets; hospitality gives you pressure and teamwork; volunteering or a society gives you organising and persuading. An interviewer for a service desk role cares far more that you stayed calm and fixed the customer's problem than whether the problem was a laptop. Home labs count too: a weekend spent getting a domain controller working is a fine "learned something quickly" story.
Keep each story as five or six lines of notes, not a script. Notes let you tell it in your own words; a memorised paragraph sounds memorised and falls apart at the first follow-up.
Six IT questions, worked through
The outlines below show the shape of a good answer. They are illustrations, not stories to borrow: use your own.
"Tell me about a time you dealt with a difficult user."
What it checks: whether you stay calm, listen, explain without jargon and still solve the actual problem. An outline: a manager's laptop failed an hour before a presentation and they were angry on the phone (situation); you had to get them presenting on time (task); you acknowledged the deadline, gave a realistic time, set them up on a loan laptop with their files from cloud storage, then fixed the original laptop afterwards (action); they presented on time, and you logged the fault so the hardware issue was tracked (result). The learning might be that giving someone a time estimate early takes the heat out of the call.
"Tell me about a mistake you made."
What it checks: honesty, ownership and whether you stop it happening again. Don't offer a disguised strength. Pick a real error with a contained impact, such as a change applied to the wrong group of users. The action should cover how you noticed, how quickly you told your lead, how you put it right, and the habit you changed, for example checking the target before running anything that changes more than one account. The more access a job gives you, the more this answer matters.
"Tell me about a time you had to learn something fast."
What it checks: how you learn, not just that you did. Name the method: the vendor's documentation, a test environment, a colleague who already knew it, and the order you used them in. The result should show you applied it, such as completing the work by the deadline or writing up what you learned so the next person didn't start from nothing.
"Describe a time you worked under pressure, such as during an outage."
What it checks: whether you stay methodical, communicate and know your role. A junior's honest part in a major outage is often the communication, and that is a good answer. An outline: email was down for a whole office (situation); you were answering calls on the service desk (task); you set a recorded message so callers knew it was known about, linked new tickets to the main incident, passed the engineers the pattern you were seeing in the calls, and gave users updates at the times you promised (action); the service came back, the engineers weren't interrupted by duplicate reports, and you helped write the timeline afterwards (result).
"Tell me about a time you disagreed with a colleague."
What it checks: whether you can disagree with respect, use evidence and accept a decision. A good story has you raising the issue privately, explaining your reasons with something concrete (tickets, logs, a user's complaint), listening to theirs, and agreeing on a way forward. It is fine if they turned out to be right: say what you took from it. Avoid stories that end with the other person being shown up.
"Tell me about a time you improved a process."
What it checks: whether you notice repeated work and do something about it. Service desks are full of these: the same password question every Monday, a setup checklist that lived in one person's head. The action is what you did to fix it and how you got others to use it, such as writing a knowledge base article (KBY's lesson on publishing a knowledge base article safely covers how). For the result, give the measure you actually saw, and if you never measured it, say what you noticed instead. Never invent a percentage.
Getting the length right
Short and to the point, as the National Careers Service puts it. A useful test when you practise out loud: if you have been talking for a while and haven't reached the action, the situation is too long. Cut the technical background a non-technical interviewer won't follow, and let them ask for more detail. Expect follow-up questions; the National Careers Service says to be ready for them, and a short answer leaves room for them.
Mistakes that cost marks
Watch for these when you practise; each is easy to fix:
- Saying "we" throughout. The panel can't credit you for what the team did. Use "we" for the context and "I" for your part.
- Stopping at the action, with no result and nothing learned.
- Answering a "tell me about a time" question with what you would do. If you have no real example, say so and offer the closest one you have.
- Spending most of the answer on the situation or on technical detail.
- Choosing a story where the problem was someone else's fault and you were the one who noticed.
- Reciting a script. It sounds rehearsed, and the first follow-up exposes it.
Civil Service and public sector interviews
The UK Civil Service recruits using Success Profiles, which have five elements: behaviours, strengths, ability, experience and technical. Not every element is used for every role, and the job advert tells you which ones will be assessed and how.
Behaviours are where STAR does most of its work. The Civil Service lists nine: seeing the big picture, changing and improving, making effective decisions, leadership, communicating and influencing, working together, developing self and others, managing a quality service and delivering at pace (Civil Service behaviours). Recruiting managers choose a selection for each role, so you won't be asked about all of them, and the examples of each behaviour are written for each grade. Read the examples for the grade you are applying for and match your stories to them. At Executive Officer level, for instance, managing a quality service includes identifying common problems that affect service, reporting them and finding possible solutions, which is an IT service desk's daily work. The same page suggests the STAR method for your examples, and says examples can come from work experience, volunteering or a hobby as well as a job.
The candidate overview adds two things worth knowing. Interviews usually last 30 to 60 minutes. And for written examples on an application form, don't assume the recruiting manager will know or understand the situation you were facing: make it clear how your example shows the behaviour being assessed. Naming the behaviour in your first sentence is a simple way to do that.
Strengths questions are different, and STAR is the wrong tool for them. The strengths guidance says there are no right or wrong answers, that the panel wants your initial response, and that you shouldn't rehearse. Prepare by thinking about what you enjoy and do well, not by writing stories. The Civil Service may also ask how you would behave in a given situation rather than what you did, so be ready to reason through a hypothetical too.
If you apply to another public body, read its job pack the same way: find what it will assess, then match a true story to each item.
Practising before the day
Say each story out loud at least twice, once to yourself and once to someone who will interrupt with questions. Then mix behavioural practice with technical practice, because real panels switch between the two. The systems administrator questions include the "change that went wrong" question sysadmin panels ask, the cloud engineer questions end with a design exercise, and KBY's Daily Triage exercises give you practice at the fault-finding half of the interview.
Common questions
- Can I use an example from a job outside IT?
- Yes. The National Careers Service says examples can come from work, home or volunteering, and the Civil Service accepts examples from work experience, volunteering or a hobby. Dealing with an angry customer in a shop shows the same skill as dealing with an angry user.
- Should I use STAR for strengths questions in a Civil Service interview?
- No. The Civil Service's strengths guidance says there are no right or wrong answers, that the panel is looking for your initial response, and that you should not rehearse. Use STAR for behaviour questions and answer strengths questions naturally.
- What if I can't remember the exact figures for my result?
- Describe the outcome you are sure of in plain words, such as fewer repeat calls or a deadline met. Only give a number you could defend if the interviewer asked where it came from.
Sources
Every figure and rule in this guide comes from these pages, read on 17 November 2026. Pay rates, exams and schemes change: check the source before you rely on one.
- The STAR method (National Careers Service)
- Interview tips (National Careers Service)
- Success Profiles (GOV.UK (Cabinet Office))
- Success Profiles: Civil Service behaviours (GOV.UK (Cabinet Office))
- Success Profiles: Candidate overview (GOV.UK (Cabinet Office))
- Success Profiles: Strengths (GOV.UK (Cabinet Office))
Spotted something wrong or out of date? Tell us and we will correct it.