Ophelos · We're hiring

Platform Engineer

Craft and maintain the technology backbone that powers Ophelos.

You'll build the platform that empowers financial health for consumers and businesses. DevOps at its core — Kubernetes, IaC, CI/CD, AWS, security. Your work directly determines how reliably and fast our engineers ship, and how stable our systems are for our customers. Aligned with our vision of a financially educated and equal world.

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
Platform
What we're looking for

Key skills

No one is the finished article — but some experience matters for this role. Here's what we're really looking for.

01

Kubernetes & IaC

Strong understanding of Kubernetes and containerisation (Docker). Comfortable with GitOps practices and Infrastructure-as-Code (Terraform, Pulumi). You've built and run production K8s estates, not just touched them.

02

CI/CD & AWS

Proficient with deployment pipelines — CI/CD, GitHub Actions, Argo. Familiar with AWS-based infrastructure (EKS, RDS, ElastiCache, Kinesis) and grounded in networking/DNS fundamentals (OSI layers).

03

Security & operations

Experience with security operations and best practices — vulnerability management, incident response, security monitoring. You think about platform stability, uptime, and error rates as primary success metrics, not afterthoughts.

The team

Who you'll work with

This is your team. The Platform crew you'd be building, running, and on-call alongside.

Simon Lao
Simon Lao
Senior Platform Engineer
LinkedIn
Wayne Parker
Wayne Parker
Platform Engineer
LinkedIn
Dhyan Selvam
Dhyan Selvam
Platform Engineer
LinkedIn
The role

What you'll be doing

You'll craft and maintain the technology backbone that powers Ophelos. Your DevOps expertise is what enables our engineers to ship reliably, our infra to scale, and our systems to stay secure and fast. Success is measured concretely: reduced deployment times, systems stability (uptime, error rates), and positive feedback from the teams you serve.

How your time breaks down
40% · Developer experience
Collaborating with the tech team to streamline our deployment process and improve developer experience. You're the reason engineers can ship fast and confidently — pipelines, tooling, paved paths.
30% · DevOps reliability & scale
Developing and enhancing our DevOps practices, ensuring the platform's reliability and scalability. Build sustainable systems — highly available, highly resilient — that scale with the business.
30% · Security, monitoring & performance
Proactive systems monitoring, issue resolution, and continuous improvement. Own infrastructure and security projects and lead Security, Infrastructure, and Performance initiatives. Mentor less experienced members of the team as we grow.
A day in the life

A typical day mixes building, supporting, and shipping. You might be improving a CI/CD pipeline, debugging an EKS rollout, responding to a Datadog alert, or pairing with a product engineer on a deployment problem. Regular time goes into IaC (Terraform/Pulumi), GitOps workflows, and security tooling. Three days a week you're in the Liverpool Street office with Simon, Wayne, and Dhyan — the platform crew. LLM tooling (Claude Code, Codex, OpenSpec) is part of how the wider org works; you'll use it day-to-day and help shape how it shows up in platform work.

How we work

AI-native, end to end

Every company says they use AI. The real question: if you removed it, would the product still work? At Ophelos, the answer is no — the core of what we do (deciding who to contact, how, and when) leverages AI systems and machine learning. It's not a rules engine with a chatbot bolted on.

Where AI actually shows up
Outreach Decision Engine (ODE)
Runs every day across every active debt account. Calculates whether contacting a specific person today is worth it and whether the benefit will be achieved — not an impersonal contact schedule.
Customer Portal
A live Claude-powered agent. When someone visits to make a payment, they're talking to an AI that knows their balance, payment history, available options, and creditor. It can answer, guide, escalate, and respond in their language.
Ingestion & Comms
AI extracts structure from new debt files, validates schemas, and drafts email, SMS, and letter templates that operators refine — not the reverse.
How engineers work day-to-day

The stack is Claude-native end to end. Engineers use Claude Code and VS Code as their primary environment, with AI embedded at every stage — writing, reviewing, debugging, refactoring. The product itself runs on the same stack: a purpose-built AgentOS powered by Agno, routing to Claude and OpenAI through an internal LLM gateway. Specs and designs are drafted with AI before code; engineers use a structured workflow where AI helps write proposals, technical designs, and task lists — it's a partner on architecture, not just a code completer.

Ways of working & stack
How we work
  • Platform-as-product — your customers are the engineers across Ophelos.
  • GitOps and IaC by default — no clicking around in cloud consoles.
  • LLM-first across the wider org — Claude Code, Codex, OpenSpec are part of how engineers work.
  • Hybrid — three days a week in-person at our office near Liverpool Street.
Tech stack
  • AWS EKS · RDS · ElastiCache · Kinesis
  • Kubernetes · Docker (containerised services)
  • Ruby on Rails (the main app)
  • Databricks (orchestrating AI & data pipelines)
  • Terraform · Pulumi (IaC)
Tools
  • GitHub Actions · Argo (CI/CD)
  • Datadog (monitoring & observability)
  • Claude Code · Codex (LLM coding tools)
  • OpenSpec (LLM-powered spec-driven development)
  • AgentOS · Agno (in-house, powering the product agents)
What to expect

Our hiring process

Four stages, designed to be a real conversation rather than a series of hoops. We aim to come back within 48 hours after each round.

1
Stage 1
Intro call
30 min · with Will Robertson (Head of People & Talent) or a trusted recruitment partner
A quick intro to understand your background, what you're looking for, and the practicals. Run by Will or one of our recruitment partners.
  • Walk through your experience and what you're looking for
  • Why Ophelos, why now
  • Practicalities — comp, notice, location
2
Stage 2
Hiring manager interview
45 min · with Ciaran Lofts (Tech Lead)
A behavioural and scenario-based conversation — how you've approached real platform problems, made trade-offs, and worked through disagreement. We learn more from concrete examples than from generic experience.
3
Stage 3
Take-home + technical walkthrough
Online · 1 hour live · plus the take-home itself
A short Helm chart task to complete in your own time, then a 1-hour online walkthrough — general questions and a pairing exercise on what you built.
  • Take-home: convert the Docker Voting App K8s manifests into a structured Helm chart (~1.5–2 hours; AI coding assistants encouraged)
  • Submit as a public GitHub repo + README explaining your approach, 24h before the live
  • Live online: a couple of general questions, then pair on extending or refining what you built
4
Stage 4
Culture and founder chat
Onsite · Liverpool Street office
Time with a few people from across the team, including one of our founders. Less about boxes to tick, more about whether this is somewhere you'd thrive.
  • Get a feel for the office and how we work day-to-day
  • Hear different perspectives on what makes Ophelos tick
  • A founder conversation to close out