Software Engineer

← All roles

LondonFull TimeOn-site

About Letly

Letly is the AI-Native operating company built for the home. We believe the home should be autonomously run and we're building the software that will run all rental properties end-to-end.

The backend at Letly is technically difficult on purpose as the operational realities of handling property and money are messy. But the foundations are already there: 10+ backend and AI services, a monorepo on the frontend, GitOps and Kubernetes on the infra side. You'd be building on solid ground rather than firefighting a fragile prototype — with a lot still to build.

We've raised a $4m pre-seed and are a small, high-agency, engineering-oriented team, growing revenue at >100% month-over-month. We're hiring to facilitate this aggressive growth.

Our stack

Backend — a microservice architecture in NestJS and TypeScript, with Python and FastAPI for the AI agent services.
Data — MongoDB Atlas and Redis.
Event-driven — services coordinate over Pub/Sub rather than calling each other directly.
Infra — Kubernetes on GCP (GKE), deployed via ArgoCD.
Frontend — Angular in an Nx monorepo.

How we build

Small, well-factored services with clear boundaries. Tests are written alongside the code, not after it — they're what lets us move quickly without breaking things that handle money. Trunk-based CI/CD: you ship to production and own it, with observability and clean rollbacks. Lean frameworks, readable code.

We work on a wide spectrum of technical challenges from money movement to operational logistics (scheduling, bookings, access) mediated over event-driven systems, to building around AI agents in production that are capable of executing autonomously under the hood.

What we're looking for

You've built and operated production backend systems that real users depended on. We care about the scope you've owned and how you owned it.
First Class or high 2:1 (or international equivalent) in Computer Science or a relevant technical field.
Fluency in at least one backend language and framework. You don't need to arrive fluent in our stack: we hire engineers who've built production systems with any robust framework — NestJS/TypeScript, Java/Spring Boot, Go, Kotlin, C#/.NET or Ruby on Rails — and can ramp into TypeScript fast.
The range to reason about system design: where a service boundary belongs, what a design trades away, and how it holds up once it's live.
Strong fundamentals: concurrency, HTTP and API design, data modelling (document or relational), and what actually happens when a call fails.
You treat tests as part of shipping, you work comfortably in a shared trunk, and you can read a large codebase you didn't write.
You use AI heavily and still know exactly what you shipped. Generated code has the same quality bar as what you wrote by hand: you can explain every line, you've thought about the constraints it has to bear, and you don't merge anything you couldn't have written yourself.

How you work

Hyper-focus on detail. These systems move money and manage assets; we have low tolerance for "mostly right".
First-principles reasoning. You take a hard problem apart rather than reaching for the nearest familiar pattern.
Communication clarity. You can explain a complex trade-off to another engineer, and to someone who doesn't write software — because here you'll have to do both.
Ownership mentality. You own the outcome, not the ticket: start to production, without being chased.
Collaborative. Teams change the world, not individuals. You make the next engineer better and faster.
Adaptability. You do well in a fast-moving environment where requirements shift under you.
Learning velocity. You pick up new paradigms quickly and don't need long to get productive in unfamiliar territory.
Quality-obsessed. Not just the code — the tests, the docs, the handover, the thing you leave behind.