Business · Mid-career

Business Analyst Resume Example

This example suits a business analyst with three to eight years of experience, including analysts who started in an operational role. It shows how to give requirements, process and testing work a visible size and result, and how to make domain knowledge clear to a reader in the same sector.

The example resume

Laid out in the Margin template. The person, employers, schools and figures in this example are invented for illustration. Any resemblance to real people or organisations is unintended.

Arjun Menon

Business Analyst | Banking Operations, Requirements, Process Improvement

  • arjun.menon@example.com
  • +1 555 0171
  • Bengaluru, India
  • linkedin.example.com/in/arjun-menon

Professional summary

Business analyst with seven years of experience in banking and insurance, including four leading requirements and process work on lending and onboarding systems. Skilled in workshop facilitation, BPMN process mapping, user stories and UAT, and trusted by operations and engineering teams to turn a vague problem into a clear, testable scope.

Work experience

Business Analyst

Kaveri Point Bank, Bengaluru

Aug 2022 – Present

  • Led requirements for a digital personal-loan journey, running 18 workshops with credit, operations, compliance and IT and producing a signed-off backlog of 140 user stories
  • Mapped the as-is and to-be loan process in BPMN, removing 9 of 31 manual handoffs and cutting average approval time from five days to two
  • Wrote acceptance criteria in Gherkin and maintained a traceability matrix linking every story to a test case and, where relevant, a regulatory requirement
  • Planned and coordinated UAT with 24 business testers over three cycles and 412 test cases, reaching a 96% first-time pass rate in the final cycle
  • Prepared the change impact assessment and training material for 300 branch staff ahead of go-live

Associate Business Analyst

Nilgiri Ridge Insurance, Bengaluru

Jul 2020 – Jul 2022

  • Gathered requirements for a KYC document upload feature and documented them as a business requirements document and functional specification
  • Analysed 14 months of claims rework data in SQL and Excel, showing that 40% of rework came from two missing mandatory fields
  • Supported UAT for a policy administration upgrade, logging and triaging 230 defects in Jira with the vendor
  • Produced the cost-benefit analysis for automating renewal reminders, which secured approval for the project

Operations Executive

Nilgiri Ridge Insurance, Bengaluru

Jun 2019 – Jun 2020

  • Processed about 60 policy endorsements a day and wrote the first standard operating procedures for the endorsements team
  • Proposed a checklist change that cut data-entry errors on endorsements by a quarter

Skills

Analysis: requirements elicitation, process mapping (BPMN), gap analysis, user stories, acceptance criteria, cost-benefit analysis

Delivery: Scrum, backlog refinement, UAT planning, traceability, change impact assessment

Tools: Jira, Confluence, Visio, Lucidchart, SQL, Excel, Figma (wireframes)

Domain: retail lending, KYC and onboarding, general insurance

Certifications

Certification of Capability in Business Analysis (CCBA)

International Institute of Business Analysis

2023

Education

Bachelor of Commerce

Southfield College of Commerce, Bengaluru

2016 – 2019

Open this example in the resume builder Start empty with this template

Why this resume works

  • The loan journey bullet names the stakeholders (credit, operations, compliance and IT), the technique (18 workshops) and the deliverable (140 signed-off user stories), which is the full shape of requirements work.
  • Process mapping is tied to a measured result: 9 of 31 manual handoffs removed and approval time down from five days to two. The notation, BPMN, is named for readers who search for it.
  • UAT is described with the figures a test manager would ask for: 24 testers, three cycles, 412 test cases and a first-time pass rate.
  • Traceability and acceptance criteria have a bullet of their own. These disciplines separate an analyst from a note-taker, and the link to regulatory requirements suits a bank.
  • The operations role at the foot of the experience section shows where his insurance knowledge comes from, and that he was improving processes before he held the analyst title.

What employers look for in this role

  • Elicit requirements through workshops, interviews, observation and document analysis
  • Map current and future processes and identify gaps, waste and risks
  • Write business requirements, functional specifications or user stories with clear acceptance criteria
  • Act as the link between business stakeholders and the development or vendor team during delivery
  • Plan and support user acceptance testing and manage defects to resolution
  • Assess the impact of change on people, processes and systems, and support training and rollout
  • Build business cases that set out options, costs and benefits

Skills to consider

List only the skills you can back up with an example. These are the ones that come up most for this kind of role.

Analysis techniques
Requirements elicitation, Process mapping (BPMN), Gap analysis, Use cases and user stories, Root cause analysis, Data analysis with SQL and Excel, Cost-benefit analysis
Documentation and modelling
Business requirements documents, Functional specifications, Acceptance criteria (Gherkin), Wireframes, Data flow and entity relationship diagrams, Traceability matrices
Delivery and change
Scrum and backlog refinement, UAT planning, Defect triage, Change impact assessment, Stakeholder management, Training and rollout support
Tools
Jira, Confluence, Visio or Lucidchart, Figma or Balsamiq, Power BI, Azure DevOps

More bullet points to adapt

Each of these follows the same pattern as the example: an action, what it was applied to, and what changed. Swap in your own facts and figures. The bullet builder assembles the pattern for you.

  • Facilitated a two-day process workshop with 14 stakeholders from three departments and issued an agreed to-be process map within the week
  • Reduced requirement-related defects found in UAT from 38 to 11 between two releases by adding worked examples to every acceptance criterion
  • Wrote the data migration mapping for 62 fields between the legacy and new policy systems, agreeing 17 data-quality rules with the business owner
  • Built the business case for automating invoice matching, estimating 1,400 staff hours saved a year, which the investment committee approved
  • Created wireframes for a branch dashboard and tested them with eight users before development began, removing two screens from scope
  • Maintained the stakeholder map and communication plan for a regulatory change affecting 11 teams, with every compliance deadline met

Words that recur in adverts

These terms appear often in adverts for this kind of role. Use the ones that are true of you, in sentences that show the skill in use, and check a specific advert with the keyword checker.

  • Requirements gathering
  • Elicitation
  • Process mapping
  • BPMN
  • User stories
  • Acceptance criteria
  • UAT
  • Gap analysis
  • As-is and to-be
  • Stakeholder workshops
  • Business case
  • Functional specification
  • Traceability
  • Change management

Which sections to include

Begin with a summary naming your domain (banking, insurance, retail, public sector) and the techniques you are strongest in. Experience follows and should show the whole analysis cycle across your bullets: elicitation, process mapping, specification, testing support and change. Put a grouped skills section next, with techniques first and tools second, since adverts for this role list both. A certification such as CCBA or a BCS diploma goes after skills, then education. If you moved into analysis from an operational job, keep it on the page in two bullets: that is where your knowledge of the business was earned.

Mistakes to avoid

  • Writing "gathered requirements" and nothing else. Say which technique you used, who the stakeholders were, what you produced and how many items, so the reader can see the size of the work.
  • Leaving out the result of the change. A business analyst is hired to improve something, so state what the process or system did better afterwards: time, errors, cost or compliance.
  • Listing documents as achievements. A requirements document or a process map is a means, so connect each one to a decision it supported or a defect it prevented.
  • Ignoring testing and rollout. Many adverts expect the analyst to support UAT, training and go-live, and a resume that stops at sign-off looks incomplete.
  • Describing your domain in general terms. Name the business area you know, such as lending, claims, billing or supply chain, because domain knowledge often decides between two analysts.

Questions and answers

Should a business analyst resume include technical skills such as SQL?

Yes, if you use them. SQL and Excel let you check data yourself instead of relying on others, and many adverts list them. Put them in a tools line and show one use in a bullet, such as analysing rework data. You do not need to present yourself as a developer.

How do I write bullets for requirements work that has no obvious number?

Count what you can: workshops run, stakeholders involved, stories or requirements written, test cases, defects, process steps removed, systems affected. Then add the effect on the project, such as fewer change requests or a faster sign-off. The bullet builder helps you join the action and its result.

Is a certification such as CBAP, CCBA or a BCS diploma necessary?

It depends on the employer and the country. Some adverts ask for one, particularly at consultancies and large organisations, while many place more value on domain experience. If you hold a certification, list it with the awarding body and year. If you do not, clear evidence of the techniques in your experience section does much of the same job.

What if my job title was not "business analyst" but I did the work?

Keep your real job title and let the bullets show the analysis: requirements you documented, processes you mapped, testing you coordinated. You can describe the nature of the work in your summary, for example "operations specialist with three years of requirements and process improvement work". Never change a title to one you did not hold.