A business analyst CV should show how you understood a need, captured requirements, and supported a team through a change.
Important: These examples are teaching patterns, not a real candidate's employment history. Replace brackets with accurate details. Never add a credential, tool, result, or metric you cannot verify.
Role keywords to check against the actual vacancy
Requirements gathering
Process mapping
User stories and acceptance criteria
Data analysis
Stakeholder facilitation
These are prompts for comparison, not a list to paste blindly. Only include a skill when your experience supports it.
Professional summary structure
Business analyst with experience supporting [business process or product] through [requirements, process, or data work]. Collaborated with [teams] using [verified tools or methods].
Fill each bracket with your real background. Remove any phrase that does not describe you.
Weak vs stronger experience bullets
Too vague: Gathered requirements.
More specific: Documented [process or feature] requirements through [interviews, workshops, or review] and clarified acceptance criteria with [team].
Use responsibly: Use only research activities you actually performed.
Too vague: Improved processes.
More specific: Mapped [current process] and recorded [specific handoff or issue] for review with [owner].
Use responsibly: Do not claim savings or cycle-time reductions without evidence.
Too vague: Worked with stakeholders.
More specific: Prepared [document or decision log] to align [stakeholder groups] on [specific scope].
Use responsibly: Keep the stakeholder description accurate.
Checklist for this role
Include tools such as Jira, Visio, SQL, or spreadsheets only when used.
Show the artifacts you created: requirements, process maps, test cases.
Separate recommendations from implemented outcomes.