Sample interview answers
Are you a team player? Sample answers and teamwork examples
Yes. I like working towards a shared goal, and I'll take whatever role the team needs, including the less visible work. In my last job, when a colleague was off for two weeks, I took over half her accounts and kept a handover note for her return, so nothing was dropped.
To adapt it, say yes, then prove it straight away with one thing you did for a team, not just with your team.
Short answers, then STAR teamwork stories
Short answer: retail or hospitality
Definitely. In a shop, the customer doesn't care whose job something is, so I help wherever it's needed. If the tills are busy, I'll leave the shelves and open another till; if a colleague's stuck with a difficult return, I'll find the manager for them. I also try to leave my section tidy for the next shift, because nobody should start a shift catching up on someone else's mess.
Why it works: Small, concrete examples show teamwork as everyday behaviour.
Short answer: someone who also works well alone
Yes, though I'll be honest that I do my best detailed work with some quiet time. As a data analyst, I spend a lot of time on my own building reports, but the work only matters if it answers the team's questions. So I agree the question with colleagues before I start, share early drafts, and ask for corrections. When the sales team said my dashboard was hard to read, I sat with two of them for an hour and rebuilt it around how they actually used it.
Why it works: It is honest about a preference without sounding like a loner.
Short answer: healthcare assistant
Yes, because on a ward you can't do anything safely alone. I help colleagues with repositioning and personal care, answer call bells in other bays when they're busy, and keep the nurses updated on anything I notice, like a patient eating less. When I finish my own tasks, I ask the nurse in charge where I'm needed rather than waiting to be told. Good handovers matter too, so I always pass on what the next shift needs to know.
Why it works: It links teamwork directly to patient safety, which is what a ward panel is checking.
Short answer: software developer
Yes. Software is a team sport, even when you're writing code on your own. I review colleagues' pull requests within a day so nobody's blocked, I write notes on anything unusual in my code, and I'll pair with a newer developer when they're stuck. I also try to be easy to disagree with: if someone suggests a better approach in review, I'd rather change my code than defend it.
Why it works: It names specific team habits that a lead developer will recognise.
STAR: call center agent covering a sick colleague (India BPO)
On one night shift, three of our twelve agents called in sick, and a billing issue meant calls were queueing for over ten minutes. My team leader asked us to keep calls short, but I saw newer agents transferring billing calls they could have solved. I offered to sit on a chat channel for the team while still taking my own calls, answering quick questions about the billing problem. I also wrote the three most common fixes in a pinned message. Transfers dropped noticeably by midnight, the queue cleared before the morning shift, and our team leader made the pinned message part of the standard notes.
Why it works: It shows teamwork beyond your own job description, with a result for the whole team.
STAR: university group project with an absent member (UK)
In my second year, we had a group report worth a third of a module, and one member stopped replying three weeks before the deadline. Rather than complaining or doing his part silently, I messaged him privately to ask if everything was all right. He'd fallen behind because of a family problem. We agreed he'd take a smaller, data-collection section he could do from home, and the rest of us split the writing. I set up a shared plan with weekly checkpoints and a group chat. We submitted on time, got a high mark, and he thanked us afterwards for not reporting him.
Why it works: It shows empathy and practical problem-solving rather than blaming a teammate.
STAR: line cook during a Saturday rush (US restaurant)
One Saturday, our grill cook burned his hand early in the dinner rush and had to leave. I was on the fry station, but I'd trained on grill. I told the kitchen manager I could cover both if a server ran food from fries to the pass, and he agreed. I called out every ticket so the team knew what was coming, and I asked the dishwasher to drop baskets for me when it got heavy. We got through two hundred covers with only one comped meal. Afterwards, the manager started cross-training everyone on at least a second station, so one injury couldn't stop the line.
Why it works: It shows calm communication and stepping up when the team is under pressure.
STAR: marketing and sales working across teams
Our marketing team was generating leads, but sales said they were poor quality, and both teams were blaming each other. As the marketing executive running our webinars, I asked to sit in on a sales team meeting to understand what a good lead looked like to them. They wanted people with a budget and a project date, which our sign-up form never asked. I added two questions to the form and sent sales a weekly list grouped by project date. Within two months, sales were following up the webinar leads first, and the two teams started meeting monthly to review lead quality together.
Why it works: Working across teams is a stronger teamwork story than helping your own.
What makes these answers work
“Are you a team player?” invites a yes, so the yes alone earns nothing. The interviewer wants proof that you share information, help without being asked, handle disagreement calmly, and put the team's goal above looking good yourself. “Tell me about a time you worked in a team” asks for the same thing as a story, so prepare one STAR example as well as a short answer.
The short answers name specific habits; the STAR stories each end with a result for the whole team.
A fill-in template
Use the short version when asked “Are you a team player?” and the STAR version for “Tell me about a time…”.
- Short: Yes. For example, I [a specific habit: share notes, cover tasks, review work quickly].
- Short: When [a colleague or team needed something], I [what you did].
- STAR situation: Our team was [goal] when [problem].
- STAR action: I [two or three actions, saying “I”, including how you worked with others].
- STAR result: As a result, [team outcome], and [what changed afterwards].
Mistakes to avoid
- Just saying “yes, definitely” and stopping there.
- A teamwork story where you saved the day and everyone else looks useless.
- Saying “we” throughout so the interviewer can't tell what you did.
- Picking a story where the team result was bad and you were the only one who did well.
Frequently asked questions
How do I answer “Tell me about a time you worked in a team”?
Use STAR: the team's goal, the problem, what you personally did, and the result for the team. Choose an example where you helped others succeed, not just yourself.
What if I prefer working alone?
Say so honestly, but show you can work well with others: you share progress, ask for feedback and help when needed. Most jobs need both.
Can I use a university or school example?
Yes, especially as a fresher. Group projects, sports teams, societies and part-time jobs all work if you describe your own role clearly.