> Markdown version of [/jobs/ext/4581551-senior-platform-engineer-backend-platform](https://www.wearedevelopers.com/jobs/ext/4581551-senior-platform-engineer-backend-platform). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Senior Platform Engineer - Backend Platform

- **Company:** ALAN, INC.
- **Location:** Paris, United States (Remote available)
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Amazon S3, Distributed Systems, Python (Programming Language), PostgreSQL, Redis, SQLAlchemy, Datadog, Flask (Web Framework), Large Language Models, Backend, Fastapi, Event Driven Architecture, Kubernetes, Database Replication, Front End Software Development
- **Published:** November 5, 2026
- **Apply:** https://arc.dev/remote-jobs/j/redirect/pwoa0cqgdh

## About the Role

* 5+ years of backend engineering, with code other teams depend on: libraries, frameworks, pipelines, internal platforms. You ran it in production and owned it.
 * Distributed systems as a daily tool: events and messaging (delivery guarantees, ordering, idempotence, retries), data replication, consistency, transactions.
 * PostgreSQL in depth: transactions, locks, replication, query plans.
 * You have split a monolith or built services, step by step, while production kept running.
 * You measure before you optimise, and you set SLOs and alerts for what you own.
 * English working proficiency. French is not required.

Mindset we value

 * Product mindset. Product teams are your customers. Adoption is how you measure success.

## Description

* The events pipeline. How our components and services talk to each other asynchronously: a Postgres outbox, Redis Streams, an S3 archive. It is in production for about 20 components. You make it a product that teams use on their own.
 * Data replication between services. A service publishes read-only tables. Other services keep a local, fresh copy and join on it. This replaces slow joins across components.
 * Towards big services. The tools to take capabilities out of the monolith: a service template, APIs between services, traces across services, dependency management. We start with a pilot and turn it into a playbook.
 * The shared runtime. Queues, cache, the transaction layer. Their limits, their SLOs, their headroom.
 * The backend direction. The rules for how we build backends at Alan, written with the other engineering teams.

️ The stack

Python, Flask, SQLAlchemy, PostgreSQL, Redis, RQ, Datadog, all in a monorepo. New services are async-first. We deploy daily and believe in distributed ownership: you build it, you own it. You don't need prior Python experience., * You write to think and align. Short framing docs and decision records are how this team works with the rest of engineering.

 * Influence without authority. You get other teams to change how they build, with no reporting line.
 * Incremental. One pilot first, then the playbook. No big-bang rewrites.

Strong plus: you worked in a platform team that served product teams

 * event-driven architecture at scale
 * CDC or logical replication
 * async Python (asyncio, FastAPI)
 * multi-region or data residency
 * health, payments or other regulated data.

Not required: frontend

 * Kubernetes and cluster operations
 * database administration
 * LLM or AI expertise. Other teams own those.

Mission alignment

 * Healthcare technology excites you.
 * Leveraging AI to redefine our roles and unlock scalability.

For this opportunity, we are aiming to hire at D level or above. These are senior individual-contributor seats. Your leverage comes from technical depth and from how many teams use what you build.

But above all, we are looking for high potential and curiosity: make sure to show us this when you apply! Everything else is a bonus.