- Home
- Resume examples
- Business & management
- Business analyst
Business analyst resume example
A resume for a mid-level business analyst on systems projects in insurance and healthcare. Hiring managers want a BA who can understand the business quickly, write requirements developers can build from, and prove the change worked, so the bullets cover all three with numbers.
What recruiters look for
- Projects and their scale: the system, the budget or team size, and how many users or processes were affected.
- Requirements quality: user stories, acceptance criteria, defects avoided. Fewer surprises in testing is the clearest proof of a good BA.
- Process thinking: current-state and future-state maps, the bottlenecks you found and the time or cost saved.
- Data skills: SQL, Excel and a BI tool to size problems and check results. More BA job ads ask for SQL every year.
- Domain knowledge: insurance, banking, healthcare or supply chain. Domain fluency shortens your ramp-up.
Writing the summary
Name your domain, the kind of projects you work on and your mix of skills (process, requirements, data, testing). Add your IIBA or PMI certification if you have one.
Business analyst with eight years in insurance and health plans, six of them in business analysis, working between operations teams and developers on large systems projects. I turn messy processes into clear requirements, write the SQL to check my assumptions, and run user acceptance testing that catches problems before customers do. IIBA Certification of Capability in Business Analysis (CCBA).
Business analyst in an agile product team
Agile business analyst with five years in fintech, working as the product owner’s partner on two scrum teams. I write and refine stories, map customer journeys and use SQL and Amplitude to check every feature against its goal.
Moving from operations into business analysis
Claims operations team lead with six years of experience who has spent the last year as the business lead on our system upgrade: mapping processes, writing test cases and training users. Ready to move into a full-time business analyst role.
Bullet points that work
Strong lines for this role, beyond the ones in the example. Borrow the shape and put in your own numbers.
- Facilitated 30 requirements workshops with underwriting, finance and IT, agreeing scope for a new rating engine in 6 weeks.
- Wrote the business case for automating invoice matching, approved at $600,000 with an 18-month payback.
- Cut month-end reconciliation from 5 days to 2 by redesigning the process and specifying 3 automated reports.
- Built a traceability matrix linking 250 requirements to test cases, which the auditors accepted without findings.
- Identified $1.2 million a year in duplicate vendor payments through SQL analysis of 3 years of payables data.
- Documented 60 business rules hidden in legacy COBOL code with developers before the system was retired.
- Ran a vendor selection for a CRM with 4 bidders and a weighted scorecard, finishing on time and under budget.
- Trained 120 users on the new system with role-based guides and short videos, keeping go-live support tickets under 50.
- Introduced a definition of ready for user stories that cut sprint carry-over from 30% to 10%.
Skills to list
Hard skills
Soft skills
Certifications and licenses worth listing
- IIBA ECBA, CCBA or CBAP: the main business analysis certifications, by level. CCBA needs at least 3,750 hours of BA work and CBAP 7,500 hours.
- PMI Professional in Business Analysis (PMI-PBA): an alternative respected in project-heavy organizations.
- Certified ScrumMaster or Certified Scrum Product Owner: useful for BAs in agile teams.
- Industry designations (AINS or CPCU in insurance, for example) help in specialized domains.
Length and format
One page up to about eight years of experience; two pages for senior BAs with many large programs. Lead with your current project and its scale. Put certifications in their own section where a recruiter can spot them.
Common mistakes
- Listing documents you wrote (“created BRDs and FRDs”) without saying what they made possible.
- No numbers: give the number of stories, processes, users, workshops or the time and money saved.
- Skipping data skills. If you use SQL or a BI tool, put it in your bullets as well as the skills list.
- Writing as if you built the system. BAs define and verify; say exactly what you did.
- Ignoring the domain. Insurance, banking and healthcare employers screen for experience in their field.
Questions and answers
Do business analysts need to know SQL?
Increasingly, yes. Many job ads list it, and being able to check data yourself makes your requirements stronger. Basic queries with joins and aggregation are enough for most BA roles.
Which business analyst certification is best?
IIBA certifications (ECBA, CCBA, CBAP) are the most widely recognized and go by experience level. PMI-PBA is a good alternative if you work closely with project managers.
What is the difference between a business analyst and a data analyst resume?
A business analyst resume centers on requirements, processes and delivering change; a data analyst resume centers on analysis, models and reporting. See the data analyst example for the contrast.
Related examples
All Business & management examples- Data analystMid-level analyst: experiments, metrics and decisions the business made.Mid-level
- Management consultantPost-MBA consultant: client impact, engagements and analytical depth.Mid-level
- Product managerMid-level B2B SaaS product manager: discovery, adoption and revenue.Mid-level
- Project managerBudgets, schedules and steering committees, with PMP and earned value.Mid-level
- Executive assistantSupporting a CEO: calendar, travel, board logistics and special projects.Mid-level
- Office managerRunning the office: budget, vendors, facilities, payroll support and onboarding.Mid-level