A business analyst sits between the business and the delivery team, so a resume has to show both sides: you understood the problem, and the solution got built and used.
1. Name the artefacts you produced
Postings search for specific deliverables: business requirement documents, functional specifications, user stories, process maps, wireframes, test scenarios and traceability matrices. Name the ones you wrote or owned.
2. Show who you worked with
State the stakeholder groups (finance, operations, product, engineering, vendors) and the size of the project. It tells a screener how complex your environment was.
3. Include data skills
Many analyst roles expect SQL, Excel and a reporting tool such as Power BI or Tableau. Say what you used them for, for example validating data, building a report or measuring a change.
4. Close the loop with outcomes
After the requirement, what happened? Faster processing, fewer errors, a launched feature or a cost saving. If you supported UAT or training, say so. That is part of the result.
Weak: 'Gathered requirements and worked with stakeholders.' Stronger: 'Elicited requirements from several stakeholder groups, documented user stories in JIRA and supported UAT for a billing change.' Add your real scope and results.
5. Use delivery vocabulary accurately
Use Agile terms (backlog refinement, sprint planning, acceptance criteria) or Waterfall terms (sign-off, change request) according to how you really worked. Mixed or inflated terms are easy to spot in interviews.
Checklist
• Deliverables named. • Stakeholder groups and scale stated. • Data and reporting tools with their purpose. • Outcomes after the requirement. • Methodology terms that match your real work.