Examples & writing guide
Business analyst CV example and writing guide
Updated 27 July 2026
A good business analyst CV makes the evidence easy to find: the problem you examined, the people you worked with and the change that followed. This guide shows how to shape that evidence for applications at different career stages, including a graduate business analyst CV or a business analyst CV with no direct experience.
Examples by experience level
Junior Business Analyst
TemplateNavy Atlas4 / 5
Why this works
This entry-level business analyst CV uses an internship, a university project and transferable service experience to show practical analysis, stakeholder and delivery skills without overstating seniority.
Continue writing your CVBusiness Analyst
TemplateAshford1 / 5
Why this works
This mid-level business analyst CV connects requirements work, process analysis and stakeholder engagement to specific, believable delivery outcomes.
Continue writing your CVSenior Business Analyst
TemplateGrey Frame5 / 5
Why this works
This example shows leadership, delivery scale and measurable improvements while keeping every achievement tied to a specific business problem.
Continue writing your CVJunior vs senior: what changes
| Aspect | Junior | Senior |
|---|---|---|
| Personal statement | Leads with transferable analysis, project work and the type of junior business analyst role sought. It stays specific about the evidence available rather than claiming broad expertise. | Leads with the scale of change led, stakeholder breadth and measurable delivery outcomes. It identifies the business settings in which the candidate has the strongest record. |
| Requirements work | Shows accurate capture, clarification and updating of requirements on a defined project, with evidence of supervision or collaboration where relevant. | Shows ownership of requirements across the delivery lifecycle, including prioritisation, traceability, conflict resolution and control across several workstreams. |
| Business investigation | Uses a contained example, such as reviewing one customer journey or mapping a departmental process, and explains the finding and resulting action. | Shows how investigation shaped investment choices, operating models or a programme of business change, with scale and results made clear. |
| Stakeholder evidence | Demonstrates preparation, listening and follow-up through interviews, workshops or project meetings with a manageable stakeholder group. | Demonstrates facilitation across competing groups, constructive challenge to senior decision makers and agreement on priorities or scope. |
| Testing and delivery | Shows practical support for test preparation, defect recording, acceptance activity or requirement clarification during delivery. | Shows how acceptance was governed, how requirement coverage was assessed and how delivery risks or gaps were resolved before release. |
| Metrics and scope | Uses defensible figures such as the number of interviews, requirements, process steps, test cases or hours saved on a small project. | Adds programme value, user or site coverage, team size, adoption, cycle-time change, avoided cost or other measures appropriate to the work. |
How to write a business analyst CV
Use a reverse-chronological format, beginning with your most recent role. Two pages usually give you enough room to show relevant evidence without burying the strongest points. Put your contact details first, followed by a tailored personal statement, skills, employment, education and relevant training or projects.
| Section | What to include |
|---|---|
| Personal statement | Target role, relevant experience and one or two credible outcomes |
| Experience | Achievements that connect analysis to a decision, delivery result or service improvement |
| Skills | Methods and tools you have genuinely used, backed by evidence elsewhere in the CV |
| Education | Degree, training and relevant project work, especially when experience is limited |
| Extras | Selected projects, volunteering or professional development that strengthens your case |
Tailor the wording to the vacancy. A junior business analyst CV can draw on university projects, placements, customer-facing work or operational roles, while an experienced applicant should give more space to project scale, stakeholder complexity and measurable outcomes. Keep job descriptions brief and use the space for specific achievements. List technical and interpersonal abilities in a compact skills section, but do not rely on keywords alone; your employment bullets should show where you applied them.
Personal statement examples
Business analyst with four years' experience supporting digital and operational change across customer service and finance teams. Skilled in requirements gathering, process mapping, stakeholder workshops and acceptance testing, with recent work helping cut case-handling time by 18% across a 45-person operation. Comfortable turning competing user needs into clear requirements and traceable acceptance criteria.
Hard-working business analyst looking for a new challenge in a successful company. I am a good communicator, work well alone or in a team and have excellent problem-solving skills. I can do many business analysis tasks and learn quickly.
Writing your experience
A useful experience bullet has three parts: what you did, the scope of the work and what changed. Start with a precise action, explain the method or setting, then finish with a result the reader can understand. For example: "Mapped the customer onboarding process across five teams, identified 11 duplicated checks and helped reduce average completion time by 16%." The number gives scale, but the causal wording stays honest: "helped reduce" is better than claiming sole credit for a team result.
Business Analysts analyse, document and manage requirements through the delivery lifecycle. They also investigate business situations, including problems and opportunities for improvement. Your bullets should therefore connect analysis to delivery, rather than reading like a list of meetings attended. Where relevant, show how you examined processes, clarified information needs, documented requirements or supported testing against agreed requirements.
| Before | After |
|---|---|
| Responsible for stakeholder meetings | Led eight discovery interviews across operations and finance, resolving six conflicting requirements before development began |
| Helped improve a reporting process | Analysed a weekly reporting workflow, removed four manual hand-offs and cut preparation time from six hours to three |
| Wrote requirements and did testing | Documented 32 requirements with acceptance criteria and supported 24 test scenarios, with 22 passing on the first cycle |
The stronger versions show ownership without exaggerating it. They also name the unit of work: interviews, requirements, hand-offs, scenarios, teams or hours. If a result was qualitative, state the observable outcome, such as approval at a governance meeting or removal of a disputed requirement, then add a defensible count for scope.
Vary your verbs according to the work. Useful choices include analysed, investigated, mapped, elicited, documented, prioritised, validated, facilitated, reconciled, traced, tested and presented. Avoid repeating "supported" throughout the page, though it is accurate when you assisted rather than led. For an entry level business analyst CV, evidence can come from coursework, placements, volunteering or another job: analysing customer complaints, improving a rota process or documenting a student project can all demonstrate the pattern. Name the context plainly and do not inflate it into commercial experience. If your evidence centres on advising clients rather than delivery ownership, the consultant CV guide may be a closer fit.
Keep each bullet focused on one result. If a bullet contains several unrelated duties, split it or remove the weaker material. Four strong achievements under a recent role are more persuasive than ten routine tasks.
Key skills & ATS keywords
Hard skills
Soft skills
ATS keywords
Education & certifications
Place education after experience unless you are a recent graduate or changing career and your academic work is the stronger evidence. Give the qualification, subject, institution and dates. Add one or two relevant modules or projects only when they support the vacancy. A graduate business analyst CV might describe a project through its output, such as a mapped process, documented requirements or tested prototype, rather than listing every module completed.
Education, certifications, relevant projects and training should be clearly shown on a Business Analyst CV. Keep them in separate, plainly labelled entries so a recruiter can distinguish a completed qualification from a short course or project. If a course is still under way, state the expected completion date. Do not imply that attendance equals certification.
The supplied evidence does not establish a universal degree, school-level qualification, licence or professional route for Business Analysts. Match the vacancy's wording and present only qualifications you hold. Where an advert asks for a role-specific qualification, copy its exact title only after checking your own certificate or record.
BCS Business Analyst certification is preferred for one specified Technology Business Analyst role at Southwark Council. That is a role-specific preference, not a general requirement for every Business Analyst vacancy. Include it only if you genuinely hold that exact credential and the application would benefit from it; record the credential name, completion date and any other verifiable details available to you.
For applicants with no direct experience, a concise projects subsection can bridge the gap. State the business question, your method, the people or information involved and the result. Keep academic and simulated work clearly labelled rather than presenting it as paid employment.
Common mistakes to avoid
AvoidListing duties without showing what changed. A line such as "documented requirements and attended workshops" tells the reader little about the size of the work or its outcome.
InsteadWrite each bullet around an action, its scope and a result. For example: "Documented 46 prioritised requirements for a service redesign, cutting clarification queries during delivery by 28%." Use only figures you can support.
AvoidUsing one generic business analyst CV for every vacancy.
InsteadTailor the personal statement, skills and first few experience bullets to the work described in the advert. Give the most space to matching evidence, whether that is requirements work, process analysis, workshops, data needs or testing.
AvoidTreating requirements as documents produced once, rather than work managed through delivery.
InsteadShow how you elicited, clarified, prioritised, traced and updated requirements. Mention the delivery stages you supported and the effect your work had on decisions, rework or acceptance.
AvoidNaming techniques without proving that they were used well.
InsteadConnect each technique to a business question and outcome. Instead of listing "workshops, interviews and process maps", explain who took part, what you uncovered and what the team did differently afterwards.
AvoidOverloading the skills section with broad terms such as communication, Microsoft Office and teamwork.
InsteadUse a focused mix of analysis methods and people skills, then prove the strongest ones in the experience section. Terms such as requirements elicitation or acceptance testing should appear only when they match your actual work.
AvoidHiding useful evidence because the candidate has no formal business analyst job title.
InsteadFor an entry level business analyst CV, draw on university projects, placements, operations work or volunteering. Describe genuine examples of investigating a problem, gathering user needs, analysing a process or supporting a change.
Frequently asked questions
Two pages is a sensible target for most candidates. A graduate business analyst CV may fit on one page when the evidence is still limited, while an experienced candidate should keep two pages by selecting the work most relevant to the vacancy.
Use evidence from study, placements, operations roles or volunteering where you investigated a problem, gathered needs, analysed information or improved a process. State the situation, what you did and the outcome; do not relabel unrelated work or invent business analyst responsibilities.
Mirror the vacancy's genuine priorities in your personal statement, skills and strongest project or experience bullets. If the role focuses on requirements, workshops or testing, bring your matching evidence forward and remove low-value detail that does not support the application.
No. Under British CV conventions, use the space for evidence of skills, achievements, education and relevant projects instead; do not include a date of birth either.
Do not assume that every vacancy expects one. Read the advert carefully, list any role-specific qualification you genuinely hold with its exact title, and give more space to relevant skills, experience, projects and training.
Translate existing work into specific evidence without changing the facts. Examples might include investigating service problems, interviewing users, mapping a process, documenting needs or supporting acceptance activity; add scale and outcomes where you have records to support them.
From example to application
Turn this business analyst example into a CV that sounds like you.
Keep the structure that works. Tailor the details around your experience, strengths, and the role you want.