Own the backend behind Kyber's real-time coordination platform. Role shape: Full ownership of the backend behind Maestro's real-time and forward scheduling platform, including the multi-tenant architecture for new stations and new customers at scale. Environment: Python, Postgres, AWS, event-driven services, state machines, third-party operational integrations, TypeScript frontend contract, technical hiring, on-site deployment, customer management. Experience: Minimum three years in production backend engineering. Practical reality: direct customer contact, time in live operations starting on the airport ramp, meaningful founding equity, coding credits, London-based, remote only by exception, UK work authorization preferred. The Problem: Operations in critical infrastructure, in transportation and logistics, look organized from the outside, but behind the curtain they run on radios, Excel sheets, emails, paper manifests, phone calls, and constant improvisation. Plans are built statically ahead of time for an operation that changes by the minute. What Kyber Brings: Kyber builds the plan before operations start, then turns it into live control as the day unfolds. We use algorithms, stateful systems, and agentic AI to continuously recompute the best allocation of tasks, staff, equipment, locations, and time as conditions change. The old playbook no longer holds, and the technology is finally good enough to replace it. The Challenge: Kyber is a coordination platform, not a tool for any one industry. The backend serves two loops over a single domain-independent model of tasks, resources, events, constraints, and plans: a reactive loop that keeps the current picture accurate as events arrive, and a forward scheduler that produces the plan before a shift starts. Events arrive late, out of order, and duplicated; upstream feeds disconnect and replay; several operators mutate overlapping state at the same time. The work includes exactly-once effects on at-least-once delivery, conflict resolution on concurrent writes, bounded read latency for operators acting on live state, and deploys with no maintenance window. The platform question is how much variation that model absorbs. Each site, customer, and eventually each industry brings its own source systems, event feeds, communication channels, labour rules, and definition of what a task is, often on infrastructure we do not control. The target is that a new deployment is configuration and data, not a branch, and that adding a vertical does not mean a second system. That constrains the schema, the integration layer, and tenant isolation, and all three have to hold as deployments, event throughput, and concurrent operators grow. What We Are Looking For: You own the backend end to end: the data model, event ingestion, and third-party integrations; state machines, APIs, and real-time delivery to the frontend; the multi-tenant architecture; the reliability of software that live operations depend on; the contract the TypeScript frontend consumes; and the standards the backend is held to as the team grows (testing, staging validation, deploys, observability, and on-call). This is a founding role. You will go on site, learn the operation, and fold what you learn back into the product. You will talk to customers directly and hire the engineers who come after you. At least three years building and running production backends. Strong Python and strong relational modelling in Postgres, with practical experience of concurrency, event ordering, idempotency, and failure recovery. Comfortable on AWS and comfortable being on call. Multi-tenant SaaS at scale, event-driven architectures, and integrations with old and uncooperative systems all count. The frontend is TypeScript, so you should be able to reason across the boundary even though you will not own it. The bar is high because the problem is hard, and Kyber will only become an exceptional company if the people building it are exceptional. We look for highly agentic engineers who move without being told what to do next, take on hard problems, and hold their standards when the operation is live and the stakes are real. Salary is not a constraint for the right person, and the role carries meaningful founding equity and coding credits. London-based, remote only by exception. UK work authorization preferred.