DoubleZero is hiring a Golang SRE / Production Engineer in Malbec Labs — Remote. The overview below is synthesized from the employer posting on jobs.ashbyhq.com: factual requirements and scope are preserved, but prose is rewritten with editorial context. Verify details and apply via the employer link.
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
Day-to-day scope for the Golang SRE / Production Engineer as described in the posting:
- 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
Company context from the listing:
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.
In short, DoubleZero is a new Internet for distributed systems. It is supported by many independent contributors.
Build a standout application
For the Golang SRE / Production Engineer at DoubleZero, reviewers look for concise evidence over buzzwords. Mirror the language of the posting sparingly, quantify support or delivery outcomes, and show how you handled ambiguity, time-zone collaboration and user empathy. Keep your resume to impact, keep your cover note to one page, and link to artifacts — tickets resolved, docs shipped, dashboards owned — that prove you can operate in a fast-moving Web3 team. Prepare to discuss a time you turned a confusing user report into a clear fix and how you measure quality in support and operations.
Web3 hiring values reliability: on-time follow-through, clear writing, and a track record of improving runbooks and tooling. Treat the application as a work sample. For interviews, be ready to walk through how you prioritize across time zones, handle a difficult user, and decide when to escalate versus resolve directly. Show how you document decisions so the next teammate benefits.
In a distributed Web3 org, trust builds through written clarity. Use the cover note to demonstrate it.