Why a group project question lands here
Most graduates have one or two group projects on their CV, and an interviewer who digs into one will eventually ask who did what. Sometimes the honest answer is that you did the least. Perhaps you joined the group late, took the part that felt safest, or had exams in another module that took priority. Perhaps one teammate was so far ahead that the rest of you followed.
None of that is disqualifying. A graduate interviewer is not expecting you to have led a team of peers. They are checking three things: whether you can describe your own work accurately, whether you can talk about a weak spot without becoming defensive, and whether you learn from it. A group project where you contributed little is a good test of all three, which is why it gets asked.
Saying what your part was
Start with the part that was genuinely yours, stated at its real size. "I wrote the data-loading module and the test cases for it, and I put together the final report from everyone's sections" is a clear piece of work. It is small, but it is checkable, and the interviewer can ask about it.
Then give the reason in one sentence, framed as your choice or circumstance. "I took the smallest technical piece because I was less confident in the framework than the others, and I did not push to take on more" is honest and owned. It tells the interviewer you understand what happened.
Finally, give the change. This is where most of the time should go, because it is the part being scored hardest. The best lessons show up in later behaviour: a second project where you volunteered for the hardest module, a habit of agreeing who owns what in the first meeting, or a framework you went back and learned properly.
| Weak version | Stronger version |
|---|
| "We all contributed equally." | "Honestly, I did the least of the four of us. My part was the data loader and the report." |
| "The others did not let me do much." | "Two teammates moved fast in week one and I let them take the core logic rather than asking for a share." |
| "I learned teamwork is important." | "In my final-year project I asked for the piece I knew least about, and I agreed ownership in writing on day one." |
The blame reflex, and why it costs more than the small contribution
The answer that loses marks is rarely the one admitting a small contribution. It is the one that explains the contribution away by pointing at someone else. "One person took over everything", "the group did not communicate", "I was given the boring part": each may be true, and each shifts the story from your behaviour to other people's.
An interviewer hears that as a preview of how you will talk about colleagues when a work project goes badly. Even a fair complaint about a dominant teammate reads as blame unless you pair it with what you could have done about it. "Someone took over, and I did not say anything because it was easier" owns the same facts and scores far better.
The opposite failure is inflation. A candidate who claims an equal share is fine until the follow-up asks how the core algorithm worked, and they cannot explain it. One question like that undermines everything else they said about the group project. The page on separating your work from the team's covers that habit in more depth; the version here is harder, because your honest share is small.
Credit the people who carried it
Name the teammates who did the heavy lifting, by role if not by name. "Priya designed the architecture and wrote most of the backend; I learned more from reading her code than from my own part" is generous, specific and believable. It costs you nothing and signals that you can work alongside stronger people without resenting them, which graduate employers value because most new hires start out as the least experienced person on the team.
Sample phrasing
"Honestly, I contributed the least of our group of four. I built the data-loading module and its tests, and I assembled the final report. I took the smallest piece because I was unsure of the framework, and when two teammates moved quickly I let them take the core logic instead of asking for a share.
What I changed: in my next project I asked for the part I knew least about, and our group agreed who owned what in the first meeting. That project is the one I would rather talk you through, if useful."
That answer takes about forty-five seconds. It is honest about the contribution, owns the reason, credits the others implicitly, and ends by offering stronger evidence. If you have a better project, steering towards it at the end is fine, as long as you have answered the question first.
An admitted small contribution with a real lesson attached is a good answer. Blaming a teammate or inflating your share turns it into a bad one.
© 2026 Preptima. Originally published at preptima.com (opens in a new tab).