Software Engineer, Control Plane

Lifecycle as a service. A single, well-defined interface for provisioning, updating, repairing, and retiring what customers run, backed by reconciliation against observed state rather than best-effort writes.

Schema-driven, product-agnostic design. Moving product-specific knowledge out of code and into contracts the service interprets at runtime, so products and the control plane can evolve independently.

Usage and consumption reporting. A product-agnostic path for metering what customers consume and reporting it to the systems that bill for it. We don't build the billing engine — but consumption data is money, and correctness here is unforgiving.

Internal tooling. Admin surfaces that let our own teams operate the platform through the control plane's abstractions. You'll own the services and interfaces behind them, partnering with our UI engineers on the surface itself.

5+ years building and operating production backend systems

Systems breadth: you reason across several interacting systems at once — how they fail, where the seams belong, how they stay consistent

Experience designing APIs and contracts that other teams depend on — versioning, backward compatibility, deprecation

Comfort with asynchronous and event-driven systems: idempotency, retries, partial failure, eventual consistency

Experience debugging complex issues across the stack — networking, performance, data integrity — and good instincts for where security boundaries belong

Self-directed: comfortable with ambiguity, able to take a loosely-defined problem and drive it to done

Able to become productive in an unfamiliar language quickly — our services are Go today

Production Go experience

Built reconciliation- or controller-pattern systems (Kubernetes operators, Terraform providers, provisioning or deployment control planes)

Worked with schema- or config-as-data systems (CUE, JSON Schema, protobuf) and the realities of schema evolution and migration

Metering, usage reporting, or other systems where correctness has financial consequences

Built internal tools for expert operators

Crypto / web3 background — genuinely not required

Are drawn to questions like: how do we know what's actually running? How do we make a change safely when several systems have to agree? How do we let products evolve without the control plane needing to know?

Would rather build the abstraction that makes the next ten integrations easy than hand-wire the eleventh

Want to work somewhere that writes real design docs — arguing a position, naming the tradeoff, and disagreeing in writing before the code gets written

Are excited about building robust, large-scale, always-on services

Love building and iterating on new technologies in a fast-paced environment

A flavor of technologies in use:

Languages: Go (primary), Python

Services: gRPC / protobuf, GCP Pub/Sub, River (Postgres job queue), Watermill

Data: Postgres, Redis, GCS

Schema & config: CUE, YAML

Runtime we integrate with: Kubernetes, ArgoCD, GCP

While we value experience with these technologies, we're primarily looking for engineers with strong systems judgment and the ability to quickly pick up new tools and frameworks.