CV example

Business analyst CV example

Business analysts sit between the business and the people who build solutions. This example shows a BA who proves it with process savings, clear requirements and projects that shipped because the analysis was right.

Below you'll find a full example CV (also called a résumé), summaries for different experience levels, the skills and keywords employers search for, stronger bullet points, and the interview questions to prepare for.

Example CV for a fictional business analyst, Tunde Bakare. People, companies and figures are made up. View full size

Business analyst CV summary examples

Your summary is the first thing a recruiter reads. Two or three sentences: who you are, your strongest evidence, and what you want next. Here is the example CV's summary, plus versions for other levels.

Example CV

Business analyst with 5 years in banking and insurance. I map processes, turn messy needs into clear requirements, and work with developers and testers until the solution does what the business needs.

Entry level

Graduate with a background in operations support who has documented processes and gathered requirements for two internal tools. Strong in Excel and SQL, and working towards the ECBA.

Senior

Senior business analyst with 10 years leading analysis on core banking and ERP programmes. Built the BA practice’s templates and standards and mentor a team of 6 analysts.

Skills to put on a business analyst CV

Hard skills

  • Requirements gathering and documentation
  • Process mapping (BPMN, flowcharts)
  • User stories and acceptance criteria
  • Gap and impact analysis
  • Data analysis with Excel or SQL
  • User acceptance testing (UAT)
  • Agile and Waterfall delivery

Soft skills

  • Asking good questions
  • Facilitating workshops
  • Clear writing
  • Managing conflicting stakeholder needs

Show soft skills through your bullet points rather than listing them on the CV itself.

Keywords recruiters and ATS look for

Many employers screen CVs with an applicant tracking system (ATS) that matches words from the job ad. These come up often in business analyst postings. Use the ones that are true for you, in the same wording as the job you're applying for. To compare your CV with a specific job ad, use the free CV keyword checker, or have Litjob tailor your CV to the job description for you.

  • business analyst
  • requirements gathering
  • business requirements
  • user stories
  • process improvement
  • process mapping
  • stakeholder management
  • UAT
  • gap analysis
  • SQL
  • agile
  • documentation

Bullet points: before and after

Strong bullet points say what you did, how big it was and what changed. Compare:

WeakGathered requirements from stakeholders.

StrongerRan 12 workshops with finance and operations to define requirements for a new billing system.

WeakImproved business processes.

StrongerRedesigned the supplier payment process, saving 20 staff hours a week.

WeakWrote documentation.

StrongerWrote 140 user stories with acceptance criteria that guided a 6-developer team through 8 sprints.

WeakDid testing.

StrongerLed UAT with 30 users, catching 2 critical issues that would have stopped go-live.

Only use numbers you can explain in an interview. An honest estimate (“about 30%”) is better than a made-up exact figure.

Tips for writing a business analyst CV

1

Quantify the process, before and after

Time, steps, errors or cost removed are the clearest proof of a BA’s value.

2

Name the systems and domain

Core banking, ERP, CRM or claims: domain knowledge is often the deciding factor in BA hiring.

3

Show the full cycle

Include discovery, requirements, testing and adoption, so employers see you stay until the solution works.

4

Mention technical depth honestly

SQL, data modelling or API basics help a lot, but only list what you could use in a test.

Common business analyst interview questions

Your CV gets you the interview, and interviewers will ask about what's on it. Prepare for these:

How do you handle stakeholders who want conflicting things?
Describe bringing them together, tying needs to business goals and agreeing priorities.
Walk me through how you would gather requirements for a new system.
Cover stakeholders, current-state analysis, workshops, documentation and sign-off.
What is the difference between a business and a functional requirement?
Business: what the organisation needs. Functional: what the system must do to support it.
Tell me about a time your analysis changed a project’s direction.
Choose a real example with a clear before and after.

Keep reading