Platform Lead - Openshift

You'll own the technical direction of an enterprise OpenShift platform and stay hands-on while you do it. This is not a people-management-only role. A significant part of your week goes on platform engineering, troubleshooting, architecture and automation; the rest goes on leading a team of OpenShift administrators and setting the standards they work to.The workSet and hold the technical direction for the container estate across every environmentBuild, run and upgrade clusters — with your hands on the terminal, not just approving the change requestKeep the lights on: incidents, problem management, patch cycles, backups, recovery testingMake the architecture calls on scale, capacity and where performance breaks downPush automation everywhere — declarative infrastructure, pipeline-driven deployments, Git as the source of truthHold the security line: access controls, cert lifecycle, closing off vulnerabilities before audit finds themDig into what actually caused the big outages and fix it properly rather than papering over itKeep documentation, runbooks and standards in a state where someone else could pick them upReport on service levels and platform health to people who don't speak KubernetesShare the on-call rota and lead the response when it countsLeading the teamRun the day-to-day for a team of platform administratorsReview what the team designs and ships before it reaches productionCoach engineers up — technically, not just through a development planWork alongside application, infrastructure, network, security and DevOps teams to get workloads onboarded and runningAgree priorities with architects, project managers and the wider businessWhat you'll bringAround eight years across infrastructure and platform work, with a similar depth on OpenShift and Kubernetes specificallyExperience leading engineers, formally or as the person others defer to technicallyReal command of the stack underneath — Linux, networking, storage, container runtimesProduction experience at enterprise scale, including the failures that taught you somethingFluency with automation tooling: Ansible, Terraform, Bash, Python, whichever you reach forPipeline and GitOps practices used in anger, not in a proof of conceptObservability, logging, tuning — knowing what to measure before you're askedResilience planning: availability targets, recovery objectives, capacity ahead of demandA degree in a technical discipline, or the equivalent proven the hard wayUseful, not essentialRed Hat OpenShift administration certificationExposure to service mesh, operators, cluster management and security tooling, Argo CDPlatforms serving multiple business units rather than a single application team