Software Engineer

Role overview

We are seeking skilled Software Engineers to join our team. This is a remote role, open to candidates anywhere in the Philippines. You do not need to be in Manila.

The work is hands-on and spans several platforms. You will work closely with product, business and project leads, across both legacy systems and new development.

How we work

We use Claude Code every day. It writes a lot of our Python. It is involved in most of what we build, from application code through to internal tooling and data work.

Producing code is no longer the bottleneck. Two things are. Working out what actually needs building, because requirements here tend to arrive as a rough business problem rather than a specification. And judging whether what came back is right. These tools sound just as confident when they are wrong.

Most of the skill is in the steering. Knowing what to put in front of the tool, noticing when it is working from a wrong premise, and knowing enough about the business to tell when an answer is wrong.

That last part takes time. There are a lot of systems here with twenty years of history behind them, and the fastest way in is the systems themselves. So the skill that matters is using these tools to interrogate one until you actually understand it. Query the database. Read the code. Test the theory against the real thing rather than against what you assume is there.

We are less interested in what you already know about our stack than in how fast you can do that.

The work is a mix of three things. New development, building what does not exist yet. Rebuilding, because a lot of what runs here has been running a long time and is being reworked properly rather than patched. And investigation, where a question comes in that nobody can answer from memory and you go and find out.

That last one means reading across systems you have never seen, working out what is actually happening, proving it, and writing it down so the next person does not start over. The writing down is part of the job, not admin on top of it.

Responsibilities

• Work out what actually needs building, from a business problem rather than a specification
• Design, build and test new software across a range of platforms
• Rework and replace systems that have been running for years, without breaking what depends on them
• Work with product, business and project teams to deliver
• Write maintainable code with sensible test coverage
• Use AI tooling well, and take responsibility for checking what it produces before it ships
• Dig into unfamiliar systems and data, and leave a written trail
• Improve how we work as you go

Requirements

• 4+ years of production, hands-on software engineering, including time spent maintaining and fixing things you built rather than only building them
• A track record of shipping good software at pace, alone and in a team
• Hands-on experience with Claude Code on real work. We will ask what you built with it, and where you had to overrule it

Skills

You will not have all of these. Breadth across several of them matters more than depth in any one.

Python

• We write a lot of Python. Services, data work, automation, internal tools
• Comfortable going straight at an API or a database and building something small that other people can run
• Scripts that read clearly and are safe to run twice, because much of this touches production data

Google Cloud Platform

• Compute Engine, Cloud Storage, Identity-Aware Proxy, Cloud Functions
• Deploying and running applications on GCP

Kafka

• Real-time data streaming and processing

JavaScript and TypeScript

• Front-end and back-end
• Modern frameworks. React or Angular are fine, VueJS is what we use

API development

• Robust, scalable, secure REST or GraphQL APIs, using Flask, NestJS or Spring Boot

MySQL and PostgreSQL

• Schema design, query optimisation, and writing the complicated ones

Git and GitHub

• Day-to-day version control and collaboration

Docker

• Building and running containers

What we are looking for in people

• You can work at pace without losing the thread
• You solve problems on your own, and you know when to pull someone in
• You check things instead of assuming them, and you say so when something does not add up
• You communicate clearly in writing, because the team is distributed

Why join us

• Varied work. Legacy systems and new build, often in the same week
• You will use AI tooling properly, rather than as something bolted on the side
• Remote, and flexible about how you work
• A distributed team, and colleagues who are good at this