Business Analyst CV Guide: What Recruiters Actually Look For in 2026
Write a business analyst CV that gets noticed — the skills, metrics, and framing that hiring managers look for, with before/after examples and common mistakes.
Business analysis is one of those roles where everyone claims they do it, but few people write a CV that proves it. The problem is that BA work is largely invisible in a job description — you sat in meetings, you wrote requirements, you facilitated workshops. None of that sounds impressive until you connect it to what actually changed because of it: the project that shipped on time, the process that cut manual work by 40%, the requirements document that prevented a six-figure rework.
Hiring managers for BA roles are looking for structured thinkers who can move between business stakeholders and technical teams without either group feeling patronised. Your CV needs to demonstrate that bridge-building ability, not just list the tools you know.
What Recruiters Scan For
1. Domain experience that matches the role. A BA CV for a financial services firm is read very differently from one for an NHS digital programme or a retail e-commerce team. Recruiters want to see that you understand the language, the regulatory context, and the type of stakeholder you would be working with. Generic CVs that could apply to any sector signal that you have not really engaged with the role.
2. Named methodologies. Agile, Scrum, Waterfall, SAFe, DSDM — whichever frameworks you have worked within, name them. If you have a BCS (ISEB) qualification, an IIBA CBAP, or a PRINCE2 certification, these should be visible early. Do not bury credentials under a section at the bottom.
3. Clear evidence of requirements work. Business requirements documents (BRDs), functional specifications, user stories, use cases, process maps — these are the tangible outputs of BA work. Mention them by name, with context. "Authored 80-page functional specification for a payment processing system migration" is stronger than "wrote requirements."
4. Stakeholder management at scale. How many stakeholders? What seniority? Across how many departments or geographies? A BA who has run workshops with C-suite executives across three business units is a different hire from someone who documented requirements passed down from a single PM. Show the scope.
5. Quantified process improvement. BAs are expected to make things more efficient. If you facilitated a process review that reduced a manual task from 4 hours to 20 minutes, that is an achievement worth putting in bold. If you helped scope a system migration that delivered £2M in annual cost savings, include it.
Key Skills to Highlight
Technical and analytical tools:
- SQL — even basic querying demonstrates data literacy that many BAs lack
- Excel / Google Sheets at an advanced level (pivot tables, VLOOKUP/XLOOKUP, data validation)
- Jira, Confluence, Azure DevOps for backlog management and documentation
- Process mapping tools: Visio, Lucidchart, BPMN notation
- Data visualisation: Tableau, Power BI, Looker
- Wireframing basics: Balsamiq, Figma — enough to sketch requirements visually
Methodologies worth naming explicitly:
- Agile/Scrum: Sprint planning, backlog refinement, retrospectives
- MoSCoW prioritisation, SWOT analysis, PESTLE, gap analysis
- Use case modelling, as-is / to-be process mapping
- UAT planning, test script creation, defect triage
The soft skills that matter (with proof):
- Eliciting requirements from non-technical stakeholders — name the workshops you ran
- Translating technical constraints for business owners — name the projects where this was critical
- Conflict resolution between competing stakeholder priorities — mention it if it happened
Strong vs Weak Bullets
The single biggest issue on BA CVs is task-listing. Here is what the difference looks like:
Weak: Gathered requirements from stakeholders for a new CRM system. Strong: Elicited and documented 120+ functional and non-functional requirements across 14 stakeholder groups for a Salesforce CRM implementation covering 350 users; requirements sign-off achieved in 6 weeks against an initial 12-week estimate.
Weak: Conducted process mapping workshops. Strong: Facilitated 8 as-is / to-be process mapping workshops with operations and finance teams, identifying 3 manual handoff points responsible for an estimated 15 hours of avoidable work per week; findings directly informed a £180K automation project brief.
Weak: Worked closely with developers to deliver a payments feature. Strong: Acted as primary BA on a PSD2-compliant open banking integration, translating regulatory requirements into 34 user stories with acceptance criteria reviewed by legal, compliance, and engineering; feature delivered within sprint plan with zero post-launch critical defects.
Common Mistakes That Cost You Interviews
1. No sector-specific vocabulary. A BA CV in financial services should reference things like COBS, GDPR data mapping, change management, or regulatory impact assessments. A BA CV in healthcare should mention NHS Digital standards, IG toolkit, clinical pathway analysis. Generic CVs feel like they were written by someone who Googled "what do BAs do."
2. Hiding analytical skills. Business Analyst is in the job title, but many BAs undersell their quantitative work. If you run SQL queries, build Excel models, or create dashboards in Power BI, these are differentiators — especially at companies moving toward more data-driven processes.
3. Using passive voice throughout. "Requirements were gathered," "workshops were facilitated," "a process was designed" — this makes it sound like things happened around you, not because of you. Every bullet should start with an active verb: Led, Authored, Defined, Facilitated, Delivered, Reduced, Mapped, Resolved.
4. Omitting the business outcome. BA work exists to serve a business outcome. Always trace the line from your contribution to the result. A requirements document that prevented a scope creep episode, a workshop that unblocked a stalled project, a data model that enabled a new reporting capability — outcomes are what justify the hire.
How to Tailor Your CV for Each Application
Read the job posting and identify the three or four phrases that appear most deliberately — these are the hiring manager's actual priorities. If they keep saying "digital transformation," use that phrase. If they mention "lean process improvement" twice, it is not accidental. Mirror their terminology.
Check the seniority signals too. A "Senior BA" role at a bank probably wants different language than a "Business Analyst" role at a scale-up. The bank wants methodology rigour, governance experience, and formal deliverables. The scale-up wants adaptability, speed, and comfort with ambiguity.
NextCV automates the hardest part of this: paste the job description and your profile gets reshaped to surface the most relevant experience in the language the employer actually used. For BA roles that vary considerably across sectors and company sizes, that tailoring is the difference between a generic application and one that reads like it was written specifically for that posting.
Closing Thoughts
The best BA CVs read like a brief from a structured thinker: clear, specific, outcome-focused, and easy to scan. You are in the business of clarity by profession. Apply the same rigour to your own career documents that you would apply to a requirements specification, and you will stand out from the majority of applicants who are still writing task lists dressed up as achievements.