Software Engineer, Control Plane

Role overview Join the small, senior team responsible for the coordination layer that provisions, updates, and retires customer workloads, meters consumption, and keeps internal and external users aligned on what is actually running. The work centers on a reconciliation-driven control loop that treats each product as an opaque, schema-described unit, so onboarding new product types is a matter of writing a description rather than wiring code. This is a back-end platform engineering role focused on automation, decoupling, and integration breadth in production-grade distributed systems; web3 or blockchain experience is explicitly not required.

Responsibilities - Design and own lifecycle-as-a-service interfaces for provisioning, updating, repairing, and retiring customer workloads, with reconciliation against observed state instead of best-effort writes. - Move product-specific knowledge out of code and into schema-driven contracts interpreted at runtime, enabling the control plane and individual products to evolve independently. - Build product-agnostic usage and consumption reporting pipelines that feed downstream billing systems, treating metering correctness as financially critical. - Develop internal admin tooling and services that let platform operators work through the control plane's abstractions, partnering with UI engineers on surfaces. - Define and evolve public and internal API contracts, including versioning, backward compatibility, and deprecation strategies that other teams depend on. - Participate in an on-call rotation covering the control plane services owned, and drive cross-functional coordination when the control plane is the shared integration point.

Requirements - 5+ years building and operating production back-end systems at scale. - Demonstrated systems breadth: reasoning across several interacting systems, understanding failure modes, seams, and consistency boundaries. - Hands-on experience designing APIs and contracts used by other teams, with attention to versioning and migration. - Comfort with asynchronous and event-driven architectures, including idempotency, retries, partial failure, and eventual consistency. - Strong full-stack debugging skills across networking, performance, and data integrity, plus sound instincts for security boundaries. - Self-directed working style: able to take a loosely defined problem and drive it to completion with minimal hand-holding. - Ability to become productive quickly in an unfamiliar language (the current services stack is Go).

Nice to have - Production Go experience. - Built reconciliation- or controller-pattern systems such as Kubernetes operators, Terraform providers, or provisioning and deployment control planes. - Worked with schema- or config-as-data systems (CUE, JSON Schema, protobuf) and the realities of schema evolution and migration. - Experience with metering, usage reporting, or other systems where correctness has direct financial consequences. - Built internal tools for expert operators. - Background in crypto or web3, though not required.

Benefits and work setup - Remote-first organization with optional hybrid offices. - Small, senior team with a wide charter and outsized influence on architectural direction. - Culture that emphasizes written design documents and disagreement-before-code. - Tech stack includes Go and Python services built on gRPC and protobuf, Postgres, Redis, GCP Pub/Sub, job queues, CUE-based schema, and Kubernetes-based runtime integrations.