consensys - DevOps Manager
Requirements
• Has managed a DevOps/SRE/platform team of 4+ — and is still technical enough to read a Terraform diff and disagree with it. • Has built an on-call function from nothing, or rebuilt a broken one. • Production ownership of a system with contractual availability commitments — and has been in the room explaining an outage to the customer. • Kubernetes, IaC, GitOps, multi-cloud (AWS and Azure). • Has worked through a separation, migration or carve-out where the tooling was someone else's and the accountability was yours. • Direct and calm under pressure. Our team has been through a lot this quarter and will read you carefully. • Blockchain/Ethereum node operations. • Financial services or other regulated-industry infrastructure. • Security tooling and SOC operations. • WHAT THIS ROLE IS NOT • Not a coordination layer. Not an interim step to something else. You'll have real authority over how infrastructure runs here, and you'll be held to it. • WORKING AT CONSENSYS • We are a fully remote, globally distributed company. We hire the best people wherever they are, work asynchronously, and judge each other on impact rather than hours or location. We offer competitive compensation, meaningful equity, and the chance to work on genuinely open source software at the frontier of web3. • Consensys is an equal opportunities employer. We celebrate diversity and are committed to building an inclusive environment for all employees.
Benefits
• Infrastructure services we previously consumed — observability, incident management, deployment tooling — are being rebuilt from scratch, at the same time as we sign institutional clients who want 99.95% and a named incident process. The team doing that work is small, senior, and currently without a manager. • You are that manager. Two jobs: run the team, and build the operational function the team doesn't have yet. • WHAT YOU'LL OWN • The team. A small group of senior infrastructure and DevOps engineers across Europe, US, and (shortly) APAC. Hiring, one-to-ones, growth, workload. Two of them are currently carrying multiple load-bearing roles each; fixing that is an early success measure. • On-call and incident management. You build it — severity definitions, escalation, paging, post-incident review — and you make it survivable, not heroic. • NOC/SOC capability, in partnership with Security. What we operate ourselves, what we buy, what we subcontract. • The transition off our former parent's infrastructure. Getting infrastructure-as-code, root access and tooling ownership properly handed over, and standing up what isn't. This is unglamorous, political, and the single biggest near-term risk in the function. • Client-facing operational commitments. Availability definitions, maintenance windows, RTO/RPO, DR testing, and the evidence behind them — our clients are now asking for proof, and an undocumented gap costs us less than an unevidenced claim. • Cost. Cloud spend across our networks, and the unit economics behind per-transaction pricing. • Audit readiness — supporting SOC 2 and ISO 27001 work on the infrastructure side. • Technical enough, with DevOps experience to translate requirements from management to the team. • 1. An honest written assessment of where infrastructure actually stands: what's owned, what's inherited, what's undefended. • 2. Set up runbooks, processes, for SRE to handover from the Consensys Software Inc. (CSI) team, and onboard new SREs to the development stack. • 3. Form the NOC, with a working on-call rota with a real ramp plan, not a spreadsheet of names. • 4. The hiring plan filled — starting with the APAC engineer and tech ops. • 5. One tested failover. Not a design document.
Apply in one click
Upload My Resume
Drop here or click to browse · Tap to choose · PDF, DOCX, DOC, RTF, TXT