Show them as requirements you wrote for an agent, test cases you built from real work, and decisions you reviewed, then add a certificate number an employer can check. A business analyst is believed when the CV shows what the agent was allowed to do, where it had to stop for a person, and how you proved it held.
What does a hiring manager need to believe about a business analyst?
Most business analyst CVs already say "gathered requirements" and "mapped processes". Adding "AI" to those lines changes nothing. A hiring manager in a retail bank wants to know three things: that you can describe a job precisely enough for an agent to do part of it, that you know which parts must stay with a person, and that you can prove the agent behaves as specified.
That last point is the one most analysts miss. With agents that act, a requirement is only finished when there is a test that shows it holding on real cases. If your CV shows you wrote acceptance cases from past complaints or past applications, you are describing the work employers need done.
Which parts of the work were the agent's and which were yours?
Be exact about the division. Overclaiming ("built an AI system") reads as vague; underclaiming ("used AI tools") reads as nothing. Use the language of the work itself:
| Task in a retail bank | What the agent did | What you did as the analyst |
|---|---|---|
| Complaint triage | Read the complaint and drafted a category and reply | Defined the categories, the sources it could use and when it must hold for a person |
| Account maintenance requests | Executed routine address changes within limits | Set the limits, listed the exceptions, wrote the test cases |
| Affordability queries | Drafted an explanation for a person to send | Mapped which data was a sealed bank record and which was the customer's own statement |
| Fee refunds | Drafted the refund; a person approved it | Specified the approval threshold and the red line it could never cross |
The right-hand column is your CV. Each row is a sentence that shows judgment, not tool use.
What does a strong CV line look like?
Take a business analyst we will call Tomasz at a mid-sized retail bank. His old line read: "Supported AI adoption in customer operations." His rewritten lines read (sample values):
- "Wrote the scope and escalation rules for a complaint-triage agent: 12 categories, 3 hold conditions, one red line (no reply that admits liability)."
- "Built 150 acceptance cases from past complaints and reviewed the agent's results with the operations lead before it moved from drafting to routine actions."
- "Reviewed held drafts for two weeks during the pilot and logged each override with a reason, which fed three changes to the agent's sources."
Every line names the agent's job, the boundary, and evidence. An interviewer can ask about any of them and Tomasz has a real answer. The AI agent skills CV section for a business analyst gives a layout you can copy.
How do you make the claim checkable?
A claim on a CV is a promise. Three things turn it into evidence:
- A certificate number. A professional certificate issued through VerifyDoc.ai can be checked by number or QR code, and shows as lapsed or revoked on the same page if it is no longer current. Put the number and the expiry month on the CV.
- Artefacts you can describe. You cannot share a bank's test cases, but you can describe their structure: what a case contained, how it was scored, and what happened when one failed.
- Review decisions with reasons. An analyst who has sat in the review queue and can explain why a draft was held, sent back or approved is rare. Say you did it.
Avoid listing tools. Naming software tells the reader what you clicked, not what you decided.
If you are moving from analysis into an operations or oversight role, the guide on rewriting a business analyst CV for AI operations jobs covers the whole document, not just this section. Compliance-leaning analysts should also read how a compliance analyst shows AI agent skills on a CV, since the evidence employers look for overlaps.
Where the Academy fits
Pryme Intelligence Academy gives a business analyst checkable proof at two levels. The Operator certificate shows you can review an agent's decisions to a standard: a written exam and a two-week practicum, signed off by an assessor, done on a simulated queue in a free workspace if your employer does not use Pryme. The Builder certificate suits analysts who design and certify agents. Start with the free Foundations badge if you are unsure which fits.
Questions people ask
Should a business analyst list prompt writing as a skill?
Only as part of something larger. Writing an agent's brief, its sources and its limits is the skill; the wording of a prompt is a small piece of it. A line about scope and test cases says more than a line about prompts.
What if my employer's agent project was cancelled?
List what you did anyway. Requirements, test cases and review decisions are evidence of skill even if the agent never went live. Say plainly that it was a pilot.
Is the Builder certificate better than Operator for an analyst?
It depends on the job you want. Operator suits review and oversight roles; Builder suits roles where you design and certify agents. Many analysts take Operator first, since the tracks build on each other. Read the guide to AI skills for job seekers to see what each kind of employer will ask you to prove.