About
Software engineer at Ophelos, a UK fintech in the Intrum group with an AI-native debt-resolution platform. I work across the Python platform and the Rails monolith it replaces. For two years I have owned how a client's file becomes data the platform can act on, along with the reliability, observability and money-correctness work around it.
This year that has included making an LLM agent's output safe to save, shipping a voice-automation pilot end to end, and taking new clients live with the market's operations team. Earlier at Ophelos I led engineering for a European market launch and rebuilt background-job monitoring. I build with AI coding agents, from plans I write and review.
I have nine years across fintech, startups and enterprise software in the UK and Japan. Before Ophelos I spent six years in Tokyo, leading development of two products at a startup and building banking and insurance systems for enterprise clients.
Selected work
-
LLMs in production
Made the LLM agent that writes client import rules safe for production: past incidents replay as automatic tests, and every generated rule set is repaired or reported before it is saved.
-
Voice automation
Owned the implementation of a voice-automation calling pilot, built end to end in three weeks; real call batches ran on it.
-
Client onboarding
Replaced bespoke per-client import setup with a published format clients fill in themselves, removing one to two weeks of engineering from each onboarding. The team then built it into the product.
-
Money correctness
Stopped the same payment being counted twice in a ledger that cannot reverse a posting, by matching the incumbent system's own rule so both platforms agree.
Experience
- London
-
Feb 2026 – present
Software Engineer III Ophelos
Software engineer across Ophelos's greenfield collections platform (Python services, TypeScript frontends) and its Rails modular monolith. I own client data ingestion end to end and the production safety of the LLM agent in that path.
Highlights
- Made the LLM agent that writes client import rules safe for production: past incidents replay as automatic tests, and every generated rule set is repaired or reported before it is saved.
- Owned the implementation of a voice-automation calling pilot, built end to end in three weeks; real call batches ran on it.
- Replaced bespoke per-client import setup with a published format clients fill in themselves, removing one to two weeks of engineering from each onboarding. The team then built it into the product.
- Stopped the same payment being counted twice in a ledger that cannot reverse a posting, by matching the incumbent system's own rule so both platforms agree.
- Took new clients live on a new collections platform, agreeing the business rules directly with the market's operations team.
-
Jan 2024 – Feb 2026
Software Engineer II Ophelos
Software engineer on Ophelos's Rails modular monolith, working on client data ingestion, reliability and observability for enterprise clients across European markets. Promoted to Software Engineer III in February 2026.
Highlights
- Redesigned background-job monitoring with frequency-bucketed metrics, alert routing and circuit-breaker batch handling, which cut the alert noise from batch failures.
- Built dependency ordering for event-sourced ingestion pipelines, so related client files process correctly when they arrive out of order.
- Built a hierarchical configuration system with cascading overrides that centralised scattered policy controls; the team reused the pattern for regulatory configurations.
- Led engineering for a European market launch and wrote the onboarding playbook the team adopted as its standard.
- Rolled out a content security policy across regions in stages.
- Tokyo
-
Sep 2021 – Jan 2024
Lead Software Engineer TENT, Inc.
Lead engineer at a Tokyo startup, building two cloud-based products in a small engineering team.
Highlights
- Led development of Kauriru, a cloud-based rental marketplace (Rails, React, AWS), driving 4x growth in shops onboarded and 5x sales growth over 2 years.
- Built and led development of ZAIKA, a cloud-based inventory management application with QR/RFID, expanding customer accounts 5x. Built a self-serve onboarding form that reduced per-company setup from 3 weeks to hours, eliminating around 100 hours of manual onboarding work.
- Owned PR review, system architecture, and onboarding tooling end-to-end across the engineering team.
-
2022 – 2023
Software Engineer (Freelance) n, Inc.
Freelance engagement alongside primary role at TENT.
Highlights
- Built marketing-application features in a four-person freelance team using Rails, GraphQL, Next.js, TypeScript, and Relay.
-
2017 – 2021
Software Engineer Groove Direction Inc.
Software development for six enterprise client companies across insurance, banking, and B2B systems.
Highlights
- Shipped a banking insurance system used at counter operations (Spring Boot, Java, Azure) and a B2B IT sales web application (Vue.js, Spring Boot).
Stack
- Languages
- Python, Ruby, TypeScript, Java
- Frameworks
- Ruby on Rails, FastAPI, Spring Boot, React
- Data and messaging
- PostgreSQL, MySQL, Redis, Sidekiq, Celery, RabbitMQ
- Cloud and tooling
- AWS, GCP, Docker, Datadog
- Tools
- Claude Code, Codex, GitHub, Cloudflare
How it's built
- Source
- Generated from the same file as my LinkedIn profile, so the two never disagree.
- Quality
- Nothing deploys until unit, browser and accessibility tests pass in three browsers.
- Security
- A strict Content Security Policy that allows only the page's own code, plus HSTS.
- Stack
- Static HTML · Python · Playwright · GitHub Actions · Cloudflare
- Method
- Built with Claude Code from plans I wrote and reviewed.
帆, the sail From my name, 一帆, “one sail”.
青海波, the waves A Japanese pattern, drawn by the page.
The route My experience as a line from Tokyo to London.
藍 and 朱, the colours Indigo, named “Japan Blue” by a British chemist, and vermilion.