Writing experience that shows your contribution
Go one step beyond listing your duties: explain which problems you worked on and how you contributed.
Separate the context from your role
Distinguish what the whole team achieved from what you did yourself. State the project's purpose in one sentence, then describe your scope, who you worked with and the key decisions you made. Do not present team results as your personal results.
Describe actions with specific verbs
Instead of “participated in a project”, write what you actually did: researched, designed, built, tested. Adding, where useful, what information you based a decision on and why you chose that approach shows the context of the experience.
Use numbers only when you can verify them
If you have figures that can be confirmed from records, give the time period and what they are compared against. If you do not, describe the deliverables, the process you improved or the problem you solved. There is no need to invent impressive-looking results.
Check for confidential and personal information
Before mentioning client names, non-public revenue or internal screens, confirm that they can be shared. If needed, describe the company and project in general terms, and check the access settings of your portfolio links.