Software Engineer, Control Plane

Conduit's Control Plane team owns the coordination layer of the Conduit Platform: the services that provision, update, and retire everything customers run on us — rollups, RPC nodes, indexing, and whatever comes next — meter what those products consume, and give both customers and our own team a trustworthy picture of what is actually running.

The core of it is a control loop. We're building a lifecycle service that observes what's actually running and reconciles toward the desired state, rather than writing a status field and hoping it stays true. It treats each product as opaque: its shape and configuration come from schema read at runtime, so onboarding a new product type is a description, not a pull request.

If you've worked on Kubernetes controllers, provisioning APIs, deployment systems, or any platform where the hard part is keeping many systems consistent with one another, this will feel familiar. It's a web2 stack in service of web3 technology — we don't require blockchain experience, and people on the team picked up the domain here.

Three things worth knowing up front:

• →

  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.