A useful starting point
Show a requirement you clarified, a process you mapped, and a change that shipped. Two pages. Skip UML as decoration. Skip this if you are applying for product management without discovery ownership — the BA example is the honest file.
These examples illustrate structure, not a real applicant’s history. Replace every sample detail with your own evidence. Follow the employer’s instructions on qualifications, registration, document length and file format.
Evidence to consider
- Elicitation method
- Artefacts (stories, process maps)
- A shipped change
- Stakeholder set
Illustrative achievement bullets
- Wrote 90 user stories for a claims rebuild; 80% accepted first sprint review
- Mapped an as-is process of 40 steps and cut 11 after workshops with ops
- Bridged finance and engineering on a VAT rule that unblocked go-live
- Built a requirements traceability sheet used in UAT sign-off
Relevant skills to substantiate
Workshops · User stories · Process mapping · SQL basics · Stakeholder management · UAT
What to leave out
- Photos
- Every BA tool
- Unowned “the programme delivered”
Choose a layout
Explore the classic template or use it in the CV builder. This is a suggested layout; follow the vacancy’s requirements.