Analyze vehicle identifier data quality, uncover inconsistencies, and guide client remediation while building dashboards that track data quality indicators and validate corrections.
Applied AI Analyst (Mid and Senior Level) - Transaction Enrichment
📜 Description
- Design, test, and refine prompts for merchant tagging and spending categorisation, including how transaction data is prepared for models.
- Use Python and SQL to analyse enrichment results, identify failure patterns, and recommend improvements.
- Design evaluations, including LLM-as-judge approaches, to assess whether changes improve results or introduce new issues.
- Build prototypes and test harnesses with real data to validate hypotheses before engineering work begins.
- Identify product opportunities and help shape how customers recategorise transactions and how enriched data supports other products and AI tools.
- Work with Product and Engineering to ensure findings inform the roadmap.
🛠️ Requirements
- You think in experiments: you form a hypothesis before looking at the data, design something that could prove you wrong, and interpret results with appropriate scepticism.
- You are curious about messy, imperfect systems: you want to understand why something breaks, and you brainstorm ideas to improve it.
- You can describe what you want and build it together with an LLM, to explore data, clean outputs, call APIs and prototype ideas.
- You have some experience with LLM APIs: calling them, prompting them, structuring their outputs, and understanding why they sometimes give you nonsense.
- You keep the product goal in view: you care about what changes for customers and the business.
- You are comfortable owning ambiguous problems: you can scope the work, prioritise what to test first, and know when good enough is good enough.
- You are a clear communicator who can explain what you built, what you found and what it means to engineers, PMs and stakeholders who don’t care about the implementation details.
- Evaluating LLM outputs, including LLM-as-judge approaches, ground truth sets or evals.
- Prompt engineering and prompt tuning, and comparing LLMs on accuracy, cost and coverage.
- Classification, categorisation, labelling or entity-matching problems.
Full job description
The role
Every transaction made by a Zopa customer passes through our transaction enrichment pipeline. We tag the merchant and assign a spending category, so customers can understand their money better and the rest of the bank can build on reliable data. This role is about making that classification measurably better.
As an Applied AI Analyst, you will design and tune the prompts that do the categorising, work out where and why they fall short, and help shape what we build next. At heart this is an analytical role, but one where product thinking matters as much as technical ability. You will move quickly, make pragmatic trade-offs, and care about what ships and what lands.
You will work closely with the Product and Engineering team to make sure your findings influence the roadmap. You will be comfortable using LLM APIs directly and building with AI coding tools, and you will need the underlying understanding to use them well.
About the Transaction Enrichment Team
The team sits at the heart of how Zopa turns data into intelligent products. We build and evolve the capabilities that transform raw transaction data into reliable, structured intelligence, so customers can understand their money better, and the rest of the business can build confidently on top of it.
A core focus is transaction enrichment: tagging merchants, assigning categories, ensuring data quality, and making sure everything integrates cleanly into our broader data models and customer-facing products.
As we move toward more AI-first ways of working, the tribe is also rethinking how transaction data should be accessed and used — not just by analysts and product teams, but by AI systems and LLM-powered tools. The work is foundational and long-term in nature: improving systems, shaping strategy, and building capabilities that compound in value over time.
A day in the life
-
Design, test and refine the prompts that tag merchants and assign spending categories, and work out how transaction data should be prepared and passed to the model.
-
Analyse enrichment results using Python and SQL to understand where and why enrichment falls short and making evidenced recommendations for improvements.
-
Surface opportunities the team would not otherwise: spot patterns in the data that point to a product gap, a recurring failure mode that suggests a systemic fix.
-
Design and run evaluations, including LLM-as-judge approaches, to analyse whether a change improves things or introduces new problems.
-
Build quick, scrappy prototypes and test harnesses to test a hypothesis with real data before any engineering resource is committed.
-
Shape the future of the product, for example how customers could re-categorise transactions, and how enriched data can support a wider range of Zopa products and AI-powered tools.
About you
We hire for capability rather than years, though this is typically 1-3+ years in an analytical or technical role. You’ll likely bring many of the following:
-
You think in experiments: you form a hypothesis before looking at the data, design something that could prove you wrong, and interpret results with appropriate scepticism.
-
You are curious about messy, imperfect systems: you want to understand why something breaks, and you brainstorm ideas to improve it.
-
You can describe what you want and build it together with an LLM, to explore data, clean outputs, call APIs and prototype ideas.
-
You have some experience with LLM APIs: calling them, prompting them, structuring their outputs, and understanding why they sometimes give you nonsense.
-
You keep the product goal in view: you care about what changes for customers and the business.
-
You are comfortable owning ambiguous problems: you can scope the work, prioritise what to test first, and know when good enough is good enough.
-
You are a clear communicator who can explain what you built, what you found and what it means to engineers, PMs and stakeholders who don’t care about the implementation details.
Nice to have
None of this is required, and we welcome smart people who have not done it yet. If you have experience of any of the following, we would love to hear about it:
-
Evaluating LLM outputs, including LLM-as-judge approaches, ground truth sets or evals.
-
Prompt engineering and prompt tuning, and comparing LLMs on accuracy, cost and coverage.
-
Classification, categorisation, labelling or entity-matching problems.
-
Banking, fintech, payments or another fast-paced, data-led environment.
-
Side projects or things you have built with LLMs simply because you wanted to.
What this role is not:
-
This is not a research role. We value what ships and what lands over what looks good in a notebook.
-
This is not a production engineering role. Engineering owns production code and deployment. You may occasionally contribute where it makes sense, but that is not your primary responsibility.
-
This is not a reporting role. Your value lies in the recommendations you make and what changes as a result.
Similar jobs
Search more Data Analyst jobsAnalyze casino media performance, acquisition trends, and business drivers to deliver actionable insights, improve reporting and visualization tools, and support media and growth teams’ decisions.
Execute commercial analytics and incentive reporting by managing complex datasets, calculating and auditing compensation, building dashboards, automating workflows, and turning performance data into actionable insights.
Build data pipelines, models, and dashboards that support treasury operations, turning complex financial data into clear insights while exploring AI and predictive analytics to improve reporting.
Analyze and improve customer risk and control data in the CUBE Network, supporting data matching, quality standards, and more effective processing workflows with Python and other analytical tools.
