Skip to content
JL JobLabs

CV Example · Business & Ops · UK 2026

Business Analyst CV Example UK

Business analyst CVs in the UK suffer from the same problem PM CVs do: too many verbs, not enough decisions. After 12 years placing BAs into UK financial services, insurance, public sector and SaaS, the strong ones in 2026 read more like product or change CVs. They name the project, the stakeholders, the analysis you ran, the recommendation you made, and what changed because of it. Hiring managers don't want 'gathered requirements' for the seventh bullet; they want the requirement you uncovered that the team had missed for two quarters. BAs sit between the business and delivery, and the CV needs to show you can hold that ground.

Alex By Alex · 12-year UK recruiter · Updated April 2026

Example header

Rebecca Hall · Senior Business Analyst · 8 years · London / Hybrid


Personal statement / Professional summary

Senior business analyst with eight years working across UK insurance and asset-management change programmes. Comfortable on regulatory, technology and operating-model projects, with strong process-mapping, requirement-elicitation and stakeholder-facilitation skills. Last role: lead BA on the policy administration platform replacement for a UK insurer, delivering the requirements artefact accepted on first review by the vendor and reducing in-flight scope changes by 64% versus the prior comparable programme.

Bullet point examples

Strong bullets follow the same shape: action verb, specific scope, quantified outcome. Use these as patterns, not as copy-paste templates — the numbers must be your own.

Lead BA, policy administration platform replacement

  • Owned business analysis for a £4.8m platform replacement across 6 product lines, delivering the requirements artefact accepted on first review by the vendor.
  • Reduced in-flight scope changes by 64% versus the prior comparable programme through a structured requirement-prioritisation workshop and written acceptance criteria for every story.
  • Facilitated 22 cross-functional workshops with underwriting, claims, finance and IT, producing a single end-to-end process map adopted as the change baseline.

Stakeholder elicitation and facilitation

  • Ran the stakeholder analysis across 4 business areas and 30+ named contacts, producing the engagement plan now used as the template for other in-flight programmes.
  • Resolved a long-running conflict between underwriting and claims on policy-amendment treatment by walking both teams through a shared process map; saved an estimated 4 weeks of rework.

Process and data analysis

  • Mapped 14 end-to-end business processes in BPMN 2.0, identifying 9 automation candidates that informed the build backlog and 3 manual processes that were retired entirely.
  • Wrote 220 user stories with explicit acceptance criteria across 4 epics, with a measured 91% acceptance rate at first sprint review.

Regulatory and audit work

  • Co-authored the impact assessment for the FCA Consumer Duty changes across the policy and claims journeys, including evidence pack accepted in internal audit's pre-deadline review.
  • Maintained the requirements traceability matrix from regulation through to test cases, with sign-off from the head of compliance and the test manager.

Earlier role: BA at consultancy

  • Delivered business analysis on 4 client engagements across UK retail banking, including a current-state operating-model review for a top-5 lender.
  • Built the consultancy's standard process-mapping template, adopted across 12 active engagements.

Skills section — what to list

Mirror the skills exactly as they appear in target job ads. The ATS reads this section literally — synonyms hurt match scores.

Requirements elicitationBPMN 2.0 process mappingUser story writing and acceptance criteriaStakeholder analysisWorkshop facilitationGap analysisCurrent-state and target-state operating modelsUse-case and scenario analysisSQL (intermediate)Excel (advanced)Jira and ConfluenceVisio / LucidchartAgile and waterfall deliveryRegulatory change (FCA, PRA awareness)Test-case authoring and UAT support

Business Analyst-specific CV mistakes that get you binned

  • × Endless 'gathered, documented, supported' verbs without naming the analysis or the decision. UK hiring managers read those CVs as junior regardless of title.
  • × No data fluency on the CV. Mid-to-senior BAs in 2026 are expected to be comfortable in SQL or at least Excel pivot tables; saying 'analytical' isn't enough.
  • × Listing methodologies (Agile, Waterfall, Lean, Six Sigma, BABOK) without naming a project where you actually used them.
  • × Hiding the business outcome. 'Documented requirements' is half a bullet; 'documented requirements that informed a £4m vendor decision' is the full one.
  • × Treating BA work as administrative. Strong UK BA CVs in 2026 show you actively shaped decisions, not just recorded other people's.

Common questions

How is a business analyst CV different from a project manager CV?
BAs analyse and shape the work; PMs deliver it. On a CV, that means BA bullets lead with analysis, requirement and recommendation; PM bullets lead with delivery, budget and timeline. Many UK candidates blur the two because they've done both, especially in smaller programmes where one person wears both hats. If that's you, pick the role you're applying to and re-frame the bullets accordingly. Don't try to be both at once on a single CV; hiring managers will read it as confused and assume you're stronger in neither.
Do I need certifications like BCS or CBAP for UK BA roles?
Helpful but not required. The BCS International Diploma in Business Analysis is the most commonly recognised UK qualification, and CBAP carries weight in larger consultancies and global financial services. At junior and mid-level the qualifications help clear ATS filters; at senior level your delivery track record matters more. If you don't yet have one and are mid-career, the BCS Foundation is the most accessible starting point. List any certifications in a single line at the bottom of the CV; they're a tie-breaker, not a headline.
How important is SQL for a business analyst CV in 2026?
Increasingly expected for mid-level and above, particularly in tech, SaaS and any data-heavy financial services BA role. You don't need to be an analyst-grade SQL writer; you need to be able to pull a basic dataset and validate a number without asking the data team. If your day-to-day is requirements work and you don't touch SQL, learn enough to do basic SELECT, JOIN and GROUP BY queries and add it honestly to the skills section as 'intermediate'. Pure Excel-only BA CVs are increasingly filtered out for senior roles.