TAILOR.

How to Write a Business Analyst CV That Gets Interviews (UK)

A business analyst CV lives or dies on describing the BA role abstractly rather than naming what was built, who used it and what it changed. Most business analyst applications never reach a human: the ATS filters them on missing keywords, and recruiters bin the rest in seconds. Here's how to tailor a Business Analyst CV to the specific job ad in front of you.

Score your business analyst CV for free, in 30 seconds.

Against the ATS, the recruiter and the hiring manager. No credit card needed.

Run your free CV Health Check →

What a Business Analyst CV needs to pass the ATS

Applicant Tracking Systems screen business analyst CVs on exact-match keywords. Stuffing backfires (the recruiter still has to read it), but missing the obvious terms gets you binned before anyone sees the document. The keywords most business analyst job ads scan for in financial services, retail, public sector and large enterprise transformation programmes:

  • requirements gathering
  • stakeholder workshops
  • user stories
  • BPMN
  • JIRA
  • Confluence
  • gap analysis
  • UAT
  • agile
  • BABOK

Hand-curated for this role, not auto-generated. Use the exact words from the specific job ad you're applying to, that's what the ATS is scanning for.

What recruiters look for in a Business Analyst CV

Past the ATS, a recruiter gets seven seconds with your CV before deciding whether to read further. The top third (the title, professional summary and key competencies) has to answer their screening questions instantly. For a Business Analyst, that means:

  • The domain you've analysed (banking, retail, logistics). Recruiters bin generic BAs immediately
  • Size of the change you've shaped: number of users affected, systems migrated, processes redesigned
  • Methodology fluency: agile vs waterfall, BABOK, BPMN, the tooling you've actually used

Before and after: one Business Analyst bullet

Weak

Gathered requirements from stakeholders and documented user stories for the development team.

Strong

Captured and prioritised 140+ user stories across 4 quarterly releases for a UK retail bank's mobile app, working with 7 product owners and 3 dev squads to ship a new mortgage application flow used by 28,000 customers in its first month.

The weak version is BA boilerplate that every BA writes. The strong version names the domain (retail banking), the scale (140+ stories, 4 releases, 7 POs), the deliverable (mortgage flow) and the user impact (28k customers). All of that survives an interview because it's specific and falsifiable.

See what TAILOR would change in yours →

Tailor your Business Analyst CV in 30 seconds

Paste your CV and a business analyst job ad. TAILOR scores it against the ATS, the recruiter and the hiring manager, then tells you exactly what to fix.

Absolutely free. No credit card needed. No watermark.

Run your free CV Health Check →

Business Analyst CV FAQ

Should my Business Analyst CV emphasise technical or business skills?

Both, weighted to whichever the JD names first. Pure business BAs lose to technical BAs in product, fintech or data-heavy roles; pure technical BAs lose to business BAs in transformation, change or regulatory roles. Read the JD twice and lead with what it leads with.

Do BABOK or CBAP certifications matter on a UK BA CV?

Less than in the US, but they help. UK recruiters value them and rarely require them. If you have them, list them in education or certifications. If you don't, lean the top third on the domains and deliverables you've actually owned. They signal capability more reliably than any certification does.

How do I show BA work that ended up scrapped or paused?

Name it honestly with the lesson. 'Led discovery for an order-management replatform; recommended halt after the 4-week analysis surfaced unviable migration costs, saving £1.4m in further committed spend.' A killed project, well analysed, is interview-credible. Better than glossing over a six-month gap.

Related