Business analyst CVs tend to fail in the same way: they describe process without ever landing on the point of it. 'Gathered requirements', 'facilitated workshops', 'produced documentation' — all true, all activity, and none of it tells the reader what actually changed for the business. A BA is hired to turn problems into valuable change, so the CV has to prove you did exactly that, not just that you were present while it happened.
What employers want
Hiring managers for BA roles are looking for evidence that you turn business problems into working, valuable change. They want three things: proof you can define and shape the right solution, domain knowledge relevant to their sector, and credibility with stakeholders on both the business and technical sides. A CV that reads as a list of methods answers none of those directly. One that ties your analysis to real outcomes answers all three.
Lead with outcomes, not activities
Every requirements exercise you ran existed to achieve something. Say what it achieved. Instead of stopping at 'gathered requirements for a new system', carry the sentence through to the result: the cost saved, the time reduced, the process improved, or the system delivered and adopted. The analysis is the means; the outcome is what a hirer is scanning for. If a bullet describes only the activity, it is unfinished.
Show your domain and methods
BAs are rarely interchangeable across sectors. Someone who knows financial services regulation, healthcare pathways or retail operations brings context that shortens the ramp-up, so make your domain obvious. Alongside it, be clear about how you work: Agile, Waterfall or a hybrid, and where you sit in delivery — close to strategy and discovery, or embedded with a delivery team writing user stories sprint by sprint. This helps a reader place you quickly.
Evidence your stakeholder and communication work
Much of a BA's value is in bridging business and technical teams and holding a shared understanding together when priorities pull in different directions. Show it concretely: reconciling conflicting requirements across departments, translating business needs into something a development team could build, or keeping stakeholders aligned through a contentious change. These are the parts of the job that are hard to fake and that employers most want to see evidence of.
Tools and techniques, in proportion
Jira, Confluence, SQL, BPMN and process modelling, user stories and acceptance criteria all belong on a BA CV — but in proportion. A long tool-dump signals someone padding rather than someone who delivers. Match the tools and techniques to what the advert actually asks for, list them clearly, and let your outcomes do the persuading. A hirer cares far more that you defined the right change than that you documented it in a particular tool.
Quantify where you can
Numbers turn a claim into evidence, and BAs have more of them available than they think: process cycle times, error rates, headcount affected, teams involved, hours saved, adoption rates. Where an exact figure is commercially sensitive, use a percentage or a range instead — 'cut processing time by around 40%' is both safe and convincing. Be honest about your contribution rather than claiming sole credit for a whole programme.
Tailor to the role
'Business analyst' covers very different jobs. A change or transformation BA works on organisational and process change, often with senior stakeholders and a strategic remit. A systems or data BA sits closer to delivery, defining detailed requirements, data flows and system behaviour. Read the advert and bring forward the experience that matches. Sending the same CV to both leaves the reader guessing which kind of BA you actually are.
A worked example
Before: 'Gathered requirements for a new CRM.' After: 'Defined and prioritised requirements for a CRM rollout across 3 teams, cutting quote turnaround from 5 days to 1.' Same project, but the second version states the scope, your role and the result. The numbers here are illustrative, but the shape is what matters: activity, plus the change it produced.
Common mistakes to avoid
- Listing process ('gathered requirements', 'facilitated workshops') with no outcome attached
- Tool-dumping every platform you have touched instead of matching the advert
- Hiding your sector and domain knowledge when it is a real advantage
- Being vague about whether you are a change, systems or data BA
- Claiming sole credit for whole programmes rather than being clear on your contribution
- Leaving out numbers because exact figures are sensitive, when a range would work
Common questions
What should a business analyst CV focus on?
The business outcomes your analysis enabled, not the process you followed. Tie requirements, workshops and documentation to what changed as a result: cost saved, time reduced, a process improved or a system delivered. Show your domain, your delivery method and your stakeholder credibility, and tailor all of it to the specific BA role.
Do I need certifications like BCS or Agile on my BA CV?
They help, especially where an advert asks for them, and BCS, Agile or similar qualifications are worth listing clearly. But they support your CV rather than carry it. Evidence of delivered change and credible stakeholder work matters more than any certificate, so lead with outcomes and let the qualifications back them up.
How do I show impact if my work was behind the scenes?
Connect your analysis to the delivery it fed into. You may not have built the system, but your requirements shaped it, so state the result the change achieved and your role in enabling it. Use percentages or ranges where exact figures are sensitive, and be honest about contribution rather than claiming sole credit.