Rewrite a business analyst CV around the work an agent cannot do for itself: defining what it should do, testing it against real cases and deciding when it is ready. In retail banking, that means presenting your requirements, process maps and acceptance testing as evidence that you can specify, test and govern an agent's behaviour.
Why does a business analyst already think like an agent builder?
A governed agent starts life as a brief: its role, the sources it may read and the systems it may connect to. Writing that brief is requirements work. Someone has to sit with the card disputes team, find out which cases are routine and which need a person, and write it down precisely enough that a machine can follow it. That is the job you already do.
Testing follows the same pattern. Before an agent is allowed to act, it is replayed against real cases from the bank's own operation and every answer is scored against a floor. In Pryme that certification is done by Attest, which runs seven gates: grounded, refuses, depth, escalates, scope, adversarial and stable. If you have written acceptance cases for a payments change, you understand why the cases must come from real work and why a pass on one gate does not excuse a fail on another.
What is new is the vocabulary of authority. A governed agent acts at one certified depth, from reading to drafting to executing routine work within bounds to moving money, and each action needs its own. The agent's role sets a ceiling, the evidence sets the depth, and the lower wins. Learn to write about your work in those terms, using the guide to the AI skills employers ask job seekers to prove as your reference.
What are the steps to rewrite the CV?
- You: pick the roles you are aiming at. Titles vary: "AI operations analyst", "agent product analyst", "automation business analyst". Read the duties. If the advert talks about review queues, it is an operator role; if it talks about briefs, test sets and certification, it is closer to building.
- You: recast each project as a scope decision (depth 1 to 3). For every change you analysed, say which steps you automated, which stayed with a person and why.
- You: show the approval matrix you defined (depth 3 and 4). Retail banks run on limits. A line about the refund or fee-waiver limits you set out, and who approved above them, maps directly to how a governed agent is held.
- You: describe testing as evidence. Name the cases, where they came from and the standard for passing. Say when you recommended against go-live.
- You: add a certificate with a number an employer can check.
- You: match the top third to each advert. The AI operations analyst CV template gives a layout that works for both operator and builder roles.
How do business analysis tasks translate into agent work?
| Business analysis task | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Requirements workshop | A brief is assembled from a plain-language description of the job | Candidate only | Agreeing scope, red lines and owners |
| Process mapping | Drafts the steps for routine cases | 2 | Deciding where hand-offs and approvals sit |
| Approval matrix | Acts within the bank's own limits and only drafts above them | 3, held at 4 | Setting limits, naming who approves |
| User acceptance testing | Is replayed against real cases and scored | Sets the depth | Choosing the cases, accepting the result |
| Benefits tracking | Reports held and refused volumes | 1 | Deciding whether to widen depth |
The point to draw out is that the last column is where a business analyst lives. You do not build the model; you decide what it is for, how far it may go and how anyone will know whether it is working.
Which certificate fits a business analyst?
The Academy's four tracks run in order, each the key to the next. Foundations gives you the vocabulary. Operator proves you can run a live queue: a written exam of 40 questions in 60 minutes with a pass mark of four in five, then two weeks of review decisions to a standard of nineteen in twenty with no missed red line. Builder is for whoever designs, trains and certifies agents, and ends with a capstone agent certified in Attest to depth 2 or higher.
For most business analysts Builder is the target, but you reach it through Operator, and that is useful. An analyst who has reviewed held card refunds for two weeks writes better briefs. If you are moving into a hands-on operations role first, stop at Operator and add Builder later. If you only want to understand the field, Foundations alone is enough for now.
List each certificate with its number and expiry. It is a professional certificate, not a licence, and it sits alongside any business analysis qualification rather than replacing it.
What evidence will a retail bank interviewer ask for?
Expect three kinds of question. First, scope: "Which part of a mortgage overpayment request would you leave with a person?" A strong answer names the capability, the depth and the reason, such as anything that changes the payment schedule being held for a named person.
Second, testing: "How would you know the agent was ready?" Talk about cases drawn from the bank's own history, a floor for each gate, and what happens if a later run fails. In a governed system a run that clears no depth drops the agent to depth 1 the same day.
Third, conduct. In the UK, the FCA's Consumer Duty asks firms to deliver good outcomes for retail customers, and banks supervise model risk in most markets, with PRA SS1/23 setting principles for UK banks. You do not need to quote either. You need to show that your scope decisions considered the customer, not only the cost. Analysts with a regulatory bent will find the companion piece on rewriting a compliance analyst CV useful for this part.
Where do business analyst rewrites go wrong?
- Writing about methodology instead of outcomes. "Agile practitioner" says how you worked. "Defined which dispute types stayed with a person" says what you decided.
- Overclaiming technical build. If you did not configure the system, say you specified and tested it. Interviewers check.
- Leaving out the cases you stopped. A recommendation against go-live is strong evidence of judgement. Include one.
- Ignoring the reviewers. Agents work alongside people. Mention how your designs made the reviewer's queue workable.
For the shorter version of all this, see how a business analyst should show AI agent skills on a CV.
Where the Academy fits
Lessons, labs and tests are free, and every lab runs in a free Build workspace, so you can write and test a brief without an employer's system. Module tests are set in your own industry and role, which for you means retail banking scenarios. You pay an issue fee only when a professional certificate is issued, and anyone can check it through VerifyDoc.ai by number or QR code.
Questions people ask
Is a business analyst overqualified for an operator role?
Not if the role is a route in. Operator work teaches you how agents fail in practice, which makes your later specifications better. Say in your cover letter that you see it as a stage, not a destination.
Should I list the cases I tested on my CV?
List the type and source, not customer details. "Built a test set of 200 historic card disputes" is enough, and it is plainly checkable at interview.
Do I need data science skills?
No. Agent operations roles ask for judgement about the work, precise writing and disciplined testing. Statistical modelling is a different job.