A business analyst résumé example, and the process it removed
One complete business analyst résumé, written out in full. The person is invented. The reading and the score come from the product itself.
— requirements are not a deliverable. the change is.

Business analysis produces a great deal of paper, and a résumé that lists the paper tells a reader nothing. This example is written out in full so you can read what the outcome version looks like, then put through the tools here so you can see what a parser takes from it. The candidate is invented. Idris Ravenscourt does not exist, neither employer exists, and every figure was chosen to demonstrate a shape.
The example, in full
An invented person. Not a real document, and not yours.
Idris Ravenscourt
Business Analyst
Edinburgh, United Kingdom · [email protected] · +44 131 496 0283
Summary
Business analyst with seven years in insurance and utilities. Works on requirements, process and the difference between what was asked for and what was meant.
Experience
Senior Business Analyst · Trellick Mutual, Edinburgh · 2021 to present
- Wrote the requirements for a claims platform used by 340 staff across 4 teams.
- Cut claim handling time from 11 days to 6 by redesigning 3 process steps.
- Ran 28 workshops with 90 participants and turned the output into one prioritised backlog.
- Reduced rework on delivered stories by 41% by adding acceptance criteria at refinement.
Business Analyst · Kelso Water Services, Stirling · 2018 to 2021
- Mapped 60 process steps across 5 departments and removed 14 of them.
- Specified the billing changes affecting 220 000 customer accounts.
- Trained 9 colleagues on process mapping and handed the practice over.
Education
BA Business Management · Corstorphine Business School, Edinburgh · 2014 to 2017
Skills
requirements elicitation, process mapping, user stories, acceptance criteria, stakeholder workshops, data analysis, SQL, Visio, Jira, change management
Certifications
BCS International Diploma in Business Analysis · 2020
The analyst's result is somebody else's saved time
Claim handling from eleven days to six after three process steps were redesigned. Fourteen of sixty process steps removed. Rework on delivered stories down 41%. None of those is a document, and all of them came out of documents.
That is the argument for writing an analyst's page this way. The requirements, the maps and the stories are the method. A hiring manager is buying the effect, and the effect is always somebody else's time, error rate or cost.
Scope belongs in the first line of each role
Three hundred and forty staff across four teams. Two hundred and twenty thousand customer accounts. Five departments. Those numbers sit early in each block so the rest of the block can be read at the right scale.
The handover line is the quiet one: nine colleagues trained on process mapping, and the practice handed over. An analyst who leaves a capability behind is a different proposition from one who leaves a folder behind.
What the reading found
The door on this page hands the document above to the résumé builder as plain text, through the same import an uploaded file goes through, and the review shows every field beside the line it came from. Here the completeness pass found four readable sections, 105 words of experience evidence and ten distinct skills, with the diploma stored as a certification and its year kept.
No language model is involved. The readers are deterministic functions with their own rules, every string they emit is checked in code to be a span of the document, and a field that fails that check is dropped and counted.
What the checker scored it
Ninety-seven out of 100, with one improvement remaining worth 8 points. The arithmetic is 100 × 30% + 100 × 30% + 92 × 40% = 97, explained in the article on the score. Seven action-led lines, six of them measurable, seven lines of depth, and 181 readable words against a band opening at 250.
Six measurable lines out of seven is a very high ratio for this profession, and it is what makes a short page score well. The ATS checker shows which lines it counted on your own document, so you can see whether your ratio is the problem or your length is.
What this example leaves off
No list of documentation templates, no framework badges and no description of a methodology. A delivery manager knows what a business analyst produces; they are hiring to find out what happened afterwards.
Named systems the organisation happened to run are left off as well, unless the posting asks for them. A claims platform is a claims platform; the useful part of that line is the 340 staff who had to use it and the six days that came off the handling time.
What to change for your own
Change the domain. Insurance, utilities, retail banking, health and public sector analysis all use this shape with different regulators and different nouns. Then convert your deliverables into effects: days saved, steps removed, defects avoided, accounts affected.
Keep the qualification with its year. Keep one handover line. The guide on experience bullets covers the construction, the design gallery holds 37 layouts, and the financial analyst example, the operations manager example and the project manager example sit beside this one.
Write yours beside it
Opens the builder with Idris's example loaded, saved as its own entry in the Placard design. Replace every line with your own. Free, no account.
Use this exampleCheck a résumé insteadQuestions
- Is Idris Ravenscourt a real person
- No. He is invented for this page, and so are Trellick Mutual and Kelso Water Services. The figures show a shape and describe nobody's career.
- Should a business analyst list documents produced
- Only where the document changed something. Twenty-eight workshops with 90 participants turned into one prioritised backlog is a deliverable with an outcome. A count of specifications written is a count of files.
- What did the checker score it
- 97 out of 100, with one improvement remaining worth 8 points. The document has 181 readable words, and the volume rule's top band opens at 250.
- Is removing process steps a good line
- It is the best line on the page. Fourteen steps removed from sixty is a result somebody had to defend in a meeting, and it is more convincing than any adjective about efficiency.
- Do I need a methodology section
- No. Name the qualification with its year and let the lines show how you work. Rework falling 41% after acceptance criteria moved to refinement says more about method than a framework list.
- Which design is this rendered in
- Placard, one of the 21 ATS-safe layouts out of 37. It gives the role headings weight, which helps a page where two roles carry everything.
Conxfolio is a free set of four career tools: a résumé builder with 37 rendered layouts, an ATS résumé checker that prints its own arithmetic, a cover letter builder that traces every proof paragraph back to the line it came from, and a portfolio builder with 20 authored designs. There is no account to create, nothing is held back for a paid plan, and no language model is used anywhere in the product, so the readers, the score and the letter are deterministic code you can check.