openashbyhqparadigmxyz
Infrastructure Engineer
Conduit
LocationUS
EmploymentFullTime
Posted2026-05-18T23:24:09.292+00:00
Last observed2026-06-13 05:25:02.827532
Job idparadigmxyz-conduit-xyz:ashbyhq:90255ea2-4a89-4727-907b-25bd3b369a90
Conduit is an enterprise-grade blockchain infrastructure and tooling platform powering the next generation of on-chain applications. Our platform supports many of the most notable teams in crypto, with use cases spanning payments, tokenization, and beyond. Built for security, customization, and scalability, Conduit delivers production-grade reliability paired with deep blockchain expertise—so teams can stay focused on what matters most: their product. Backed by a $37M Series A led by Paradigm and Haun Ventures, Conduit is a remote-first company with offices in San Francisco and New York City for those who prefer a hybrid environment. Our team brings experience from companies like Meta, Amazon, Aave, Compound, and Paradigm. We’re building the infrastructure layer that will power on-chain finance for the next decade. If you want to build something people rely on every day, join us. About the Role 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. Responsibilities - 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 Qualifications Required: - 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 Bonus: - Experience running large-scale Kubernetes (e.g. clusters in the 100–1,000+ node range) - Crypto / web3 / rollup background We think you'll find this work really exciting if you: - 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 sitti
This page is generated from the committed OpenOpps static snapshot. Use the source posting or apply link for the employer's current canonical posting state.