Business analyst requirements, with the quote you would need
BA postings sit between a business team and a build. Evidence is a requirement, a process map, or a UAT cycle you ran. It is not a second title for project coordination unless you wrote the requirements.
Examples on this page are fictional composites, not customers and not testimonials.
Often required
The process you studied
Billing, onboarding, claims, or a back office.
An artifact
A story, a flowchart, a spec. Name yours.
Who signed off or used it
A department, if the resume says.
How you checked it
UAT, a workshop, or a data pull.
A tool
Visio, Jira, or a document. Do not add the posting’s suite.
Often preferred, and easy to fake
- SQL or a report you wrote
- A process metric
- Facilitation you can describe
What a citation looks like
Requirements
“Wrote the refund rules for the new billing screen and walked support through UAT for a week.”
Artifact, audience, and a check are present. BPMN certification is not.
SQL
“No sentence.”
Reading a report someone else built is not SQL.
The gap people paper over
Agile certifications and “liaised with stakeholders” without an artifact are the empty versions of this job. Keep the artifact.
Questions
Is this the same as a product manager?
Not automatically. Quote requirements and UAT. Prioritization of a roadmap may be a gap.
Can I use the employer’s internal project name?
If it is already on the resume and not confidential. Do not add code names for color.
Related: Data analyst, Product manager
Check your resume against a real posting