[Hiring] Software Engineer @Conduit

Role Description

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.
• Provide a trustworthy picture of what is actually running.
• Build a lifecycle service that observes what's actually running and reconciles toward the desired state.
• Treat each product as opaque, with onboarding a new product type as 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.

• A small, senior team with a large charter.
• The mission is automation.
• A lot of this work is decoupling before extending.
• The team optimizes for correctness and reliability first.

What you'll work on

• Lifecycle as a service: A single, well-defined interface for provisioning, updating, repairing, and retiring what customers run.
• Schema-driven, product-agnostic design: Moving product-specific knowledge out of code and into contracts.
• Usage and consumption reporting: A product-agnostic path for metering what customers consume.
• Internal tooling: Admin surfaces that let our own teams operate the platform through the control plane's abstractions.

Responsibilities

• Own the interfaces other teams build against — lifecycle operations, usage reporting, schema contracts.
• Integrate systems that don't fit together on their own, including third-party billing and partner integrations.
• Drive cross-functional coordination when the control plane is the shared point of integration.
• Improve the tooling and process that keep the platform maintainable and reliable.
• Participate in the team's oncall rotation, covering the control plane services you own.

Qualifications

• 5+ years building and operating production backend systems.
• Systems breadth: ability to reason across several interacting systems.
• Experience designing APIs and contracts that other teams depend on.
• Comfort with asynchronous and event-driven systems.
• Experience debugging complex issues across the stack.
• Self-directed: comfortable with ambiguity and able to drive loosely-defined problems to completion.
• Able to become productive in an unfamiliar language quickly — our services are Go today.

Bonus

• Production Go experience.
• Built reconciliation- or controller-pattern systems.
• Worked with schema- or config-as-data systems.
• Metering, usage reporting, or other systems where correctness has financial consequences.
• Built internal tools for expert operators.
• Crypto / web3 background — genuinely not required.

Our tech stack

• 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.