In this article
Before you start
This page is one question in the hiring manager interview questions guide, part of the wider interview preparation library.
Related questions in the same round include whether you see yourself as a lead developer or a manager, which probes the same ownership.
Why interviewers ask this
A project result belongs to a team, so it tells a hiring manager little about you. The question exists to separate your part from the group's part. A hiring manager is deciding what you would own on their team, and a sentence that begins "we built" gives no evidence either way. Candidates report meeting this question in hiring-manager rounds, usually right after they mention a project on their résumé or in an earlier answer.
Expect follow-ups, because detail is easy to test. Amazon's published Leadership Principles describe leaders who "operate at all levels, stay connected to the details, audit frequently, and are skeptical when metrics and anecdote differ" (Amazon, Leadership Principles, undated, accessed 2026-10-26). That does not say how any one interviewer probes, but it shows why vague or inflated claims invite more questions.
A weak answer describes the whole project and never says what the speaker did. A strong answer names specific actions and one result. A Staff-level answer also separates what you did, what you led and what teammates did.
Exact contributions from first principles
- Exact contribution
- An exact contribution is a specific piece of work on a project that you personally did, decided or led, described as an action with an outcome, so the listener can tell your part from the team's part.
- Action story
- An action story is a short spoken account of one project that states the situation and your role briefly, then the steps you took in the first person, then the result, in that order.
In plain words
Picture a group photo of a finished building. Everyone in the photo helped. The interviewer wants to know which walls you built. The photo is the project and the walls are your contributions. The analogy breaks in one place: in a real project some work is shared, and the honest answer says so instead of claiming the whole wall.
The tool most career offices teach for this is the situation, task, action, result (STAR) method. The STAR method is a structured way to answer a behavioral interview question by covering the situation, task, action and result of one example (University of Iowa Tippie College, undated, accessed 2026-10-26). It is written in full as situation, task, action, result (STAR). For this question, the action is the part that matters most.
Step 1: Frame the task and your role in a few sentences
Start with the situation and your role, and stop early. Northwestern's career office describes the task step as "Describe the task and your role in it" and gives it about 10% of the answer (Northwestern Career Advancement, undated, accessed 2026-10-26). Its action step gets about 50% and its result step about 25%. The rest of the answer is the situation, in a sentence or two.
Input: one project from your history. Output: two or three sentences that say what was wrong and what you were responsible for.
An illustrative frame: "Our nightly sales-report pipeline took six hours and kept missing the morning deadline. I was the engineer responsible for cutting its run time, on a team of four." Notice what is missing: the history of the company, the tools list and the other projects. You now have the frame, and the next step is the longest part.
Step 2: Say I for each action and name the team separately
Say "I" when you describe your own actions and keep the team's work in separate sentences. The Iowa career office puts it plainly: "Use the word "I," not "we" when describing actions." The University of New Mexico's Los Alamos career service adds that you should "keep the focus on you, even if you are discussing a group project", describing what you did, not what the team did (University of New Mexico, Los Alamos Career Services, undated, accessed 2026-10-26).
A weak version: "We rewrote the job and we got the time down." A strong version: "I profiled the job and found that one join took most of the time, so I rewrote it. A teammate moved the data to a faster file format." The strong version credits the teammate and still makes your part clear.
The action should be the longest part of the answer. In a 90-second answer at an illustrative 120 words a minute, about 180 words, the action gets 90 words, the result 45 and the task 18.1
Text description of the diagram
- In a 90-second answer the action gets 90 words, the task 18 and the result 45.
- The action is the longest part of the answer.
Step 3: Draw the line between what you did, led and handed off
Sort the project's work into three piles: work you did yourself, work you led or decided but others carried out, and work teammates did. This split is original advice, not from a source, and it makes the answer exact because each pile gets its own verb. "I wrote" and "I decided" are claims about you. "A teammate built" is credit.
Take an illustrative project with twelve work items. You did five, you led three by choosing the design and reviewing the result, and teammates did four. That is 41.7%, 25.0% and 33.3%.1
| Pile | Work items | Share of work |
|---|---|---|
| Did myself | 5 | 41.7% |
| Led or decided | 3 | 25.0% |
| Teammates did | 4 | 33.3% |
You do not recite these numbers in the interview. You use them to check that your sentences match the work. A claim of "I did everything" would not fit a project with a team of four. Amazon's Ownership principle begins "Leaders are owners" and says they "never say "that's not my job"", which supports showing work you took on beyond your own task, as the "led" pile does.
Step 4: Close with a result you can measure
End the action story on the outcome, with a number if the work had one. The Northwestern guide gives the result about 25% of the answer and says it can be the outcome "or what you learned." Its own example reads "By surveying regional offices, I found that only 72 percent had database tracking systems that were upgraded", which shows how a figure anchors a claim. The Iowa page sets a goal of "at least a 15% increase in advertisers from the year before" before it reports the result.
In the illustrative pipeline project, the run time fell from six hours to two. That is a cut of 66.7%.1 If you have no hard number, give the best honest measure: a deadline now met, an error that stopped recurring, a process another team reused.
The answer opens with the task and your role in a few sentences. The action takes about half of the answer and uses I. The result closes the answer with a number.
Step-by-step description
- State the task and your role briefly.
- Say I for each action you took.
- Separate did, led and teammates' work.
- End on a measured result.
- The answer opens with the task and your role in a few sentences.
- The action takes about half of the answer and uses I.
- The result closes the answer with a number.
Knowing it is half the job. Saying it is the other half.
Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.
Start Free Trial →The Staff-level answer
What were your exact contributions to the projects mentioned?
Let me take the nightly sales pipeline. It took six hours and kept missing the morning deadline, and I owned cutting its run time on a team of four. I profiled it, found that one join took most of the time, and rewrote it. I also chose the new storage format after testing two options, and I reviewed the two changes my teammates made. A teammate built the alerting; I only specified it. Run time fell from six hours to two, and next quarter I reused the same profiling steps on a second pipeline. I can walk through the join if that helps.
The example is illustrative. What makes it Staff-level: it separates doing, deciding and reviewing, it credits a teammate by name of role, and it offers detail before being asked.
The rubric
This rubric is advice on what a strong answer shows, not any company's scoring sheet.
| Dimension | Weak answer | Strong answer | Staff answer |
|---|---|---|---|
| Ownership | Says "we" throughout | Says "I" for each action | Separates did, led and teammates' work |
| Specifics | Describes the project in general terms | Names the steps and tools used | Names the decision and the options rejected |
| Result | No outcome stated | One measured result | Result plus what was reused or learned |
| Honesty | Claims the whole project | Credits the team once | Credits teammates by role and scopes own part |
| Delivery | Long setup, short action | Action is the longest part | Offers depth on request, stays within the time |
Three variants of this question
Which part of the project were you responsible for?
Name the one deliverable you owned, then the actions you took on it. "I was responsible for the run time of the pipeline; I profiled it and rewrote the slow join." Do not list every task on the project.
What would not have happened without you?
Pick a decision or piece of work that moved the result and say why. If nothing fits honestly, say what you sped up or unblocked instead. Avoid claiming the project would have failed without you.
What did you do versus what did the team do?
Use the three piles of step 3: what you did, what you led and what teammates did. Give each a sentence and one example. This is the same question wearing its own labels, so the answer is already prepared.
Common mistakes
- "We built the whole thing." (wrong) The interviewer cannot tell what you did. (right) "I built the ingestion step; a teammate built the dashboard."
- "I did everything." (wrong) It is unlikely on a team project and invites probing. This is an inference, not a source claim. (right) "I did these five tasks and led these three."
- A long account of the company and the project before any action. (wrong) The action should carry the weight. (right) "One sentence of situation, one of role, then the actions."
- "I just helped a bit." (wrong) It undersells real work. The Iowa guide says "don't be shy about taking credit." (right) "I wrote the tests that caught the regression."
- No result at all. (wrong) The answer ends on a task. (right) "Run time went from six hours to two."
Follow-up questions
How do you describe a project you joined late?
Say when you joined and what state the project was in, then claim only what you did from that point. This is editorial advice, not from a source. A clear boundary reads as honest.
What if the result of the project was not good?
Give the result as it was and say what you learned, because the Northwestern guide lists "what you learned" as an acceptable result. Then say what you changed afterwards.
How do you talk about a project where ownership was shared or unclear?
Say that it was shared, name the part you took on and say how you agreed the split. Avoid claiming the shared parts alone.
How do you show scope without over-claiming?
Describe work you led or took on beyond your task as "led", not "did". This matches Amazon's Ownership principle, "Leaders are owners", without claiming other people's work.
How long should the answer be?
Aim for 60 to 90 seconds, which is 120 to 180 words at an illustrative 120 words a minute. Stop at the result and let the interviewer ask for detail. If the project was a design, expect to be asked to design something similar, such as a multi-task system across domains, and a follow-up may be what excites you at work. The rest of the round is covered in the hiring manager interview questions guide.
- Pick one project and say your role in a sentence or two.
- Say "I" for your actions and credit the team in separate sentences.
- Make the action the longest part, about half of the answer.
- Sort the work into did, led and handed off, so every claim fits.
- Close on a measured result or on what you learned.
Sources
- Amazon's Leadership Principles — Amazon (undated page, accessed 2026-10-26), 26 Oct 2026
- The STAR Approach — Northwestern University Career Advancement (undated page, accessed 2026-10-26), 26 Oct 2026
- STAR Method — Tippie College of Business Career Services, University of Iowa (undated page, accessed 2026-10-26), 26 Oct 2026
- Interviewing Guide: STAR Method — University of New Mexico, Los Alamos Career Services (undated page, accessed 2026-10-26), 26 Oct 2026
