Business and finance

Business Analyst resume example

Show requirements you turned into shipped change, and the measured effect on the process.

Below: what to put in the summary, six sample bullets with numbers, the skills worth listing, and the mistakes that show up most. The sample resume is a fictional person.

Start with this layout Upload my resume

Free to write and edit. You pay only when you download.

Sample business analyst resume for Elena Kowalski, a fictional person, in the Split layout. The names, employers and numbers are invented.

What to put in the summary

Name the industry, the kind of work (requirements, process redesign, reporting), and how you work with both business users and developers. A good summary shows you can translate between the two groups.

Business analyst in insurance operations with five years turning policy-team requests into clear requirements and tested changes. Comfortable in workshops, SQL and user acceptance testing. Most recently reduced manual claim-handling steps from 19 to 11.

Example summary, written for a fictional business analyst.

Sample bullets with numbers

Show the before-and-after of a process in numbers: steps, days, errors, handoffs. Requirements documents are outputs; the improved process is the outcome.

  • Mapped the claim intake process end to end and cut manual steps from 19 to 11, reducing average handling time by 1.5 days.
  • Wrote requirements and acceptance criteria for a policy-document upload feature, delivered in two sprints with no post-launch defects over 60 days.
  • Facilitated 14 workshops with claims, legal and IT to settle a rules conflict that had stalled a project for three months.
  • Ran user acceptance testing for 40 users across two regions and tracked 63 defects to closure.
  • Built a SQL report that showed 12% of claims were being reopened for missing information, leading to a revised intake form.
  • Documented 30 operating procedures that onboarding staff now use during their first month.

These numbers are invented to show the shape of a good bullet. Use your own, and leave a number out rather than guess.

Key skills to list

  • Requirements gathering
  • Process mapping (BPMN)
  • User stories and acceptance criteria
  • SQL
  • UAT
  • Jira and Confluence
  • Visio
  • Workshop facilitation
  • Gap analysis
  • Power BI

Include both the practices (requirements, mapping, UAT) and the tools. Hiring managers for analyst roles look for both.

Common mistakes

  1. Listing deliverables (BRDs, process maps) with no result they produced.
  2. Writing “liaison between business and IT” as the whole job description.
  3. Hiding industry knowledge, which is often the deciding factor.
  4. Using a long skills list in place of two or three strong stories.

A layout that suits this resume

Split centres your name and gives two equal columns, useful for a business analyst who needs to show process work on one side and tools and certifications on the other. See the Split template, or compare all 22 layouts.

Business Analyst resume questions

What is the difference between a business analyst and a data analyst on a resume?

A business analyst’s evidence is requirements, process change and stakeholder work; a data analyst’s is queries, dashboards and findings. Many jobs mix them, so show both in the bullets you have.

Is a certification worth it?

A CBAP or PMI-PBA helps in some sectors and for senior roles, but real bullets matter more. List it if you hold it.

Related resume examples

Write your business analyst resume

Start from this layout, swap the sample facts for yours, and check the result against the job post before you download.

Start with the Split template Upload my current resume

Free to write and edit. You pay only when you download.