Infrastructure Engineer

Conduit's infrastructure team builds the systems, tools, and abstractions that power the Conduit Platform — and partners with engineering teams across the company on the cross-cutting projects that define what Conduit can build.

Because we're an infrastructure company at our core, the most interesting work here tends to span multiple teams and surfaces: a single feature might touch the control plane, the data plane, and a customer-facing API. In this role you'll split your time between first-party infrastructure work — designing, building, and scaling the platforms our customers rely on — and partnering with other engineering teams from project kickoff on the cross-cutting work that needs deep systems expertise woven throughout. You're not permanently attached to any one team — you bring systems chops to whichever cross-cutting project needs them, and you're there from design through ship, not only when something is on fire.

Because the work spans so many surfaces, systems knowledge and self-direction matter more than any specific tech. You should be the kind of engineer who can pick up an unfamiliar codebase, figure out what matters, and drive it forward.

• →

  Design, build, and scale the infrastructure that powers the Conduit Platform — availability, reliability, performance, and cost

• →

  Partner with engineering teams across Conduit on cross-cutting projects from kickoff through ship — bringing systems and reliability expertise into design, implementation, and rollout

• →

  Drive systems-level work that crosses team boundaries — performance, capacity, scaling, networking

• →

  Build shared tools, libraries, and abstractions that up-level the whole engineering org

• →

  Drive sustainable incident response and retrospectives

• →

  Participate in on-call rotation

• Know your way around a shell

• Strong foundation in software design and system internals

• Solid understanding of distributed systems and security best practices

• Strong production coding ability in Go, Python, or similar

• Self-directed: you can pick up an unfamiliar codebase or problem space, figure out what matters, and drive it to done with minimal hand-holding

• 3+ years building and supporting production systems on a public cloud (e.g. GCP, AWS)

• Experience designing and supporting highly available and scalable distributed systems

• Experience debugging complex issues across the stack — networking, performance, memory, etc.

• Work effectively with engineers across teams — comfortable mentoring, peer reviewing, and contributing to other teams' designs

• Experience running large-scale Kubernetes (e.g. clusters in the 100–1,000+ node range)

• Crypto / web3 / rollup background

• Own problems end-to-end and are willing to learn and pick up whatever knowledge you're missing to get the job done

• Like working across the stack and across teams — one project might be deep in our K8s control plane, the next a cross-team build that touches the rollup data path, the next shared tooling

• Like sitting at the boundary of software engineering and operations, and don't want to be pigeonholed into either one

• Get energy from being a core collaborator on the cross-team projects that define what Conduit can build

• Like problem solving in a dynamic collaborative environment with modern cloud tooling

A flavor of technologies in-use:

• Languages: Golang, Python

• Cloud: GCP (GKE)

• Infrastructure: Kubernetes, ArgoCD, Helm, Terraform

• Observability: Prometheus, Grafana

• Databases: Postgres (CloudSQL, AlloyDB), Bigtable, Redis