Your Contribution vs Your Team's Result

Almost every result worth putting on a resume was produced by more than one person, which creates a genuine problem: describing only your slice can make real work sound trivial, and describing the whole result can claim other people’s. The workable answer is to state the collective outcome and your specific role in it, in the same line. “As one of three engineers on the replatforming, I built the payments integration” is accurate, informative, and cannot be contradicted.

Getting this wrong in either direction has a cost. Overclaiming fails in a reference conversation. Underclaiming loses you interviews for work you actually did.

Why AI drafts overclaim here

A drafting tool sees an outcome and a person and joins them with the shortest available construction, which is the one that makes the person the agent. “The team reduced processing time” becomes “reduced processing time.” The grammar is tighter and the claim is larger, and nothing in the process registers that difference as meaningful.

The result is a resume where every collective achievement has been quietly reassigned to you. Individually each line looks reasonable; read together they describe someone who did everything, which is the impression a careful reader forms and discounts. Ownership creep is one of the standard directions in which generated bullets drift, and it is the direction that a referee is most likely to correct.

The construction that works

Two clauses: the shared result, and your part.

Contributed the data model to a cross-team analytics rebuild that replaced four separate reporting systems.

One of two developers on the migration; owned the customer records component end to end.

Ran the weekly coordination for a programme led by the head of operations, keeping five workstreams to a single schedule.

Each of these is longer than the overclaiming version and considerably more informative. A reader learns the size of the effort and where you sat in it, which is what they were trying to work out anyway. The phrase “one of two” does more for you than an unqualified “led,” because it is credible.

Naming the collective without diminishing yourself

People avoid words like “contributed to” because they sound weak. The weakness comes from vagueness, not from honesty. “Contributed to the migration” is weak. “Contributed the reconciliation logic to the migration” is specific and strong. The fix is always to name what you contributed rather than to upgrade the verb.

This is worth stating plainly: specificity is what makes a modest claim impressive. A named component, a named deliverable, a named decision you made carries more weight than a broad claim of leadership, and it is available to you at any level of seniority.

Where the line actually sits

Some rough tests for whether a result is yours to claim outright:

• Would anyone else describe this as theirs? If yes, share the credit in the sentence.
• Was your contribution necessary? Not sufficient, necessary. If it would not have happened without you, “led” or “drove” may be right even without a title.
• Who got asked when it went wrong? Accountability is the most reliable indicator of ownership, and organisations tend to remember it accurately.
• Would your former manager use this verb about you? The single most useful test, and the one that matches how a reference conversation actually probes your role.

Where the answers conflict, describe the arrangement in the sentence instead of picking a verb to summarise it. Ambiguity in your own head should become explicitness on the page, not a stronger word.

Team results with individual metrics

A specific trap: attaching a collective metric to an individual claim. “Increased conversion by a fifth” where the increase came from a programme of a dozen changes, one of which was yours, is a misattribution even if every number in it is real.

If you want to use the collective figure, frame it as collective and then say what you did: “part of a programme that raised conversion materially; I rebuilt the checkout validation step.” Nobody is deceived and nothing is lost. If you cannot separate your effect from everyone else’s, that is normal, and the honest response is to describe the work rather than the movement in the metric — narrowing the claim to what you can support.

Junior roles and early careers

At the start of a career almost nothing is solely yours, and this is where underclaiming does the most damage. The answer is not to inflate the verb; it is to be precise about the component. An intern who wrote a specific script that is still in use has a stronger line than an intern who “supported the engineering team,” and both descriptions are of the same six weeks.

The same applies to group coursework and bootcamp projects, where “we built” is the accurate frame. Say what the group built, then what you wrote.

Reading for it

On a final pass, count how many bullets make you the sole agent of a result. If it is nearly all of them, the page is wrong, because that is not how work happens. Adjusting a handful of lines to acknowledge the people who were there makes the whole document read as more credible, not less — and it is one of the things a deliberate sceptical read of your own resume is looking for.