This role transfers that way of working to named people. It replaces the classical business-analyst function deliberately: the division does not need requirement documents that age for months before a developer reads them. It needs a person who takes a fuzzy business problem and returns a working prototype in days — something that runs, that a business owner can click through and correct, and that a squad can then harden into production.

Main Duties

• Research: take an assigned business problem, an exception flow, a manual process, a reporting gap, work directly with the person in charge, and establish what actually happensrather than relying on what the procedure says.
• Prototype: build a working draft of the solution with AI tools in days, not weeks, a runnable process mock-up, an automated report draft, a screen flow, a reconciliation script on masked data. A fully functional system must allow business owners to both operate it and correct data errors.
• Iterate in the room: refine the prototype with the business owner in live sessions, using AI to make each round of changes on the spot.
• Hand off: deliver the accepted prototype to the receiving squad with its logic documented, its data sources named, and acceptance criteria written from the prototype itself. Remain the reference person during the production build.
• Record decisions: Every prototype or proof-of-concept must leave behind a concise, one-page summary documenting: the core problem, the approaches tried, what the business owner accepted, and what was deliberately left out.
• Spread the method: pair with squad members and analysts so that AI-assisted prototyping becomes how the division works, not what one unit does.

Skill/Requirements

• Banking or payments domain exposure: experience in building for operations, payments, reporting or support flows and can read a banking process.
• AI-native working habit, or clear evidence of moving that way: uses AI tools daily to produce real output, iterates rather than accepts first drafts, and can show something they have already built or automated for themselves.
• Enough technical literacy to make prototypes real: basic SQL (or committed to reach it in three months, as for the payments analyst), comfort with data in tables, ability to read and adapt a script even without writing one from scratch.
• Good at Critical Thinking: proven instinct to ask "why" and thoroughly interrogate stated requirements before writing any code or building infrastructure.
• Possesses strong executive presence and communication skills, with the ability to confidently present, justify, and defend technical data solutions to senior leadership in plain language.