Software Engineer
Role details
Job location
Tech stack
Job description
You'll work on the core AI systems that make fraud decisions. This means building and improving the agent pipelines that coordinate LLMs, VLMs, OCR and forensic tools. You won't be just calling APIs, but designing how autonomous agents reason about complex, ambiguous evidence.
Day to day, you might be:
- Improving how the system handles a document type it's getting wrong
- Designing a new agent reasoning pattern (e.g., cross-referencing findings across multiple documents in a claim)
- Debugging why an agent produces inconsistent verdicts on edge cases
- Deploying pipeline changes to AWS and monitoring real-world performance
- Writing tests that verify an agent makes the right routing decision when evidence conflicts
The work sits at the intersection of AI engineering, systems design, and a surprisingly interesting fraud detection domain.
Builder Mindset
We're looking for people who build systems, not just talk about them.
This role is about shipping reliable AI into production: debugging edge cases, improving pipelines, and learning from real-world behaviour. If you enjoy turning ideas into working software and iterating quickly, you'll fit right in., * The specific AWS services we use (Bedrock AgentCore, EventBridge)
- Our domain (insurance fraud, document forensics)
- The exact frameworks in our stack
These are learnable. What matters more is that you can reason about systems, write reliable code, and think critically about how AI makes decisions.
How We Work
- Small team, high autonomy, async-first
- Security-conscious by default. We assume all inputs are hostile
- We'd rather halt and ask a question than ship something we're uncertain about
- Code gets attacked before it ships. We review from the perspective of a hostile auditor
- We don't over-engineer. Three similar lines of code is better than a premature abstraction
What Growth Looks Like
Early on: You're deploying changes to the pipeline, understanding how evidence flows through agents, and shipping features that touch the reasoning layer.
Later: You own major subsystems. The document analysis agent, the tool orchestration layer, or the cross-document case analysis pipeline. You're making architectural decisions about how agents reason.
Longer term: You're designing novel multi-agent patterns, integrating new forensic tools, and shaping how the platform learns from analyst feedback over time. Similar jobs, Senior .NET Engineer £65,000-£70,000 * Fully Remote UK * SaaS / PPM Sector I'm supporting a high-growth SaaS company in the Project Portfolio Management sector to hire a Senior .NET Engineer to join their remote-first UK engineering team. This role focuses on building..., Senior DevOps Engineer (SC Cleared) - Multi-Cloud Newcastle - Hybrid 4 Months Contract Inside IR35 £450 to £550 a day Active Security Clearance is Needed A high profiled consultancy firm is looking for an experienced DevOps Engineer with active SC Clearance to..., Role: Senior Software Engineer - Front End Location : London/Newcastle - Hybrid Office & Home mkodo builds world class apps, middleware and digital products in the global lottery, betting, and gaming space. We value the expertise of our team members and offer opportunities...
Requirements
You should be strong in:
- Python: you write clean, typed code and care about it working correctly at the edges
- Working with LLMs beyond chat: structured output, multi-step reasoning, prompt calibration for reliability
- AWS: comfortable with S3, Lambda, IAM, and deploying services that need to work without you watching them
- LLM/VLM Observability (e.g Arize Phoenix)
- Testing code that involves non-deterministic systems
Ideally you also bring:
- Experience with agent orchestration frameworks (LangGraph, LangChain, or similar)
- Familiarity with vision-language models for image analysis
- Some exposure to document analysis, OCR, or fraud detection
- Opinions about when agents are useful and when they're over-engineering