Storage Engineering Manager

Uppgiften

The team The Storage team builds and operates Verda's storage platform. It runs Ceph across every Verda datacenter: block storage (RBD) behind every VM volume, CephFS and NFS behind our Shared File System, and RGW behind S3-compatible Object Storage, which is launching to customers with multi-site replication. The team operates shared cloud clusters and dedicated storage clusters for customers running large-scale ML training, brings up a new storage cluster with every datacenter we open, and provides storage to internal engineering teams, including the Kubernetes platform. It also owns storage performa… Core stack: Ceph (RBD, CephFS, RGW multisite), NVMe, HAProxy, Ubuntu, containers, high speed fabric storage networks, Gitlab, VictoriaMetrics, Grafana, PagerDuty. The role You will lead the Storage team as its Engineering Manager, reporting to the VP of Infrastructure. The team is small, senior, and growing as Verda opens new datacenters at a rate of greater than one a month. Your job is to turn deep individual expertise into a mature team that can scale: you own its people, its delivery, and the reliability and durability of the data it holds. You own the team and its growth. Hiring, onboarding, career development, and building depth so the team's knowledge does not live in one or two heads. You decide what the team should look like in a year, and you build it. You own priorities and projects. Storage sits underneath almost everything Verda sells: VM volumes, shared filesystems, object storage, dedicated clusters, new sites. Every team needs something from Storage. You set the priorities, give requests a clear front door, say "not yet" when it's the right answer, and drive multi-quarter projects to completion. When someone needs to know what Storage will deliver and when, you are the answer. You own maturity and reliability as an outcome. A storage incident can mean lost data and lost customer trust, and you are accountable for it not happening. That means defining durability and availability targets for each service the team runs, running the sheriff and on-call rotation and escalation path, owning incident response and postmortems through to closed actions, managing capacity, upgrade and hardware risk, and deciding when reliability work takes precedence over feature work. You replace heroics with process: runbooks, change management, upgrade playbooks, and a repeatable storage r… The tech lead and Staff Engineer own technical architecture and direction. How the storage platform is built, which backends it uses, and how services are designed to meet the targets you set. You decide the technical roadmap together; on questions of how, they have the final say, and on who, what, when and whether, you do. This role requires real storage engineering depth. You should be able to read a Ceph design doc, a rebalancing plan or an incident timeline and argue with it: you know why etcd does not belong on distributed storage, and what a read hotspot on a handful of OSDs looks like. But your primary output is a team that ships reliably, keeps growing, and stays healthy.