Golang SRE / Production Engineer
We’re looking for an SRE who thinks like a systems architect and builds reliability through automation. You should have lived inside large production environments and be allergic to manual processes.
What you’ll do
Design and build automation-first reliability systems in Go
Treat infrastructure as pipelines: provisioning, observability, deployment, failover
Build internal tooling, control planes, and reliability infrastructure
Own production readiness, alerting, and operational maturity
Work across protocol, networking, and hardware boundaries
What we’re looking for
Big tech SRE / Production Engineering background or similar
Strong Golang engineering skills in production environments
Systems thinker: you design for scale, reliability, and operational simplicity
Experience building internal platforms rather than just operating existing ones
Comfort with distributed systems, networking, and low-level system behavior
ABOUT DOUBLEZERO
DoubleZero is a high-performance, permissionless global network purpose-built for distributed systems. The mission is simple: increase bandwidth and reduce latency.
DoubleZero increases bandwidth by filtering junk data that currently plagues validators and other network operators. DoubleZero reduces latency by connecting these filters via underutilized private fiber links, forming a mesh network. By combining these improvements and routing the right data through optimized, low-latency paths, the DoubleZero protocol empowers blockchains and other systems to achieve performance levels previously impossible.
In short, DoubleZero is a new Internet for distributed systems. It is supported by many independent contributors. Among them, DoubleZero Foundation drives the adoption, decentralization, security, and advancement of the protocol. Malbec Labs develops the technical components of the protocol itself. We look forward to hearing from you.
Check your CV against this role
Drop your CV. You get a 0-100 fit score against the actual job description, plus the read a senior engineering lead would write. Private to you.
Score this once, or every future role
Start the candidate journey and every new role on the board gets scored against you.
Five minutes. Tell us what you’re after, drop your CV once, pick how we should reach out. You get a candid read back and you only hear from us when a role fits.