Business Analyst resume example
A business analyst sits between the business and the delivery team, so your resume should show both sides: the problems you uncovered, the requirements you wrote and what changed once the solution shipped.
This is a fictional, illustrative example -- not a real person or a promised result. Replace every detail with your own.
Full example resume
Sample content, for illustration -- not a real person.
Business analyst with 5 years of experience in banking operations, turning stakeholder needs into clear requirements for workflow and reporting projects. Recently redesigned loan intake, cutting processing time from 9 days to 4.
- •Mapped the loan intake process across 3 teams and removed 11 manual hand-offs, cutting processing time from 9 days to 4.
- •Wrote 140 user stories with acceptance criteria for a new servicing portal, reducing development rework by 30%.
- •Ran UAT with 25 branch users, catching 38 defects before launch.
- •Built SQL reports that replaced 5 spreadsheet trackers used by operations managers.
- •Analysed claims backlog data and proposed a triage rule that cleared 1,200 aged claims in 6 weeks.
- •Documented 20 core processes in BPMN for an audit, with no findings raised.
- •Coordinated 8 stakeholder workshops to agree on a single claims status definition.
Summary: weak vs. improved
Analytical business analyst skilled in bridging business and IT.
Business analyst in banking operations. Redesigned loan intake, cutting processing time from 9 days to 4.
"Bridging business and IT" is the job description, not an achievement. An industry and a before/after result show what that bridging produced.
Skills to include
- ✓Requirements gathering and user stories
- ✓Process mapping (BPMN)
- ✓SQL and Excel analysis
- ✓Jira and Confluence
- ✓Stakeholder workshops
- ✓UAT planning
Only list skills you actually have -- the AI review in the editor will flag a skill that doesn't appear anywhere else in your resume.
Bullet examples: weak vs. improved
Gathered requirements for the servicing portal.
Wrote 140 user stories with acceptance criteria for a new servicing portal, reducing development rework by 30%.
The volume and the rework reduction show the quality of your requirements, not just that you wrote them.
Worked on process improvement.
Mapped the loan intake process across 3 teams and removed 11 manual hand-offs, cutting processing time from 9 days to 4.
Concrete scope (3 teams, 11 hand-offs) and a time result make the improvement tangible.
Supported user acceptance testing.
Ran UAT with 25 branch users, catching 38 defects before launch.
"Ran" shows ownership, and the defect count shows the value of testing.
How this changes by experience level
Show documentation and analysis you produced, with scope: processes mapped, reports built, stories written.
Documented 20 core processes in BPMN for an audit, with no findings raised.
Own requirements end to end and tie them to delivery results, like the full example above.
See the full example above.
Show portfolio-level influence: prioritisation, business cases and mentoring other analysts.
Wrote the business case for a $1.2M workflow platform, approved first time and delivering 18% cost savings in year one.
Section order
- Contact
- Short summary
- Skills and tools
- Experience
- Certifications (CBAP, PMI-PBA)
- Education
Common mistakes to avoid
- !Describing meetings you attended instead of decisions you enabled
- !No link between your requirements and a business result
- !Listing methodologies without evidence you used them
Recommended template: Classic
Traditional single-column layout. Best ATS readability.