How to explain your contribution in a team effort

Say what you were responsible for early

Once you’ve introduced the project, add a sentence about your role:

“Our team was improving the cancellation flow. I was responsible for understanding why customers were contacting support instead of cancelling themselves.”

Now the interviewer knows where you fit. Your next few sentences can explain how you approached that responsibility.

Be specific enough to give the story a starting point. “I was the PM” names your job, but it doesn’t explain what you handled on this project.

You might have owned the research, recommended the release scope, or coordinated a rollout. Start there.

Replace “worked with” with what happened

“I worked with design and engineering” could describe almost any PM project. Think about what you actually did together.

Did you bring customer examples to a design review? Question an assumption in the proposed flow? Help choose a smaller version when the estimate came back too high?

Those details make your contribution easier to understand.

For example:

“I worked with the designer on the new flow.”

Becomes:

“I brought examples from customer calls to the design review. People couldn’t tell when their cancellation would take effect, so I recommended showing the date before they confirmed.”

If the designer suggested that solution, say that instead. Your contribution might have been identifying the problem and helping check whether the proposed design solved it.

Use “we” and “I” where each belongs

Here’s an illustrative answer:

“Our team redesigned the cancellation flow. My part was understanding why customers needed help to cancel.

“I reviewed recent conversations with support and spoke with customers who’d tried the flow. Several weren’t sure whether cancellation would end their access immediately or at the next billing date. I brought that finding to the designer and recommended making the timing clear before confirmation.

“The designer explored how to show it, and engineering built the change. I then helped run customer sessions to check the revised flow. In those sessions, people could explain when their access would end without asking for help.”

“We” describes the shared project. “I” introduces the PM’s research, recommendation, and follow-up. The designer and engineers have clear roles too.

You don’t need to account for every person’s work. Include enough detail for someone to understand how your contribution fitted into the team effort.

If you supported the work, explain the choices you made

You may have worked under another PM or joined a project after the main decisions were made. You can still discuss the part you handled.

Suppose you prepared a customer feedback summary. What did you notice? How did you group the feedback? Did you flag a problem the team hadn’t considered?

“I prepared the summary” becomes more useful when you add:

“I noticed that several requests came from customers trying to complete the same task. I grouped those examples together and raised the underlying problem with the PM.”

If you know what happened next, include it. Perhaps the team investigated further or changed the scope. If your involvement ended at the recommendation, make that clear.

Check whether your part is easy to follow

Take one draft answer and highlight the sentences beginning with “we.”

For each, ask: “Does the interviewer know what I did here?” Add a detail where your contribution is missing.

Then read the sentences beginning with “I.” Check that they describe your work accurately and acknowledge collaboration where it matters. There’s no ideal ratio of “I” to “we”; the goal is a clear account of what happened.

Finally, say the answer aloud and ask someone: “What do you think my contribution was?” Their answer will tell you more than counting pronouns.

If you’re unsure how to explain the team’s result, use this guide to outcomes without impressive metrics. You can then bring both the shared result and your own contribution into your Remi answer.