Operations & Management

Business Analyst resume example & template

A mid-level business analyst resume for someone who moved from order management into requirements work. Each bullet names the artifact produced (user stories, BPMN maps, test cases) and what changed because of it.

  • Names the deliverables BA managers look for: user stories, acceptance criteria, BPMN, UAT.
  • Shows enough SQL and reporting to prove the analyst can validate data, not just gather it.
  • The CCBA credential and IIBA wording match what enterprise postings filter on.
100%
Nadia Haddad
Business Analyst · Requirements, Process Mapping & UAT
Milwaukee, WI(414) 555-0137nadia.haddad@email.comlinkedin.com/in/nadiahaddad

Summary

Business analyst with 8 years in manufacturing and banking, 6 of them writing requirements for Scrum teams. Works from current-state BPMN maps to user stories, SQL checks and UAT sign-off. Background in order management means she knows how the people using the system actually work.

Experience

Business Analyst II · Associated BankMar 2023 – Present
Milwaukee, WI
  • Wrote 140+ user stories with Given/When/Then criteria for a commercial loan origination rebuild on nCino.
  • Mapped commercial loan booking in BPMN 2.0: 9 handoffs and 3 duplicate entry points; the future-state design cut average booking time from 6 days to 3.5.
  • Queried loan and customer tables in SQL Server before migration, catching 2,300 records missing NAICS codes.
  • Ran UAT for 3 quarterly releases: wrote 210 test cases, triaged defects in Jira and collected sign-off from 14 relationship managers and loan processors.
Business Analyst · Brady CorporationJun 2020 – Feb 2023
Milwaukee, WI
  • Gathered order-to-cash requirements for an SAP S/4HANA upgrade in 30+ workshops with customer service, credit and warehouse leads.
  • Built a Power BI backorder report on SAP sales data, replacing a 5-hour weekly Excel pull for 40 service reps.
  • Documented 22 as-is and to-be swimlane diagrams in Lucidchart, later reused as go-live training material.
Order Management Specialist · Brady CorporationJul 2018 – May 2020
Milwaukee, WI
  • Entered and expedited 60 to 80 label and signage orders a day in SAP, clearing pricing holds and credit blocks.
  • Flagged a pricing-condition error undercharging 3 distributors; the fix recovered $48,000 in the first year.

Education

B.B.A. Information Technology Management · University of Wisconsin-MilwaukeeMay 2018

Skills

Analysis: Elicitation, User stories & acceptance criteria, BPMN 2.0, Gap analysis, UAT planning, BRD/FRD
Tools: Jira, Confluence, Visio, Lucidchart, Power BI, Excel
Data & Systems: SQL (SQL Server), SAP S/4HANA SD, nCino
Delivery: Scrum, Backlog refinement, Release sign-off

Certifications

Certification of Capability in Business Analysis (CCBA), IIBA

How to write a business analyst resume

What hiring teams in this field actually screen for, and the terms that get matched.

What business analyst hiring managers screen for

BA managers want to see the artifacts you produced and who used them. Name the deliverable (user stories, a BRD, BPMN maps, test cases), the volume, and the team or stakeholders it served. Then show one outcome the business noticed: shorter cycle time, fewer defects at go-live, a data problem caught before migration. Domain matters too. A lending, claims or ERP background shortens ramp-up time, so say which processes you know from the inside, not just which industries you have touched.

Terms and credentials that get matched

Postings for business analysts repeat the same nouns: requirements elicitation, user stories, acceptance criteria, BPMN or swimlane process mapping, UAT, BRD/FRD, Agile/Scrum, Jira and Confluence, and SQL. Use the exact spellings. If you model in Visio or Lucidchart, list them. For credentials, the IIBA ladder is ECBA (no experience needed), CCBA (3,750 hours of BA work in seven years) and CBAP (7,500 hours in ten years). List the full name and the IIBA as issuer, and only claim the level you actually hold.

Common mistakes on business analyst resumes

The most common mistake is a list of meetings: 'liaised with stakeholders,' 'gathered requirements,' 'bridged business and IT.' Every BA does that, so it says nothing. Replace it with what came out of the room. Another mistake is claiming a project's whole result as your own; say what the analysis changed and let the team own the delivery. Finally, don't overstate SQL or data skills. If you write joins to validate data, say so plainly, because interviewers often test it with a live query.

Business Analyst resume FAQ

Quick answers before you start writing.

What should a business analyst resume include?

A strong business analyst resume opens with a concise professional summary, then work experience written as quantified, results-first bullets, followed by education, a skills section, and any certifications. The example above shows each section in order.

What skills should a business analyst resume highlight?

Lead with the skills the job posting asks for. For a business analyst, recruiters and ATS filters commonly look for Elicitation, User stories & acceptance criteria, BPMN 2.0, Gap analysis, UAT planning, and BRD/FRD. Group them so they are easy to scan.

Is this business analyst resume template ATS-friendly?

Yes. It uses a single-column structure, standard section headings, real text (no text trapped in images), and no tables or graphics that confuse applicant-tracking systems, so it parses cleanly while still looking polished.

How long should a business analyst resume be?

One page is ideal for most business analysts. Use two pages only if you have ten or more years of directly relevant experience, then tune the text size and margins so it stays clean.

Make this resume yours

Edit the wording, switch styles and colours, and tailor it to each job. All free.

Edit this template for free

Free · your data stays yours · no credit card