UX/UI designer CV: how to highlight projects and internships

Your CV should explain your contribution before a recruiter opens the portfolio. Show tasks and context rather than an unexplained software list or proficiency score.
1. Separate different settings
Use sections for internships and experience, then academic or personal projects. Give dates, topic, relevant team size and your role. Observing a usability session and leading one are different experiences.
2. Use concrete wording
| Context | Example, if accurate |
|---|---|
| Internship | Helped prepare wireframes for review by the supervising designer. |
| Personal project | Designed a mobile booking journey and documented navigation decisions. |
| Team project | Owned search screens and helped make components consistent. |
3. Connect skills to deliverables
For Figma, name functions you actually used: components, variants, auto layout or prototyping. For research, explain whether you prepared questions, took notes or produced a synthesis. Link directly to the relevant case study.
4. Describe a verifiable result
Fictional example: “Two-person academic project: workshop-search prototype. Contribution: journey, wireframes and an exploratory test with three volunteers. Revised two labels after observation; prototype not built.”
This describes work without inventing business impact. Without reliable metrics, discuss a completed deliverable, justified decision or resolved difficulty.
5. Check readability and access
Use clear headings, selectable text, useful contact details and accessible portfolio links. Do not turn essential information into an image. State actual language abilities and availability in Cameroon.
Adapt the project selection to each role. Interface-focused work and graphic-design duties call for different evidence.

Illustrative stock photos; the people shown are not presented as Kamerjob employers. Cover and illustration: Pexels / Pexels.
Find opportunities on Kamerjob and tailor your portfolio to the actual duties in each vacancy.
The Kamerjob team
Comments
Loading comments…