Ophelos · We're hiring

Senior Software Engineer

Full Stack · Payments squad · LLM-first by default.

Join our Payments squad to build out a cross-market flexible Payments capability — at a critical moment for how the team works. We've recently transitioned to LLM-first engineering, so you'd help shape both our ways of working and our approaches to LLM-based tooling. Polyglot stack, full ownership end-to-end, and a high bar for engineering quality.

See the role
The basics
Where you'll be and how we hybrid.
Location
1 Finsbury Ave
London EC2M 2PF
In the office
3 days a week
Team
Payments squad
What we're looking for

Key skills

More than anything we're interested in your general experience as a software engineer and your approach to solving problems. Some specifics matter, though — here's what we're really looking for.

01

LLM-first engineering

Claude Code, Codex, Cursor are part of how you build, not an afterthought. You're motivated by the changing landscape and want to keep pushing it — including how agentic LLMs reshape what good software engineering looks like.

02

Polyglot full-stack

5+ years in full-stack engineering, comfortable across TypeScript, Python, or Ruby. Familiar with web frameworks like FastAPI or Ruby on Rails. Specific implementation language isn't critical — you adapt to what the problem needs.

03

Quality, curiosity, ownership

Attention to detail, intellectual curiosity, and a willingness to embrace the changing technical landscape. You enjoy learning new technologies and experimenting to figure out how to build things in a better way. Excited by Ophelos's mission.

The team

Who you'll work with

The Payments / Platform crew you'd be building alongside.

SL
Simon Lao
Platform Engineer
LinkedIn
WP
Wayne Parker
Platform Engineer
LinkedIn
DS
Dhyan Selvam
Senior Platform Engineer
LinkedIn
CL
Ciaran Lofts
Tech Lead
LinkedIn
The role

What you'll be doing

You'll be joining our Payments squad, building out a cross-market flexible Payments capability. The team has recently transitioned to an LLM-first working style — you're joining at a critical moment to shape both how the team works and how we use LLM-based tooling. Full ownership end-to-end, with meaningful and measurable impact on the org and our products.

In this role, you'll get to
Design, build and ship features end-to-end
Take features from concept to production with full ownership. You scope, you design, you build, you ship — collaborating across a close, multi-disciplinary squad with meaningful and measurable impact on the product.
Own business-critical components
Own components central to how money moves across markets and clients. Their stability and maintainability are on you — including the ledger, payment flows, and the integrations that hold the whole thing together.
Mentor and raise the bar
Mentor others on the team, share ideas openly, and push engineering standards forward. Help shape how the squad uses LLM tooling as the landscape evolves — what we adopt, where we push, where we hold back.
A day in the life

Most days are a mix of design, build, and review — almost all the build done through LLM-driven workflows (Claude Code, Codex, OpenSpec) rather than direct edits. You'll be working closely with Simon, Wayne, Dhyan, and Ciaran on the platform side, plus the wider Payments squad. Three days a week you're in our Liverpool Street office for planning, alignment, and the kind of conversations that don't happen on Slack; the other two are heads-down. You'll regularly be deciding architecture for features that touch how money moves, and pushing the team's LLM workflows forward at the same time.

How we work

Ways of working and the stack

How we work
  • LLM-first — Claude Code, Codex, and OpenSpec are central to how engineers work, not bolt-ons.
  • Polyglot by default — we pick the right tool for the problem rather than getting tribal about language.
  • Close, multi-disciplinary squads with full ownership end-to-end.
  • Hybrid — three days a week in-person at our office near Liverpool Street.
Tech stack
  • TypeScript, Python, Ruby — polyglot stack
  • FastAPI for Python web services
  • Ruby on Rails powering the legacy application
  • PostgreSQL (via PlanetScale) · TigerBeetle for the financial ledger · Databricks for the data lakehouse
  • Temporal for workflow automation
Tools
  • Claude Code · Codex — primary LLM coding tools
  • OpenSpec — LLM-powered specification-driven development
  • Datadog — observability and monitoring
  • AWS · Kubernetes — cloud-based infrastructure
What to expect

Our hiring process

Designed to be honest about how you'll actually work — not a series of hoops. Four stages, no take-homes.

1
Stage 1
Screening call
25 min · with Will from People & Talent
A quick intro — your background, why Ophelos, and the practicals.
  • Walk through your experience
  • Why Ophelos, why now
  • Practicalities — comp, notice, location
2
Stage 2
Live technical
60 min · with two of our engineers
Live coding with two engineers from the team. We care more about how you use your tools than whether you can solve the problem cleanly.
  • Pair on a full-stack engineering task
  • Use your real day-to-day toolkit — Claude Code, Codex, whatever you reach for
  • Discuss tradeoffs and architecture as you go
3
Stage 3
Values & culture
45 min · with two members of the wider team
A real values interview — focused on how you operate independently in ambiguity. Not a rubber stamp.
  • How you handle ambiguous, fast-changing work
  • What you need from a team to do your best work
  • Meet some of the wider team
4
Stage 4
Founder final
30 min · with one of our founders
A conversation with one of our founders to close out the decision.
  • The bigger picture for Ophelos and Intrum
  • Mutual fit check
  • Any open questions