Head of Engineering

About the Company

Responsibilities

• ● ABOUT CONSENSYS
• ● Consensys Incorporated is an independent blockchain infrastructure company, spun out of Consensys Software Inc. - one of the world's leading blockchain technology companies and the primary development organization behind the Ethereum ecosystem.
• ● We build and operate neutral, institutional-grade blockchain infrastructure that connects banks, asset managers, custodians, and financial market infrastructures to digital asset networks, meeting the non-negotiable standards of institutional finance: privacy, scalability, resilience, security, and regulatory readiness.
• ● WHY THIS ROLE EXISTS
• ● We build and operate blockchain infrastructure for financial market infrastructure - settlement, custody and clearing institutions who put real value on the networks we run. We have signed clients with production dates this quarter, a platform that has to stand up on its own for the first time, and an engineering organization that has just been through a leadership transition.
• ● You are the engineering leader for that organization - the person who owns what we've committed to ships, and who the engineers look to when a technical decision needs making.
• ● WHAT YOU'LL OWN
• ● The delivery organization - core engineering (sequencer, node and backend services), smart contracts, and infrastructure/DevOps.
• ● Client delivery against contractual commitments. Several institutional programs are in flight with production dates between now and Q1, each with availability, latency and evidence requirements written into the contract. Availability definitions, maintenance windows, DR, incident process and the proof behind them are yours. System reliability engineering and on-call rota included.
• ● Operating production networks - including a public mainnet run under an arm's-length managed-service agreement, alongside sovereign and permissioned networks for clients.
• ● Work with the Security Lead to help set security standards for partners, clients and internal systems.
• ● The technical roadmap and its sequencing - working with Product and Sales to define what we build, what we buy, what we say no to, and the honest version of when.
• ● Completing the separation from our former parent. Observability, deployment tooling, identity and infrastructure-as-code all have to be rebuilt or properly handed over, under a live clock.
• ● Engineering standards and the release process - how we test, how we ship, how we roll back, how we review, and how we maintain.
• ● Being a credible technical voice with clients. Our buyers are institutional. They will ask you hard questions about resilience, custody of keys, and what happens at 3am, and they will judge the company by the answer.
• ● Leadership and people management - hire, lead, mentor, and develop engineering managers and team leads; foster a remote-first, high-performing, collaborative engineering culture; support performance management and career development; and liaise closely with team leads to coordinate priorities, dependencies, resourcing, and delivery across engineering.
• ● Contribute to major architecture or investment proposals.
• ● Meet customers or partners where engineering involvement is valuable.
• ● Managing and integrating company wide objectives into engineering team based measurable objective key results (OKRs) and communicating on these objectives to the organization.