Business Analyst CV Example & Writing Guide

The full CV example

A fictional analyst at fictional employers. Everything numeric below is invented and has to be replaced with something you can defend.

Fictional example. Swap in your own name, city, email, phone and one profile link.

Why this CV works

Five things this example does that a typical BA CV does not:

• The requirements bullet includes the three that failed

  61 of 64 acceptance criteria passed first time, three did not, and the CV says why and what changed as a result. A BA who reports a perfect record is either new or editing. Naming the failure mode, regulatory wording taken from the wrong source, and the fix, wording signed by compliance before it reaches a story, is the most convincing thing on the page.

• Process numbers come with a unit and a cause

  21 minutes to 13, and the cause named as two handoffs that existed only to re-key data. "Improved operational efficiency" cannot be argued with, which sounds like a strength and is a weakness: an interviewer who cannot argue with a claim cannot be persuaded by it either.

• It shows analysis that changed a decision

  140 requirements traced to five objectives, 22 of them dropped by the steering group. Most BA CVs count artefacts produced. This one counts work removed, which is a harder number to get and a better one, because it proves the traceability matrix was used rather than filed.

• It names who the analyst stood between

  Underwriting and claims, in workshops, with a decision log. "Liaised with stakeholders" is the phrase that makes a BA CV interchangeable with any other BA CV. Two named functions with a recurring disagreement between them is a situation the reader recognises from their own organisation.

• A year on the phones is kept, in one line

  It earns its place because it explains why this analyst starts with the operational reality rather than the target operating model, and it is compressed to one bullet so that page one belongs to the analysis work. That is the right treatment for any early role: keep it if it explains a habit, shrink it either way.

Professional summary examples

Entry level

Operational experience is an advantage at entry level, not an apology. Name the process you know from the inside, because that is the thing a graduate competitor cannot claim.

Mid level

Mid-level wants one process result, one analytical result and one sentence of character. Three sentences is the ceiling before a reader starts skipping.

Senior

Senior BAs are hired to raise other analysts' output. Say what standard you own and what happened to the numbers after you owned it.

Experience bullet examples

Twelve bullets in weak and strong form. The strong versions are not better because they are longer; they are better because a reader can push back on them. Every figure here is invented for the example, so the exercise is to find the equivalent number in your own work.

Weak

Gathered requirements from stakeholders.

Stronger

Ran 11 workshops between underwriting and claims and turned them into 140 traced requirements, 22 of which the steering group then cut.

Why

"Gathered" describes collection. What a BA is paid for is the filtering, so put the number that was removed next to the number that was written.

Weak

Wrote user stories and acceptance criteria.

Stronger

Wrote 64 acceptance criteria for the new claims form; 61 passed UAT first time and the three failures changed how regulatory wording is sourced.

Why

First-time pass rate is the BA equivalent of a defect rate. It is the single most useful number this job produces.

Weak

Documented as-is and to-be processes.

Stronger

Mapped claims intake across three teams and found four handoffs that existed only to re-key data, two of which were removed.

Why

A map is a deliverable. A finding is a result. Lead with what the map showed.

Weak

Supported user acceptance testing.

Stronger

Wrote the UAT scripts for 12 business users and triaged 84 defects, of which 61 turned out to be training gaps rather than software faults.

Why

That split is the interesting part, and it is a fact only the person in the room could know.

Weak

Analysed data to support business decisions.

Stronger

Ran a two-week data quality review before migration and found 9,400 records with a null cover start date, moving the cutover by three weeks rather than breaking it.

Why

The best analytical bullets describe a disaster that did not happen. Name what the finding cost and what it saved.

Weak

Improved operational efficiency.

Stronger

Cut average claims intake handling from 21 minutes to 13 by removing two re-keying handoffs.

Why

Efficiency without a unit is a mood. Minutes per case, items per week, or percentage of volume.

Weak

Liaised between business and IT teams.

Stronger

Kept the decision log that stopped the underwriting and claims referral threshold argument restarting monthly, and got the final threshold signed by both heads.

Why

Liaison is not an outcome. A signed decision is.

Weak

Created reports and dashboards.

Stronger

Rebuilt the billing exception report so that it grouped by cause, which took the weekly exceptions queue from about 2,300 to 600 once the top three causes were fixed at source.

Why

The report is the mechanism; the queue is the outcome. Write both, in that order.

Weak

Ensured requirements were traceable.

Stronger

Built the matrix linking 140 requirements to five business objectives, which the steering group used to remove the 22 that traced to nothing.

Why

Traceability claims are unverifiable unless you say what the trace revealed.

Weak

Trained users on the new system.

Stronger

Wrote the process maps and training notes for 40 billing agents, which held post go-live support calls to 18 in the first week.

Why

Training is measured by what did not happen afterwards. The support call count is the proof.

Weak

Worked in an Agile delivery team.

Stronger

Refined ahead of three squads at a two-sprint lead time, which kept the average story at one day of work and cut mid-sprint clarification requests from 14 a sprint to 4.

Why

Every BA has worked in an Agile team. Only some can say what their lead time was and what it did to interruptions.

Weak

Identified process improvement opportunities.

Stronger

Traced a 1.2% meter estimate rate to two reading rounds that had never been re-scheduled after a route change, and had both corrected in a fortnight.

Why

"Identified opportunities" is the phrasing of someone who wrote a list. Say what was traced, to what, and whether anyone acted.

Skills that belong on this CV

Education and certifications

Business analysis is entered from everywhere: operations, finance, support, testing, and occasionally a business degree. The degree line matters less than the domain, so if you have insurance, banking, utilities or healthcare experience, make sure the domain is legible in the first third of page one. Keep education to degree, institution and years below experience from your second analyst role onwards, and use the note line only if the subject is the domain you analyse.

Certifications

• BCS International Diploma in Business Analysis - Widely recognised in the UK and Ireland and often named in adverts. Say Diploma or Foundation rather than leaving the level ambiguous.
• IIBA ECBA, CCBA or CBAP - The IIBA ladder maps to experience, so the level itself signals seniority. CBAP requires substantial logged hours and is worth the header rather than the footer.
• Agile Analysis certification or a Scrum qualification - Worth one line when you refine directly with a squad, because it signals you know where the BA stops and the product owner starts.

A certification gets you past a filter and no further. The interview will be about a requirement that turned out to be wrong, so choose the one you want to be asked about and make sure the CV mentions it.

How an ATS reads this CV

Appliora's ATS Checker runs 14 checks on your uploaded file and shows the text its parser extracted. These four matter most for analyst CVs.

• Bullet quality

  The heaviest content check: how many bullets carry a figure and how many begin with an action verb. Analyst CVs fail the figure half more often than most, because the writer treats numbers as the project manager's job. Handling times, defect counts, requirement counts and queue sizes are all yours.

• How it reads

  Writing is the deliverable in this role, so the check matters more here than on a CV where it is incidental. It looks at sentence length, repetition and passive constructions. A BA CV written entirely in the passive voice contradicts its own claim to write clear requirements, and a reader who reviews documents for a living will notice before the parser does.

• Concrete skills

  The check wants recognisable skills rather than fragments. "BPMN", "UAT" and "RTM" are ordinary in an analysis team and opaque outside it. Write the phrase in full once, in the skills block, and abbreviate freely inside the bullets where the context carries it.

• Recognised sections

  The parser looks for conventional headings, and BAs like to add a "Domains" or "Projects" block near the top. That block is genuinely useful to a human, so keep it, but put it after a standard Experience heading rather than in place of one.

Templates that suit this role

• ATS Structured

  Single column and standard headings, which is what insurers, banks and public sector portals handle most reliably. Leaves room for the long bullets this role needs.

• ATS Clean

  A quieter version of the same discipline, with more white space, for when the CV runs to two full pages and needs to stay readable.

• Two Column Pro

  Puts domains, tools and certifications in a side column where a reader scanning for BCS or CBAP finds them instantly, while experience keeps the full width.

Related roles

• Product Owner
• Product Manager
• Project Manager
• Data Scientist