About the role
Each app lives at its own address, so one person's app can never read another's data. In production, Cloudflare serves those addresses: a Worker reads a copy of each app that our server writes to Workers KV on every publish, update, rollback, delete and takedown.
You'll own that path and everything around it: the Worker and its deploys, DNS, the sync and its retries, the deployment of the server itself, the database, and what we see when something goes wrong (logs, traces, error reports).
What you'd do
- Own the Worker, its deploys and its routes, and keep its answers byte for byte the same as the server's
- Keep the sync between our database and Workers KV correct under failure
- Run deploys, database changes (with a dump first) and rollbacks
- Own observability: structured logs, traces, error reporting and the alerts that matter
What we need
- Three or more years running production systems
- You've operated something behind a CDN or at the edge
- Comfortable with DNS, TLS and HTTP caching
- You write down how to do a risky operation before you do it
Nice to have, not required
- Cloudflare Workers and Workers KV
- Postgres operations: backups, migrations, roles
- OpenTelemetry
How we work
- Small team, thin slices, shipped weekly. Nothing sits on a branch for a month.
- Reviews are real. Every feature ships with its tests, and a bug found in review is cheaper than one found by someone using it.
- Private by default. A person's app data stays on their phone, and nothing we build may need to read it.
- We only claim what ships. That applies to the product, the roadmap and the offer letter.
How hiring works
- 1A 30-minute call about something you've built and what was hard about it.
- 2A working session on a real problem from this codebase. You can drive, or we can pair.
- 3A conversation about how you make decisions when the evidence is thin.
- 4References, then an offer. We aim to answer within a week at every stage.