Business analyst resume examples that show the decision, not the document.
Almost every business analyst resume contains the sentence 'gathered requirements from stakeholders'. It describes the input to the job, not the job. What a hiring manager wants to know is what changed because you were there: the process that got shorter, the build that did not get made, the report that stopped being wrong, the decision the business took differently. There is a second problem too — 'business analyst' means a systems analyst working with engineers in some companies and a process analyst working with operations in others. Applying without diagnosing which one is why good candidates get filtered.
- Ideal length
- 1–2 pages
- Two tracks
- Systems / IT vs process
- Weakest line
- 'Gathered requirements'
- Median (May 2024)
- $101,190
Tomasz Nowicki
Business Analyst · Payments Platform
Boston, MA · linkedin.com/in/tomasz-nowicki-ba
Summary
Business analyst on a payments platform serving 4,000 merchants, working between operations and a two-squad engineering team. Write the requirements that ship: 60+ user stories with acceptance criteria last year, with a 12% rework rate against a 30% team baseline. Found that 40% of refund tickets came from one ambiguous status label, which led to a change that removed roughly 900 tickets a quarter. SQL-fluent — I check the claim before I write the story.
Experience
Business Analyst — Payments · B2B payments platform (4,000 merchants)
2022 — Present
- Own requirements for the refunds and disputes domain — wrote 60+ user stories with acceptance criteria last year at a 12% rework rate against a 30% team baseline.
- Analysed 14,000 support tickets in SQL and found 40% of refund contacts traced to one ambiguous status label; the resulting change removed roughly 900 tickets a quarter.
- Mapped the current and target dispute-handling process across four teams, cutting average handling time from 9 days to 5.
- Ran the requirements workshops for a chargeback-automation build, and killed one proposed feature by showing it addressed 3% of volume at a disproportionate cost.
- Built the operations reporting layer in Looker that replaced three manually maintained spreadsheets.
Business Analyst — Operations · Logistics services provider (600 employees)
2019 — 2022
- Redesigned the order-exception process with the warehouse and customer service teams, cutting exception resolution time by roughly 35%.
- Wrote the BRD and led UAT for a WMS module rollout across three depots; 120 test cases, no critical defects in production.
- Produced weekly operational reporting for the COO and trained 15 supervisors to self-serve it.
Skills
Education
B.Sc. Economics — Boston University, 2019
Certifications
IIBA ECBA (2021) · CBAP — sitting 2026 · Advanced SQL (DataCamp track)
Languages
English (fluent) · Polish (native)
Why this example works
Requirements work is measured by rework, not volume
'60+ stories at a 12% rework rate against a 30% team baseline.' Anyone can write stories; the question is whether engineering could build from them without coming back. This is the metric that distinguishes a strong BA and it is almost never on the page.
A feature killed counts as an outcome
Showing that a proposed build addressed 3% of volume is real analytical value — arguably more than shipping it. Hiring managers notice a BA who prevents waste, because most of them are drowning in requests that should never have been built.
SQL turns opinions into findings
'Analysed 14,000 tickets in SQL' is the difference between reporting what stakeholders said and establishing what is true. Data fluency is the fastest-rising expectation in BA hiring and the clearest separator between the two tracks.
Business Analyst resume summary examples
Three to four lines: scope, stack or specialism, one quantified win. Match the register to your seniority.
Junior / career changer
Business analyst with two years supporting an operations team — process documentation, reporting and UAT — after moving across from customer support, where I learned where the process actually breaks. Comfortable in SQL and Jira; wrote the exception-handling documentation the team still uses. ECBA certified, looking for a systems-facing BA role.
IT / systems business analyst
Business analyst working between operations and a two-squad engineering team on a payments platform serving 4,000 merchants. Own requirements for the refunds and disputes domain — 60+ stories with acceptance criteria last year at a 12% rework rate against a 30% baseline. SQL-fluent; I check the claim before I write the story.
Process improvement analyst
Business analyst focused on process redesign in service operations: current and target state mapping, root-cause analysis and implementation with the teams doing the work. Cut dispute handling from 9 days to 5 across four teams, and exception resolution by roughly 35% at a previous employer. Lean Six Sigma Green Belt.
Data-heavy BA
Business analyst working at the boundary of analytics and delivery — SQL and Python for investigation, requirements and acceptance criteria for the build. Found that 40% of refund contacts traced to a single ambiguous status label, which removed roughly 900 tickets a quarter once fixed. Built the reporting layer that replaced three manually maintained spreadsheets.
Senior / lead BA
Senior business analyst leading requirements across a four-team programme, mentoring two junior BAs and owning the intake process that decides what gets built. Introduced a lightweight business-case template that halved the number of requests reaching engineering while raising the proportion delivered. CBAP certified.
Skills that belong on a business analyst resume
Requirements and delivery
- Requirements elicitation
- User stories and acceptance criteria
- BRD / FRD documentation
- Backlog refinement
- UAT planning and execution
- Gap and impact analysis
Process and analysis
- Process mapping (BPMN, swimlanes)
- Current and target state design
- Root-cause analysis
- Business case development
- Cost-benefit analysis
- Lean / Six Sigma methods
Data and tools
- SQL
- Jira / Confluence
- Looker / Tableau / Power BI
- Excel modelling
- Figma / wireframing
- API and integration literacy
Bullet point formulas that get interviews
Fill the brackets with your numbers — the structure does the selling.
- Wrote [n] stories at [rework rate] — e.g. “60+ stories with acceptance criteria at a 12% rework rate against a 30% team baseline.”
- Found [insight] in [data volume] — e.g. “Analysed 14,000 tickets in SQL; 40% of refund contacts traced to one ambiguous status label.”
- Cut [process metric] from [x] to [y] — e.g. “Dispute handling from 9 days to 5 across four teams.”
- Prevented a build worth [avoided cost] — e.g. “Killed a proposed feature by showing it addressed 3% of volume.”
- Mapped [process] across [n] teams — e.g. “Current and target state for dispute handling across four teams.”
- Led UAT with [n] cases and [outcome] — e.g. “120 test cases across three depots; no critical defects in production.”
- Replaced [manual artefact] with [system] — e.g. “Three maintained spreadsheets replaced by a Looker reporting layer.”
- Ran [workshop type] with [stakeholders] — e.g. “Requirements workshops across operations, risk and engineering.”
- Trained [n] people to self-serve — e.g. “15 supervisors trained to run their own operational reporting.”
- Owned intake for [scope] — e.g. “Request intake for a four-team programme; halved requests reaching engineering.”
ATS keywords for business analyst roles
Filters match tokens from the posting. These are the terms worth mirroring — verbatim — when they appear in the job ad.
| Keyword | Priority |
|---|---|
| requirements gathering / elicitation | High |
| user stories and acceptance criteria | High |
| stakeholder management | High |
| process mapping / BPMN | High |
| SQL | High |
| UAT / user acceptance testing | High |
| Agile / Scrum | High |
| Jira / Confluence | High |
| gap analysis | Medium |
| business case / cost-benefit analysis | Medium |
| data visualisation (Tableau, Power BI, Looker) | Medium |
| BRD / functional specification | Medium |
| CBAP / CCBA / ECBA / PMI-PBA | Medium |
| Lean / Six Sigma | Medium |
Don't guess — score your resume against the specific posting and see exactly which terms are missing.
How to write a business analyst resume
Work out which BA job the posting is
If it sits with engineering — user stories, acceptance criteria, APIs, sprint ceremonies, a product owner — it is a systems BA role. If it sits with operations — process mapping, business cases, change management, cost reduction — it is a process BA role. Some are hybrids. Lead with the matching half of your experience and mirror their vocabulary; a systems team reading 'process improvement initiatives' assumes you have never written an acceptance criterion.
Write the decision, not the artefact
Documents are inputs. Replace 'gathered requirements from stakeholders and produced a BRD' with what happened: the process that got shorter, the tickets that stopped arriving, the feature that was not built, the decision the business took differently. Artefacts belong in the skills section; outcomes belong in the bullets.
Show that your requirements were good ones
Rework rate, defects traced to requirements, UAT pass rate, stories accepted without clarification, cycle time from refinement to done. Engineering teams have strong opinions about BA quality and no way to assess it from a resume — unless you give them a number.
Prove data fluency, because it is now assumed
SQL at minimum, and say what you used it for. The distinction between a BA who reports what stakeholders believe and one who checks it is the clearest quality signal in this market, and it is increasingly what separates the pay bands.
Name the domain, not just the methodology
Payments, claims, supply chain, lending, healthcare eligibility. Domain knowledge is what makes a BA productive in month one rather than month six, and hiring managers filter on it heavily — often more heavily than on certification.
Skip the blank page.
Build this resume in Resumap — free templates, unwatermarked PDF, and an ATS check against the exact posting when you're ready.
Start freeMistakes that filter business analysts out
'Gathered requirements from stakeholders'
The emptiest sentence in the field. Say what the requirements changed — a shorter process, a prevented build, a metric that moved.
Writing one resume for both BA tracks
Systems and process BA roles read for different evidence. Diagnose the posting and lead with the matching half.
Listing methodologies as achievements
'Agile, Waterfall, Scrum, Kanban' is context, not accomplishment. Put them in skills and use the bullets for outcomes.
No evidence of data work
SQL is close to table stakes now. If you have it, show what you found with it; if you do not, it is the highest-return thing to learn.
Claiming delivery outcomes as solely yours
You worked with engineers, ops and a product owner. Name your part — the analysis, the requirements, the intake decision — which is both honest and more specific.
Omitting the domain
Payments, claims, logistics, lending. Domain is often the first filter, ahead of tooling and certification.
A three-page document listing every project
One to two pages. Pick the projects with outcomes and drop the rest — a long list of BRDs written reads as busywork.
Business Analyst salary ranges (US)
United States market. Absolute figures differ by country — the gaps between levels travel better than the numbers.
| 10th percentile (management analysts) | under $59,720 |
| Median (management analysts, May 2024) | $101,190 |
| 90th percentile | above $174,140 |
| IT / systems BA in technology | typically toward the upper half |
| Operational / process BA outside technology | typically toward the lower half |
BLS has no standalone business analyst occupation; the closest fits are management analysts (median $101,190, May 2024; 10th–90th $59,720–$174,140; +9% through 2034 with ~98,100 annual openings) and computer systems analysts for the IT track. Pay in practice tracks the industry and the track more than the title — product-adjacent and data-heavy BA roles in technology sit well above operational BA roles in the same city.
Primary source: U.S. Bureau of Labor Statistics (OEWS/OOH). Self-reported aggregator figures are labelled as such.
Certifications worth listing
- IIBA ECBA — the entry-level credential, useful when you are moving into BA work from another function
- IIBA CCBA and CBAP — mid and senior IIBA credentials; CBAP carries a substantial experience requirement and is the one most often named in senior postings
- PMI-PBA — the Project Management Institute's business analysis credential; preferred in organisations already standardised on PMI
- Lean Six Sigma Green Belt — genuinely relevant for the process track, largely irrelevant for the systems track
- SQL and analytics coursework — not a certification employers ask for by name, but the skill they increasingly test for
Templates that fit business analyst resumes
Business Analyst resume FAQ
What is the difference between an IT business analyst and a process business analyst?
The systems or IT BA works alongside engineering: user stories, acceptance criteria, integrations, sprint ceremonies. The process BA works with operations: process mapping, business cases, change management, efficiency. Some roles blend them. Read the duties rather than the title, and lead with the half that matches.
What should replace 'gathered requirements' on my resume?
The consequence. 'Wrote the requirements for the refunds rebuild; handling time fell from 9 days to 5.' 'Killed a proposed feature by showing it addressed 3% of volume.' Requirements are the input — the resume needs to show what came out.
Is SQL necessary for a business analyst?
Close to it now. It is the difference between reporting what stakeholders believe and establishing what is true, and it is increasingly the dividing line between pay bands. If you have it, show what you found; if not, it is the highest-return skill to add.
Is a CBAP worth getting?
It helps in organisations that name it, and the CBAP specifically carries weight because of its experience requirement. But domain knowledge and demonstrable outcomes outrank certification in most hiring decisions — get the certificate if your target employers ask for it, not as a substitute for evidence.
How do I become a business analyst from another role?
Use the domain you already have. Support, operations, finance and clinical staff all know where processes break, which is the expensive half of the job to learn. Document one process end to end, do the analysis, propose the change — then write it up as a BA project. The ECBA is a reasonable signal while you build that evidence.
Should I list every project I worked on?
No. Pick the ones with outcomes you can state and defend, and group the rest. A resume listing twelve projects with no results reads as a document-production role rather than an analytical one.
How long should a BA resume be?
One page early, two once you have several substantial projects. Keep the first half of page one carrying the track, the domain and two outcomes — that is what determines whether page two gets read.
More resume examples
Your business analyst resume, done properly — free.
Unwatermarked PDF, ATS-safe templates, and a real score against any posting when you want it.
Build my resume