Use “we” for the shared goal and outcome, then “I” for the actions and decisions you personally owned. Name a collaborator's role where it explains a handoff. You do not need to claim the whole result to give a clear account of your contribution.
Yale's STAR guidance explicitly asks candidates to focus on their individual role when describing team work.[50] RRC Polytech similarly advises explaining how you contributed when working in a group.[74] The attribution worksheet below is an original editorial tool for doing that without erasing your teammates.
Start by separating three different things
A project has a team objective, a division of work and an outcome. Those are not interchangeable.
“The team launched the service” describes an outcome. It does not say whether you designed the workflow, tested a component, handled customer communication or attended planning meetings. Conversely, “I checked the launch checklist” may accurately describe your action without establishing that you alone made the launch successful.
Write three private notes before drafting an answer:
- What the team was trying to achieve.
- What you were responsible for doing or deciding.
- What happened, including what you cannot attribute to yourself.
If you cannot fill the middle line, investigate the event or choose another one. Adding “I led” to a team result is not a substitute for remembering your work. If you were a supporting contributor, explain the support precisely. You are not required to invent leadership to make a story usable.
Copy the contribution-and-handoff worksheet
The first row is a blank template. The other rows form one fictional community workshop example, not a real candidate case study.
| Part of the work | My responsibility | Collaborator or decision owner | What I actually did | Supported result and limit |
|---|---|---|---|---|
| [Workstream] | [Your assigned or agreed scope] | [Who owned the adjacent work] | [Observable action] | [Evidence; what remains shared or unknown] |
| Registration — fictional | Check attendee questions and flag access needs | Coordinator approved changes; venue handled access arrangements | Grouped incoming questions and sent an unresolved-items list | Coordinator received a clear list; no satisfaction measurement |
| Workshop materials — fictional | Review the participant instructions | Subject specialist owned technical accuracy | Tested the instructions as a new reader and marked confusing steps | Specialist revised the document; did not author its technical content |
| Final delivery — fictional | Staff the registration desk | Whole organising group delivered the workshop | Used the agreed list and escalated unanswered questions | Workshop went ahead; did not personally own every part of delivery |
This is an attribution map, not a points system. A contribution can matter even if it is not the most senior role in the table. Keep the evidence bounded: a reviewed document supports “I reviewed the document,” not automatically “my review prevented all problems.”
For each row, ask who could legitimately object to your wording. If a teammate would say, “That decision was mine,” revise the verb or explain the handoff. Do not contact former colleagues or move restricted project records merely to complete this exercise.
Rewrite a vague answer without expanding the claim
Fictional starting version:
“We ran a workshop, solved the registration problems and made sure everything worked.”
The problem is not the word “we” itself. The listener cannot tell which problem the candidate handled, what action they took or what “everything worked” means.
Fictional clearer version:
“Our group organised a community workshop. I handled incoming registration questions and prepared the unresolved-items list for the coordinator. When several messages asked about access arrangements, I grouped them so the coordinator could get one confirmed answer from the venue. The coordinator approved the response, and I sent it to the affected attendees. I did not arrange the venue access myself. The workshop went ahead; we did not collect a satisfaction score.”
The rewrite adds responsibility, a decision boundary and an observable sequence. It does not add a success percentage or promote a coordinator's approval into the candidate's authority. This is an illustrative answer, not testimony from a real applicant.
To make the answer shorter, remove incidental setup rather than the ownership boundary. For instance, keep “the coordinator approved the response” if it matters to understanding who made the decision.
Use verbs that match your authority
“Led,” “owned,” “supported,” “reviewed,” “recommended” and “implemented” describe different relationships to work. Do not treat them as stronger and weaker synonyms.
Before saying “I led,” identify what you directed and what decisions you could make. Before saying “I implemented,” explain the work you performed. “I recommended a change that the project owner accepted” is a complete contribution; it does not need to become “I set the strategy.”
You can also distinguish initiating from approving. “I proposed an additional check; the team lead approved it; I added it to the checklist” gives each person their part. If approval was not required, do not insert a fictional hierarchy just because the sentence frame uses one.
For outcomes, keep attribution proportional to evidence. “The team delivered on the agreed date” is a team result. “I delivered my assigned review before the handoff” is your result. Without stronger evidence, avoid “my review caused the project to finish on time.”
Prepare for ownership follow-ups
An interviewer may ask for more detail; you do not need to assume that means they distrust you. Use the question to supply the missing boundary.
| Practice question | What to prepare | What not to invent |
|---|---|---|
| “What did you personally decide?” | One decision within your actual remit | Authority held by your manager |
| “Who did the technical work?” | The specialist's role and your interface with it | Expertise you did not exercise |
| “What would have happened without you?” | Your specific responsibility and any known dependency | An unobserved alternate outcome |
| “How do you know it helped?” | The evidence you actually have | A causal claim from a shared result alone |
| “What would you change?” | A reflection grounded in what happened | A mistake or lesson added only for drama |
If you do not know the counterfactual, say so: “I cannot measure what would have happened without me. I can explain the part I handled and why the team assigned it.” That answer leaves a limit visible rather than manufacturing indispensability.
For additional practice, the follow-up branch exercise separates action, evidence, reasoning and reflection questions. The STAR expansion worksheet helps turn one workstream into a complete account.
What if your contribution was small?
Describe it accurately and choose the question carefully. A small task with a clear decision may fit a question about attention to detail better than a large project where you had little responsibility. It may not fit a question about leading a programme. Both things can be true.
Do not blame teammates to make your own role seem larger. Explain dependencies neutrally: “I needed the approved figures before I could update the report.” If the interviewer asks about a disagreement, describe the issue and your response without speculating about another person's motives.
If the real example is too confidential to discuss, choose another event or prepare an appropriately cleared version. The confidential-work worksheet addresses that separate decision; simply changing “we” to “I” does not make details safe to share.
Common questions
Should I avoid saying “we” entirely?
No. Shared work deserves shared attribution. Use “we” where you mean the team, then identify your part. Replacing every “we” with “I” can make the account less truthful.
Can I mention a result I did not measure?
You can state a result you genuinely observed, with its limits. Do not attach a measurement or claim you caused it unless you can support that statement.
Is supporting work worth discussing?
Yes, when it answers the question. Explain the task, the judgement involved and the handoff. If the question specifically requires leadership experience you do not have, acknowledge that distinction.
Keep tool-generated wording inside the same boundaries
InterviewRep describes suggestions you request yourself and use as a starting point for your own words; it cautions that suggestions can be inaccurate.[16] Reject any wording that silently increases your authority, changes a collaborator's action into yours or invents a measured outcome.
The live assistance guide covers the separate workflow. Where assistance and audio capture are permitted, try 10 free minutes; the public offer currently says no credit card is required.[16]
Method: university and college guidance supports explaining individual contributions. The worksheet, fictional workshop account and verb checks are original editorial recommendations, not a validated interview scoring instrument.
Sources
- InterviewRep | Live interview help, in your own words
- The Behavioral Interview – Office of Career Strategy – Yale University
- Interview Preparation : RRC Polytech: Career Services
10 minutes for new accounts. No credit card required. Use only where assistance and capture are permitted. Check current plans and terms.