Business Analyst resume example
Also indexed as: systems analyst · requirements analyst · process analyst
Business analyst is the title most often described in pure process language (gathered requirements, documented processes, liaised with stakeholders), which makes every applicant look identical. The differentiator is what the requirements produced: a system that shipped, a process that got faster, a cost that fell, a manual reconciliation that stopped existing.
Because the title spans everything from process mapping to data work to systems configuration, be explicit about which flavour you are. A posting for a Salesforce BA and one for a supply-chain process analyst share a name and almost nothing else.
A complete document in the Meridian family of layouts, rendered live, not a screenshot.
The screen
What a business analyst resume is actually judged on
Process outcomes, quantified
Cycle time removed, error rate reduced, headcount hours reclaimed, cost avoided.
The systems you actually configured
SAP, Salesforce, Workday, ServiceNow, Dynamics: naming the platform is often the whole match.
Requirements artefacts
BRDs, user stories, process maps, UAT plans: the concrete documents, with the scale of the programme behind them.
Bullets
5 bullets that would survive the screen
Copy the shape, not the words. Each one leads with the result, then names the mechanism, and carries the vocabulary of the field without listing it.
Mapped and redesigned the order-to-cash process across three systems, cutting invoice cycle time from 14 days to 5 and eliminating a 20-hour weekly manual reconciliation.
Wrote the requirements and UAT plan for a Salesforce migration covering 240 users; go-live ran with 11 defects, none severity-one.
Reduced order entry error rate from 4.1% to 0.6% by rebuilding the validation rules and retraining two teams on the revised process.
Facilitated 30+ workshops across finance, operations and IT to agree a single definition of a qualified order, ending an 18-month reporting dispute.
Built the reporting suite that replaced 14 spreadsheets, saving an estimated 60 analyst-hours a month.
The rewrite that matters most in this role
Gathered business requirements from stakeholders and documented them for the development team.
Ran 30+ cross-functional workshops to agree one definition of a qualified order, then wrote the requirements and UAT plan for the Salesforce migration that implemented it across 240 users.
Why it works: Requirements gathering is the baseline expectation. Naming the disagreement you resolved, the artefacts you produced and the system that shipped shows you can carry a programme rather than take notes in one.
Skills
Skills worth listing as a business analyst
Only what you would be comfortable being interviewed on. A long list dilutes every real match.
Technical & role-specific
Worth proving, not claiming
These belong inside a bullet that demonstrates them, not in a list. A line that says “communication” is worth nothing; a bullet showing you ran the workshop is worth a lot.
Keywords
What the tracking system is indexing
These are the terms a requisition for this title typically matches on. Use the ones that are true of you, inside the sentences where you did the work.
Paste the actual posting into the builder and you get this list generated from that requisition instead of the general case, including which terms you are already carrying and which bullet is the right home for the rest.
How keyword targeting worksMistakes
Errors specific to business analyst resumes
Not the generic advice. These are the ones that cost people interviews in this particular field.
Describing the method instead of the result
Everyone gathers requirements. Say what the requirements became and what it saved.
Being vague about the domain
Finance, supply chain, healthcare claims and CRM analysts are hired separately. Name yours in the summary line.
No systems named
Platform names are among the most reliably indexed keywords in this field. Omitting them costs matches.
Questions
Business Analyst resume questions
Business analyst or data analyst: which title should I use?
Whichever matches the postings you want. If your work is genuinely both, keep two versions; the two titles pull from different requisition pools.
Do I need Agile certification?
CBAP and PMI-PBA are recognised; a scrum certification helps only if the team is Agile. None of them substitute for a quantified process outcome.
How technical should the resume be?
Technical enough to prove you can talk to engineers (SQL, data models, integration patterns) without turning into an engineering resume.