Tell Me About a Time You Worked in a Team: Complete Graduate Interview Guide 2026
This question appears in virtually every graduate interview. Most candidates describe what their team did rather than what they personally contributed — here is how to get it right.
Why Employers Ask This Question
"Tell me about a time you worked in a team" is one of the most universal competency-based interview questions across every sector. Goldman Sachs, PwC, Deloitte, Amazon, Microsoft, and virtually every other major graduate employer include a version of it because almost every professional role requires working collaboratively — often across functions, time zones, and competing priorities.
Employers are not simply checking whether you have worked in a group before. Every candidate has done group projects, sports teams, or part-time work. What they are trying to determine is the quality of your contribution, how you handle the friction that is inherent in any team, and whether your natural working style will fit their culture.
Employers use past behaviour as the most reliable predictor of future performance. When they ask for a specific example of teamwork, they are not interested in your general views on collaboration — they want behavioural evidence. This is why "I enjoy working in teams and find it very rewarding" is a complete non-answer. They need a specific story with a specific outcome.
This question appears as a first-round telephone screen, a video interview stage, and a face-to-face competency interview. At some employers — particularly in financial services and consulting — it also forms the basis for group exercise assessment at the assessment centre, where your live teamwork behaviours are directly observed.
What Interviewers Are Really Evaluating
Different employers test different aspects of teamwork, and your answer should be calibrated accordingly. Understanding the underlying competency framework helps you select the right example and emphasise the right elements of your story.
| Competency Being Tested | What Interviewers Listen For | Relevant Employers |
|---|---|---|
| Collaboration & relationship-building | How you built rapport, managed different working styles, and aligned the group around shared goals | PwC, Deloitte, KPMG, EY |
| Conflict management | How you handled disagreement, different opinions, or underperforming team members without derailing the project | Goldman Sachs, JP Morgan, Barclays |
| Influence without authority | How you moved the team forward when you were not the formal leader — persuading, motivating, or re-directing | Amazon, Microsoft, McKinsey |
| Accountability & ownership | Whether you took responsibility for your part, stepped up when needed, and saw through commitments | Amazon (Leadership Principles), HSBC |
| Cultural fit & humility | Whether you can articulate what the team achieved (not just you personally), and whether you give credit appropriately | All employers, especially consulting |
Every major employer publishes the competencies they assess. PwC's framework includes "Relationship" and "Global Acumen". Amazon explicitly assesses "Earn Trust" and "Teamwork" through Leadership Principles. KPMG values "Collaboration". Read the employer's graduate careers page and tailor which aspect of your teamwork example you emphasise — the same story can be told very differently depending on what the employer is listening for.
You should also be prepared for follow-up probes. Interviewers at Goldman Sachs, McKinsey, and the Big Four are trained to drill into your example to verify it is genuine. Common follow-ups include: "What was the most difficult part of working with that person?", "How did you resolve the disagreement specifically?", and "If you could do it again, what would you do differently?"
How to Structure Your Answer (STAR)
The STAR method — Situation, Task, Action, Result — is the standard structure for competency-based interview answers and works particularly well for teamwork questions. The critical adjustment for teamwork questions is the balance of the four components: most candidates over-weight Situation and under-weight Action, leaving the interviewer with a story about what their team did rather than what the candidate personally contributed.
The STAR Framework for Teamwork Questions
The instinct to say "we" throughout a teamwork answer is understandable — it feels modest and collaborative. But it destroys your answer because the interviewer cannot determine what you personally did. Replace every "we" in your Action section with "I". For example: not "We decided to re-divide the tasks" but "I suggested we re-divide the tasks because [reason] — the team agreed and we implemented it by [date]." You can use "we" in the Result section when describing the team's collective achievement.
A strong teamwork answer typically runs for 2 to 3 minutes when spoken aloud. Practice with a timer — most candidates either run too short (under 90 seconds, missing the depth of Action) or too long (over 4 minutes, losing the interviewer in unnecessary detail).
For further guidance on using STAR across all competency questions, see our complete guide to behavioural interview questions and the STAR method.
Choosing the Right Example
The teamwork example you choose has a significant effect on the quality of your answer. Not all group experiences are equally useful as interview material. The strongest examples share specific characteristics.
Characteristics of a High-Quality Teamwork Example
- Genuine adversity: The most compelling stories involve a team that faced a real challenge — a conflict, a setback, a change in scope, a difficult team member, or a missed deadline. A project that "went smoothly" often produces a flat answer. Employers are specifically looking for how you behave when things get hard.
- A specific personal contribution: You need to be able to answer "what did YOU specifically do?" with at least three distinct actions. If your role was passive or undifferentiated, pick a different example.
- A measurable outcome: Examples with a clear, verifiable result are much stronger than vague ones. A dissertation project that received a First, a society event that raised £2,000, a business competition your team reached the final of — these produce specific, credible Results sections.
- Relevance to the role: Where possible, choose an example that mirrors the kinds of teamwork challenges you will face in the job. An investment banking candidate should ideally use an analytically demanding or commercially relevant example. A consulting candidate benefits from an example involving ambiguous problems and multiple stakeholders.
| Example Source | Strengths | Weaknesses to Watch |
|---|---|---|
| University group project | Familiar to the interviewer; usually includes genuine conflict and deadline pressure | Overused; ensure your role was clearly defined and impactful |
| Internship or work experience | Demonstrates professional context; shows commercial awareness | You may have had limited authority — emphasise influence, not just task completion |
| Sports team or society leadership | Often produces rich examples involving motivation, conflict, and leadership | Ensure the example translates to a professional context; avoid being too sports-heavy |
| Volunteering or charity project | Demonstrates initiative and values alignment; often involves diverse stakeholders | Ensure the outcome and your contribution are clearly articulated |
| Part-time or casual work | Very credible for service-sector employers; shows real-world pressure | Ensure the scale of the example feels appropriate for a graduate role |
Interviewers often ask a follow-up teamwork question exploring a different dimension — for example, one question about a successful team outcome and a second about a time the team struggled or a member was not pulling their weight. Having a second, contrasting example ready (a smaller-scale or more difficult situation) prevents you from repeating yourself and shows a richer range of teamwork experience.
5 Full Example Answers
The following answers are written in spoken interview style — the length and language are calibrated to what works in a real interview, not a written submission. Adapt the details to your own experience.
Example 1: University Group Project (Conflict & Recovery)
Situation: In my second year, I was part of a four-person team completing a corporate finance case study worth 40% of a core module. We had five weeks to build a DCF model and present our recommendation to a panel of academics.
Task: I was responsible for the financial modelling section and also took informal ownership of coordinating the group's timeline, as no one had volunteered to project-manage.
Action: By week two it became clear that one teammate was consistently missing our agreed deadlines and his section — the industry analysis — was blocking progress on my model. Rather than escalating to the module leader immediately, I asked to speak with him one-to-one. I found out he was simultaneously sitting two exam resits and had not felt able to say so in the group. I suggested we simplify his section to the three most material factors rather than the original eight, which he could complete in a weekend. I then drafted a revised project plan to absorb the delay without compromising the overall quality and shared it transparently with the full group. To recover the lost time in the modelling section, I brought forward my own work schedule by one week and ran a two-hour working session with the remaining members to build the sensitivity tables together.
Result: We submitted on time and received a distinction — 78%. The feedback specifically noted the quality of the financial model and the coherent structure of the presentation. Looking back, I learned that early one-to-one conversations are almost always more effective than group pressure when a team member is struggling — it surfaces the real issue faster and preserves the working relationship.
Example 2: Sports Team Leadership (Influence Without Authority)
Situation: I captained my university rowing team during my third year. We had eight members with very different ability levels — three club athletes and five who were primarily recreational — and we were preparing for an inter-university regatta where we had not previously competed.
Task: My role was to coordinate training and ensure the whole squad was performing at their best on race day, despite the significant gap in experience levels.
Action: The main challenge was that the experienced rowers wanted to train five days a week while the recreational members could only commit to two. I could see this was creating resentment on both sides. I proposed splitting training sessions: two joint sessions per week focused on race technique and boat cohesion, with the experienced athletes free to add extra sessions independently. To keep the less experienced members engaged rather than demoralised, I introduced session-level performance targets rather than absolute benchmarks — so everyone could see personal improvement week on week. I also held a brief team debrief after each joint session, which kept communication open and gave quieter members a structured moment to raise concerns.
Result: We finished third out of eleven crews at the regatta — our best-ever result — and the end-of-year survey from the sports union ranked our team's cohesion highest among all rowing squads. What I took from it was that in mixed-ability teams, the greatest lever you have is clarity of purpose combined with individually meaningful goals — it removes the comparison dynamic that tends to fracture groups.
Example 3: Internship Team (Tight Deadline, Stakeholder Pressure)
Situation: During a ten-week summer internship at a mid-sized asset management firm, I was placed on a four-person project team tasked with producing a market entry analysis for a potential new product line. Midway through, two of our four weeks were consumed by the senior manager being pulled onto an urgent client issue, leaving the remaining three of us to complete work originally scoped for four people.
Task: I was responsible for the competitor analysis and regulatory mapping sections. With the revised timeline, both needed to be completed in eight days rather than the planned fourteen.
Action: I immediately identified which elements of the regulatory mapping were already partially completed by the absent manager and which required a full rebuild. I re-scoped the deliverable with my remaining two colleagues — we agreed to use a tiered approach, completing a full analysis for the two highest-priority markets and a lighter summary for the remaining three, rather than thin coverage across all five. I communicated this scope change to our project sponsor before proceeding, framing it as a risk management decision rather than a capability gap. I also shared my competitor analysis template with one colleague so she could contribute to data collection while I built the regulatory framework, which recovered roughly two days.
Result: We delivered the analysis on schedule. The sponsor explicitly mentioned the scope prioritisation decision in her feedback as "commercially mature thinking" — she noted it was the kind of judgement call she expected from analysts, not interns. I received an offer to return for the following summer.
Example 4: Volunteering / Non-Profit (Diverse Team, Limited Resources)
Situation: In my final year I volunteered as a coordinator for a university food bank project. We had a team of twelve volunteers with varying availability and very different ideas about how the service should operate — some wanted to expand hours, others prioritised maintaining quality with current resources.
Task: I was responsible for coordinating weekly volunteer rotas and managing relationships with three local supermarket donation partners.
Action: The main friction point was between volunteers who wanted to expand to a Saturday session (which required six additional volunteers) and those who felt we were already overstretched. Rather than calling a vote — which I felt would create a clear winner and loser — I ran a structured discussion where I asked each volunteer to articulate what they were worried about specifically. This surfaced the real issue: the volunteers who opposed expansion were concerned about food safety protocols being compromised by less-trained new volunteers. I proposed a compromise: a pilot Saturday session with a capped intake, staffed only by trained existing volunteers, with a formal review after four weeks. I then drafted the training checklist that the food safety leads wanted so that new volunteers could be brought up to standard faster.
Result: The Saturday pilot ran successfully for the remainder of the academic year and expanded capacity by 35% without any of the food safety incidents the team had been concerned about. The project won the university's Volunteering Impact Award that year. What I learned was that in volunteer teams, resistance to change usually signals an unspoken concern — surfacing it specifically is more productive than trying to build consensus at the abstract level.
Example 5: Remote & Cross-Cultural Team (Communication Across Differences)
Situation: As part of an international case competition, I was placed in a five-person team with students from the UK, Germany, India, and South Korea. We had two weeks to develop and present a market entry strategy for a European fintech company entering Southeast Asian markets — working entirely remotely across four time zones.
Task: I took on the role of coordinating the team's schedule and building the final presentation deck, while also contributing to the financial modelling section.
Action: The immediate challenge was finding meeting times that worked across a 12-hour time difference. I proposed asynchronous working as the primary mode — each person would record a 5-minute video update by 8pm their local time, which the whole team could watch at their own convenience, with a single synchronous call per week for decisions only. This reduced friction significantly. Midway through, I noticed that the contributions from our South Korean team member were consistently arriving late and were much less detailed than the others. Rather than raising it in the group, I messaged her directly and found that she was uncertain about how much independent analysis she was expected to contribute versus waiting for group consensus — a genuine cultural difference in working style rather than disengagement. I sent her a brief written brief of what her section needed to include, which resolved the issue immediately.
Result: Our team reached the competition semi-finals, placing in the top 20% of 400 entries. The judges specifically praised the quality of the market analysis — which was the section our South Korean team member produced after we clarified expectations. I came away with a clear lesson: in cross-cultural teams, ambiguity about expectations is the most common source of underperformance, and addressing it individually and specifically is much more effective than general group pressure.
Employer-Specific Angles
While the core STAR structure applies everywhere, the specific aspects of your teamwork story you choose to emphasise should reflect each employer's published values and competency frameworks. Here is how to calibrate your answer for the major graduate employers.
Big Four (PwC, Deloitte, KPMG, EY)
All four firms assess teamwork through a collaboration or relationship competency. They value examples where you actively built trust across different levels or backgrounds, managed a client-facing team dynamic, or helped a team work through a disagreement constructively. For PwC, emphasise building relationships and cross-functional perspective. For Deloitte, the firm's culture values innovation within teams — if your example involved challenging the status quo or bringing a new approach, highlight that. For KPMG and EY, integrity and inclusive collaboration are prominent — examples where you ensured every team member's voice was heard resonate strongly.
Investment Banking (Goldman Sachs, JP Morgan, Barclays)
Investment banks look for high-performance team behaviours: delivering under pressure, maintaining quality when stakes are high, and managing conflict without allowing it to derail a deadline. For Goldman Sachs, examples from analytically demanding or commercially high-stakes contexts perform best. Emphasise your resilience and the precision of your contribution. JP Morgan values examples where you navigated diverse perspectives or escalated effectively when needed. The key differentiator for banking interviews is that your Result should include a hard commercial or performance metric wherever possible.
Amazon
Amazon interviews are structured around Leadership Principles. The most relevant principles for a teamwork question are Earn Trust, Have Backbone; Disagree and Commit, and Ownership. Amazon interviewers are specifically listening for evidence of each principle, so your Action section should explicitly demonstrate one of them. For example: if your example involves a team disagreement, show that you raised your view clearly (Backbone), heard the counterargument, and then fully committed to the team's final decision (Disagree and Commit). See our full guide to the Amazon online assessment for more on how Leadership Principles shape the hiring process.
| Employer | Teamwork Competency Focus | Key Phrase to Include |
|---|---|---|
| PwC | Relationship building, global acumen | "I made sure to understand each person's perspective before…" |
| Deloitte | Collaboration, innovation within teams | "I challenged the team to consider a different approach by…" |
| KPMG | Inclusive collaboration, integrity | "I ensured that everyone had a clear role and was heard…" |
| Goldman Sachs | Performance under pressure, precision | "With two days until the deadline, I prioritised by…" |
| Amazon | Earn Trust, Ownership, Disagree & Commit | "I raised my concern directly in the team meeting, and once we decided…" |
| Microsoft | Growth mindset, inclusive culture | "I asked for feedback from the team mid-project to improve…" |
Common Variations of the Question
The core teamwork question appears in many forms. Each variation has a slightly different emphasis that should shape which part of your example you lead with.
| Question Variant | Emphasis | What to Adjust in Your Answer |
|---|---|---|
| "Tell me about a time you worked in a team" | General collaboration and contribution | Standard STAR answer — balance all four components |
| "Tell me about a time you had a conflict within a team" | Conflict management and resolution | Lead your Action section with the specific conflict and how you addressed it; ensure the resolution is constructive, not just "it was fine in the end" |
| "Describe a time you had to lead a team without formal authority" | Influence and leadership | Emphasise how you persuaded, motivated, or aligned the team without relying on a title; specific influencing tactics are key |
| "Tell me about a time a team member was not performing" | Difficult conversations, accountability | Show that you addressed the issue directly and specifically with the individual, not just around them; focus on the approach and the outcome for the person, not just the project |
| "What is your role in a team?" | Self-awareness and team dynamics | This is asking about your natural team role — answer with a genuine self-assessment, then illustrate it with a specific example; avoid claiming to be "both a leader and a team player" without substantiating it |
| "Describe a time you worked in a cross-functional or diverse team" | Adaptability, communication across differences | Emphasise how you adapted your communication style or approach based on different expertise levels or backgrounds; show genuine curiosity and respect for different perspectives |
A single rich teamwork story can typically be adapted to answer three or four of the variants above, simply by adjusting what you emphasise in the Action section. The conflict variant leads with the disagreement. The leadership variant leads with how you moved the team forward. Prepare one strong story and practice rotating the lens on it — this is more efficient and produces more credible answers than memorising entirely separate stories for each variant.
5 Mistakes That Sink Most Candidates
These are the most common errors interviewers observe in responses to this question across graduate applications to the Big Four, financial services, and technology companies.
Mistake 1: Describing the Team's Work, Not Your Own
The most widespread failure. Candidates spend the entire Action section describing what the team did collectively, leaving the interviewer unable to assess the candidate's individual contribution. Every sentence in your Action section should begin with "I" and describe a specific action you took. Reserve "we" for the Result section, where describing the team's collective achievement is appropriate.
Mistake 2: Choosing an Example With No Real Challenge
An answer describing a team that "worked really well together from the start" and "achieved the goal without any problems" is not a compelling competency answer — it shows you either lack genuine adversity to draw on or that you are avoiding vulnerability. The most persuasive examples include a genuine obstacle: a conflict, a setback, a difficult team member, or a resource constraint. Interviewers at major employers are specifically trained to probe for the difficulty in your story.
Mistake 3: Being Vague About Your Role
Phrases like "I helped with the presentation" or "I contributed to the analysis" are too vague to evaluate. Be specific: "I built the three-scenario sensitivity model in Excel and presented slides four through seven, covering the financial projections." Specificity signals that the example is genuine and allows the interviewer to form a clear picture of your actual contribution.
Mistake 4: Failing to Mention the Outcome
A surprisingly large number of candidates finish describing their Actions and then stop, leaving the interviewer to ask "and how did it go?" The Result section is not optional. Even if the outcome was mixed — the team missed the deadline but the final quality was strong, or the project was cancelled for reasons outside the team's control — state it clearly and add a brief reflection on what you learned.
Mistake 5: Making the Team Sound Incompetent to Make Yourself Look Better
Some candidates, in their effort to emphasise their personal contribution, implicitly portray their teammates as disorganised, lazy, or unqualified — with the implicit message that the project only succeeded because of them. This is a significant cultural red flag at most employers, who explicitly value humility and collaborative credit-sharing. It is possible to show that you made a critical personal contribution without making your teammates look bad. Describe the challenge as a systemic or situational problem, not as a personality failure of your colleagues.
Most candidates mentally rehearse their answers but rarely practice speaking them. The "we" problem, the vagueness problem, and the missing Result problem almost always disappear once you practice aloud, because you hear them in your own voice. Record yourself once on your phone, listen back, and adjust. Two rounds of spoken practice will improve your answer more than ten rounds of mental rehearsal.
Frequently Asked Questions
Prepare for the Full Interview Process
Graduate interviews combine competency questions with aptitude tests. Practice your SHL numerical, verbal, and reasoning tests alongside your interview preparation to give yourself the best chance at every stage.