Business Analyst CV Example
Requirements that shipped, processes redesigned and stakeholders aligned — BA work with delivered endings.
Business analyst CVs often dissolve into liaison language — "bridge between business and IT" — that describes position, not contribution. This example replaces liaison talk with delivered endings: requirements that became launched features, processes that got measurably faster, decisions that got made.
Why this CV works
- Requirements work is judged by what happened after launch — onboarding days, change-request rates — and this CV supplies those endings.
- BPMN, user stories and UAT are shown at volume (300+ stories, 30 testers), which conveys programme scale.
- The "never escalated" workstream is a subtle, credible stakeholder-skill claim — better than any adjective.
- Honest attribution ("at the two sites that implemented") signals an analyst who reports reality.
The professional summary
Business Analyst with 6 years across banking and logistics transformation programmes. Wrote and drove the requirements for a corporate-onboarding rebuild that cut onboarding from 11 days to 3, redesigned a claims process that removed 40% of handling steps, and ran UAT cycles that caught 200+ defects before go-live. Certified CBAP, fluent in BPMN and user-story mapping.
Name the transformation, its headline outcome and your certification. "Bridge between business and IT" tells the reader nothing they can verify — the 11-days-to-3 number tells them everything.
Writing the work experience
End every bullet after the go-live: what got faster, cheaper or cleaner once your requirements shipped. Requirements without outcomes are meeting minutes.
Turning duties into achievements
Skills on this CV
ATS tips for Business Analysts
- Include "business analysis" and "business analyst" plus "requirements gathering" — the three highest-volume BA filters.
- Name BPMN, JIRA and Confluence exactly; methodology and tooling are both filtered.
- If agile, write "user stories" and "acceptance criteria" verbatim — both are checklist phrases.
ATS checks help identify potential compatibility issues, but employers and ATS platforms use different criteria — no template or score can guarantee an outcome.
Writing tips
- Post-launch numbers are your proof; chase them down even after you roll off a programme.
- Story and tester counts convey scale that titles cannot.
- One de-escalation or alignment achievement, stated concretely, covers the entire "stakeholder skills" requirement.
Frequently asked questions
BA or product owner — which way should the CV lean?
Match the ad: BA leans process, requirements and UAT; PO leans backlog, prioritisation and outcomes. This example can tilt either way by reordering bullets.
Is SQL required for BAs?
Increasingly requested. Even "basic SQL for data validation" with a real use is worth its line.
How do I show impact from a support role?
Follow your artefacts downstream: what shipped, what got faster, what audit passed because your documentation held.
Keep learning
Related CV examples
Financial Analyst CV
Modelling, variance analysis and dashboards that changed decisions — an analyst CV with evidence.
View example →
Data Analyst CV
SQL, dashboards and analyses that changed decisions — an analyst CV with a paper trail.
View example →
Project Manager CV
On-time, on-budget delivery with the numbers stated — and the recovery story every PM interview asks for.
View example →
Product Manager CV
Outcomes over output — activation, retention and revenue moved, with the discovery that found them.
View example →Make this CV yours in minutes
Start from this business analyst example, replace the sample details with your own, then download as PDF or Word.