Jordan Ellis
jordan.ellis@email.com · (555) 014-2290 · Columbus, OH · linkedin.com/in/jordanellis
Summary
Business analyst with 5 years of experience turning business needs into clear requirements and better processes. Led requirements for a claims system that cut processing time 35%.
Experience
Business Analyst 2022 – Present
- Gathered and documented requirements for a claims platform used by 400 staff.
- Mapped current processes and found changes that cut claim processing time 35%.
- Wrote 120+ user stories with acceptance criteria for two agile teams.
Business Analyst 2019 – 2022
- Ran user acceptance testing with 30 business users before go-live.
- Built SQL reports that replaced manual tracking spreadsheets.
- Facilitated workshops with stakeholders from operations, IT and finance.
Skills
Requirements gathering · Process mapping · User stories · UAT · SQL · Jira · Confluence · Visio · Stakeholder workshops · Agile
Education
Degree or certificate relevant to the role 2019
How to write a business analyst summary
Three lines are enough: your title and years of experience, the one result you are proudest of, and what kind of work you want next. Write it last, after the bullets, so you can pull the strongest number into it.
Bullets that get past the scan
Start each bullet with a verb, keep it to one line or two, and end with a number: money, time, volume or percentage. Copy key words from the job posting exactly. An ATS matches words, so "Epic EHR" and "electronic health records" can count as different skills.
Format that the software reads
Use one column, standard headings (Summary, Experience, Skills, Education), your contact details in the body of the page and a common font. Export a PDF from Word or Google Docs so the text stays selectable. Every Halden template is built this way.