Business analyst resume tips
A business analyst resume should name a process you studied and the requirement or the decision that came out of it. The title is used for very different jobs, from writing software requirements to building a report. Say which one you did.
Cover letter for a business analyst
What to put first
State the domain: insurance operations, a clinic workflow, a retail process, a public program. Then the artifact: a requirements document, a process map, a report, a set of acceptance checks. Put the artifact their posting resembles first.
The artifact
Name the document and who signed off. A process map nobody used is weaker than a short requirement a team built from. Say which you had.
Where you sat
Between a department and a software team is a different job from inside a finance team building a spreadsheet. Write the seat you had.
Questions, not just workshops
Mention how you learned the process: sitting with the people who do it, reading the current procedure, or testing a change. Workshops alone are a calendar, not an analysis.
An example line
Adapt this only where it is true for you. It is a shape for a bullet, not a claim that a particular person did this work.
Wrote the requirement for a claims intake change after sitting with the adjusters, including the fields they refused to drop, and handed it to the team that configured the system.
What to leave off
Leave off a list of diagram styles, tools you have not used to produce a requirement, and project outcomes that belonged to the delivery team. Leave off a domain you only interviewed in once.
Questions
- Is this the same resume as a data analyst?
- Not if your work was requirements rather than analysis of a dataset. Use the artifact you produced. Do not blend the titles because postings sometimes do.
- Should I include a sample requirement?
- Only if it is not confidential and they asked, or the form invites an attachment. Describe it either way.