Make a class project useful to a hiring conversation.

Explain what you did in the project.

When you write “Completed a group research project,” a reader still needs to know which part you did. Describe your task, explain how you approached it and choose a piece of work you could discuss. Coursework, internships and volunteering can all give you examples. Label each experience accurately so an employer can understand when and where you did the work.

Start with something you actually did. Gather the original assignment, your notes and a version of the output you are allowed to share. Separate what the team produced from what you personally contributed. If the work changed after your involvement, say which version represents your part. Avoid turning a collective achievement into a claim that you did everything.

Worked example: Morgan’s student-club survey.

Morgan is a fictional recent economics graduate interested in understanding customers. Morgan’s student club collected a member survey as a team. Morgan cleaned the responses, summarized themes and prepared a one-page recommendation for the organizers. The example below shows how Morgan could describe that contribution and prepare to answer questions about it.

The second statement gives the reader specific questions to ask. Why were repeated submissions handled that way? Could another reader reproduce the themes? Which finding supported a recommendation? Morgan can use the cleaning log, theme notes and one-page document to answer. Keeping those documents together also makes it easier to check that the description matches the work.

Build the evidence in four parts.

Contribution. Name your action with a concrete verb: cleaned, tested, compared, interviewed or documented. Explain who did the other work if it matters. “Our team collected responses; I cleaned and summarized them” is more accurate than claiming to have led the whole study.

Work sample. Choose a small, readable example. Morgan could share a few anonymized responses alongside a short explanation of how they were grouped. This lets a reader follow the process without working through the entire survey dataset, provided there is permission to share it.

Method. Explain one decision and its reason. Morgan might show the rules for grouping similar comments and acknowledge a difficult case. Include enough context that a reader can distinguish a considered choice from a polished final slide.

Result and limits. State what happened, not what you hoped would happen. “Organizers received my recommendation” is a result. “Increased engagement” is not justified without evidence. Name the limitations of the sample and what was not measured.

The same structure works for a class app.

Imagine a different student who implemented input validation in a team’s class app. A useful statement could be: “I added validation for missing booking dates and wrote reproducible test steps for valid, empty and reversed date ranges. My notes record expected and observed behavior. I did not implement authentication or test production-scale traffic.” The work sample could include the relevant code and test notes, if course rules and teammates permit sharing.

A reader could follow those test steps and ask why the student chose each case. The student could explain a failure they found, how they investigated it and whether they fixed it. Those details give them something useful to discuss even if the app was only ever used in class.

Make a shareable version, then find the gap.

Ask classmates or collaborators before sharing their work. Remove names, emails and confidential material, and check course, employer and participant restrictions. Anonymization is not a substitute for permission. If you cannot share an artifact, describe the method without exposing protected information; do not upload private work merely to make a portfolio look complete.

Open the Role Evidence Map and load Morgan’s example to see all three rows. When you write your own answers, describe work you actually did and keep any useful notes nearby. Then compare your experience with the job’s requirements and choose something you want to learn or practice next.