Software Engineer (Control Plane)

Join Conduit's Control Plane team as a Software Engineer. You'll be responsible for building and maintaining the coordination layer of the Conduit Platform, focusing on lifecycle management, usage reporting, and internal tooling. This role requires strong systems judgment, experience with production backend systems, and a passion for building robust, large-scale services.

• Conduit's Control Plane team is responsible for the coordination layer of the Conduit Platform, which includes provisioning, updating, and retiring customer services.
• The team is focused on building a lifecycle service that observes and reconciles the actual state of services with the desired state, treating each product as opaque.
• The mission includes automating platform operations, decoupling systems, and optimizing for correctness and reliability, with a focus on building robust, large-scale, always-on services.

• Self-directed: comfortable with ambiguity, able to take a loosely-defined problem and drive it to done
• Experience debugging complex issues across the stack — networking, performance, data integrity — and good instincts for where security boundaries belong
• 5+ years building and operating production backend systems
• 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
• Systems breadth: you reason across several interacting systems at once — how they fail, where the seams belong, how they stay consistent
• Able to become productive in an unfamiliar language quickly — our services are Go today
• Love building and iterating on new technologies in a fast-paced environment
• Would rather build the abstraction that makes the next ten integrations easy than hand-wire the eleventh
• Are excited about building robust, large-scale, always-on services
• 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?
• Want to work somewhere that writes real design docs — arguing a position, naming the tradeoff, and disagreeing in writing before the code gets written
• Production Go experience
• Built reconciliation- or controller-pattern systems (Kubernetes operators, Terraform providers, provisioning or deployment control planes)
• Metering, usage reporting, or other systems where correctness has financial consequences
• Built internal tools for expert operators
• Worked with schema- or config-as-data systems (CUE, JSON Schema, protobuf) and the realities of schema evolution and migration
• Crypto / web3 background — genuinely not required