Early-career applications often depend on work done with other people: a university assignment, volunteer event, placement task, or junior team project. The experience can be relevant, but writing about it is awkward. Use only 'we' and the reader may not see your role; use only 'I led' and you may accidentally claim a decision, result, or authority that belonged to the group.
A stronger description names the project setting first, then states the part you actually owned, supported, or completed. This is not about making a small task sound larger. It gives a reader a reliable way to understand what you did, how you worked with others, and which parts you can explain in an application or conversation.
Why this happens
Applicants with limited formal experience may be told to demonstrate impact before they have held a role with broad accountability. A group project can then become the only visible evidence of research, communication, organising information, or presenting a recommendation. The pressure to sound competitive can blur the boundary between contributing to a shared outcome and owning the whole outcome.
Europass allows people to record work experience, learning, skills, achievements, and projects, then select information for particular applications. That makes project work a legitimate source of evidence when its setting remains visible. It does not turn a team exercise, class brief, or volunteer shift into a claim of employer-level responsibility.
What to check or improve
Name the setting and the team context: for example, a course project, supervised placement, volunteer event, or junior workstream. Then use a specific verb for your own contribution: gathered, checked, drafted, organised, compared, presented, documented, or supported. Include the material you worked with or the handover you produced when it is real and relevant to the vacancy.
Avoid vague superlatives such as 'drove success' unless you can explain exactly what changed and who confirmed it. Do not attribute a team's revenue, attendance, or performance to yourself. If an outcome belongs to the group, say that it was a team output and make your individual task clear. Keep project notes, feedback, links, and dates in your private record.
Choose only projects that help answer the vacancy's actual tasks. A junior operations role may need evidence of organising information and handovers; a research-support role may need evidence of careful source notes and data handling. The same project can be described differently for relevance, but its setting, dates, and your contribution must stay consistent.
Concrete example
Imagine an early-career applicant who worked in a four-person university group on a service-improvement brief and is applying for a junior coordination role.
Illustrative example
Led a successful service transformation that improved customer satisfaction.
University team project | Service-improvement brief Organised interview notes, maintained the team's action list, and drafted the handover summary used in the final group presentation.
This is an illustrative example. It shows a concrete individual contribution and the group setting without claiming ownership of a business result or a customer outcome.
If you still hear nothing
A clear project entry cannot replace experience, authorisation, a portfolio, or a qualification a vacancy requires. A non-response does not prove that a stronger verb or an invented metric would have changed the outcome. Do not convert shared work into an individual result simply to make the bullet look more impressive.
Keep the posting and the version you sent. Review whether the project was relevant, whether the setting was visible, and whether every line describes a task you can explain. If you need more evidence, seek a legitimate project, placement, volunteer responsibility, or junior role where your own contribution can be recorded accurately.
The practical takeaway
Team-based work can be useful evidence when the reader can see both the project context and your real contribution.
Name the setting, describe the part you did, and keep the shared result in proportion.
Check the signals your resume is sending
ResuNexx can help you turn genuine project experience into CV evidence that is specific without overstating your role.
Get Your Free ResuNexx Resume Preview ↗