Kubernetes Storage Engineer with Restoration

Role : Senior (Kubernetes ) Storage Engineer IT Infrastructure
Experience : 6+ yrs (relevant)
Role Description
Kubernetes-native storage. Rook and Ceph, the CSI layer, StorageClasses, and how a persistent volume claim becomes real capacity. This is the centre of the role, not an adjunct to it.
Provable backup and restore. Not just that backups ran, but that a restore has been performed, timed and witnessed. You would own the evidence, and the schedule that keeps it current.
The enterprise arrays. Pure Storage and NetApp, including snapshots, replication, provisioning, capacity planning and performance work.
Disaster recovery. Designing the tests, running them, and fixing what they expose. RPO and RTO you can defend with a number rather than an intention.
The storage standard. Documentation, monitoring, alerting on failure rather than on absence of success, and the capacity roadmap.
Initial Task
Establish provable backup and restore across every tenant and platform system, with independently witnessed evidence. This is a stated company priority, and it would be yours.
Bring Ceph and the Kubernetes storage layer under the same operational standard as the arrays.
Run at least one full DR exercise end to end and close what it uncovers.
Remove the single points of knowledge, so no part of the storage estate depends on one person being reachable.
Experience
Kubernetes storage, hands-on in production. Rook and Ceph, or a CSI driver you have operated. You should be able to explain what happens between a persistent volume claim and real capacity, and describe a time it did not work and how you found out why. Provisioning storage and handing it to a Kubernetes team does not meet this bar.
Restores you have personally performed. Not backup jobs you monitored. An actual restore, that you ran, recently, and can tell us how long it took and what came back. A backup nobody has restored is not a backup, and this is the first thing we will ask about. Hands-on Kubernetes storage in production. Rook and Ceph, or an equivalent CSI-based platform. Persistent volumes, Storage Classes, and the boundary between cluster storage and physical capacity.
8+ years in storage and data protection, across both enterprise arrays and software-defined storage.
Real protocol depth, not product familiarity. iSCSI, NVMe over Fabrics, Fibre Channel, NFS and SMB. You should be able to explain what each one does and when you would choose it, independently of any vendor's console.
Backup and restore ownership using Commvault or equivalent, including retention, compliance, and how a failure reaches a human.
Pure Storage and NetApp, including snapshots and replication such as SnapMirror or FlashArray features.
Disaster recovery you have designed or led, including the testing, not only participated in.
Backup and storage for virtualized environments, VMware in our case.
Performance troubleshooting: the ability to prove whether a problem is the storage, the host or the network, rather than assert that it is not yours.
Scripting or automation for provisioning, reporting and restore verification.
Bachelor's degree in a technical field, or equivalent practical experience.
How the team works
You would join the IT Infrastructure team and work directly with platform engineering, the database organisation, security and the OEM vendors.
On-call is a shared rotation, not a permanent state. Major incidents escalate to the whole team, and we would rather fix the cause than staff the symptom.
We expect ownership rather than ticket-taking. If you find something broken outside your area, we would rather you said so than routed it.
This role is a step toward storage and data platform architecture ownership as a particular demographic centre grows.

Work arrangement
No