How to write a Business Analyst CV
Focus on analysis results, produced deliverables and used tools/methodologies
Headline and summary
Start with a clear title and a summary including context, method and impact.
- Title: “Business Analyst” (add industry: “Finance/IT” if relevant)
- Summary: 2-3 sentences with results (efficiency, time reduction, adoption) and methodologies (Scrum/Waterfall)
- Include 3-5 keywords: BPMN, requirements, user stories, UAT, stakeholder management
Detailed experience
In bullet points use: context → action → output → result.
- Context: project type (CRM, processes, compliance) and stakeholders involved
- Output: process maps, BRD/FRD, user stories, acceptance criteria
- Result: KPIs (efficiency +30%, error reduction, cycle time, adoption)
ATS keywords
Include recurring terms from job postings that reflect your real work.
- “BPMN”, “BRD”, “FRD”, “Requirements Gathering”
- “User Stories”, “Acceptance Criteria”, “Backlog”
- “UAT”, “Gap Analysis”, “Stakeholder Management”
- “Scrum”, “Waterfall”, “JIRA”, “Confluence”, “Power BI”
Professional summary example
2-3 clear sentences: role, context, impact
Example
Business Analyst with 6+ years of experience in IT and finance environments, specialized in requirements gathering, BPMN and stakeholder management. Used to working with Scrum and Waterfall, supporting UAT and go-live phases and contributing to improved process efficiency and solution quality.
Work experience
Describe context, role and impact with concrete examples
Entry format
Period, role, company + activities and measurable results.
- Project type (CRM, workflows, process improvement, compliance)
- Stakeholders and teams involved (business, IT, QA, operations)
- Produced deliverables (BPMN, user stories, BRD/FRD, UAT)
- Results (efficiency, error reduction, time-to-market)
Success metrics
Use numbers and indicators consistent with BA work.
- Process efficiency: +30% (e.g. reduced cycle time or manual activities)
- Stakeholders involved: 10+ (workshops and alignment sessions)
- Rework or defect reduction thanks to clear requirements and acceptance criteria
- Improved adoption through training and change management
Analysis projects
Show case studies, methodology and deliverables
Project selection
Present 2-3 analyses with tools and results.
- Objectives and context (problem to solve)
- Methodology (workshops, BPMN, gap analysis, user stories)
- Outputs (process maps, backlogs, KPI dashboards)
- Results and impact (efficiency, quality, adoption)
Education and certifications
Academic degrees and recognized BA certifications
Academic qualifications
Degrees and institutions with dates; if useful, highlight relevant theses or courses (processes, information systems, data).
BA certifications
Certifications increase credibility and ATS score when aligned with the profile.
- CBAP
- PMI-PBA
- Courses on BPMN, Agile, data analysis (if any)
Technical skills and soft skills
Balance analytical capabilities and stakeholder communication
Hard skills
Methodologies and tools for analysis and requirements delivery.
- BPMN/UML and requirements modeling
- User stories and acceptance criteria
- UAT and release support
- Tools: JIRA/Confluence, Visio/Bizagi, Power BI, basic SQL
Soft skills
Cross-functional skills that determine BA effectiveness.
- Clear written and verbal communication
- Workshop facilitation and conflict management
- Problem solving and critical thinking
- Priority management and stakeholder negotiation
Languages
CEFR (A1-C2)
Formatting
Indicate language and level; if useful specify usage (documentation in English, meetings with international stakeholders).
Certifications and methodologies
List certifications and frameworks actually used
Examples
Common BA/PM certifications and methodologies.
- CBAP (IIBA) or equivalent
- PMI-PBA (PMI)
- Scrum (user stories, backlog, refinement)
- Waterfall (BRD/FRD, change control, formal UAT)
