Frame your BA focus and domain in the summary
Open with a short summary that states your specialty—digital product BA, process improvement, ERP/CRM implementations, operations BA or regulatory change—and the industries you know, such as fintech, healthcare, retail or logistics. Mention agile or waterfall delivery contexts when that helps a reader place your working style.
Mirror posting language only when it matches work you have done. Claiming BPMN fluency, user-story ownership or UAT leadership without examples invites hard workshop questions. Point readers to the epics, process maps and release outcomes that prove the skills the job emphasizes. Leave deep SQL modeling and A/B experiment design for a data analyst CV unless the role truly blends both.
Write bullets that connect discovery work to delivery outcomes
Strong BA bullets name the problem, your facilitation or artifacts and the result. Include reduced rework, fewer escaped defects, cycle-time improvements, adoption of a new process or clearer acceptance criteria when they clarify impact. Prefer measured outcomes—stories clarified before sprint start, UAT defects cut, handoff time shortened—over vague claims that you are a “bridge between business and IT.”
The fictional examples below illustrate wording only. They are not Make.CV performance claims and should not be copied as your own. Replace every figure with results you can support with Jira history, workshop notes or release retrospectives. If metrics are confidential, use approved ranges or describe the control change without naming restricted systems.
Show methods and tools without confusing BA with data analytics
Group skills into readable categories such as elicitation and workshops, requirements and user stories, process mapping, UAT and change support, and collaboration tools. Prioritize methods named in the posting when you have genuine experience. A short accurate list of user stories, process maps, RACI, Confluence or Jira beats a long inventory of BI tools you barely used.
Tie important methods back to experience bullets. Saying you own requirements is more convincing when a bullet explains discovery sessions, acceptance criteria quality and what changed for delivery predictability. If you also write light SQL for validation, keep it secondary so readers do not mistake the CV for a data analyst profile.
Choose a clean layout and review the export
Use a readable template with standard headings so domains, methods and delivery outcomes stay easy to find. Keep dates consistent and leave room for quantified bullets. Browse Make.CV templates if you want to compare layouts before writing.
Build your CV in the free maker with live preview, then download a PDF with no watermark. Check that system names, methodology labels and acronym expansions wrap cleanly. Confirm the exported text remains selectable before you submit.
Frequently asked questions
How is a business analyst CV different from a data analyst CV?
Business analyst CVs emphasize requirements, process and stakeholder alignment that enable delivery. Data analyst CVs emphasize analysis, metrics and decision support from data. Overlap exists, but lead with the lens the job posting prioritizes.
Should I list every framework or certification?
No. Prioritize active certifications and methods you can demonstrate in a case interview. Show the most important ones through project bullets.
Do process maps and BRD samples belong on the CV itself?
Usually link a sanitized portfolio or offer samples on request. Keep the CV focused on outcomes and methods rather than attaching large artifacts.
How do I show impact when I do not own the final product metric?
Quantify BA-owned outcomes such as rework avoided, clearer acceptance criteria, faster UAT cycles or smoother handoffs. Credit product results carefully when many roles contributed.