The role
We are interested in senior cloud platform engineers who can make delivery environments reliable and straightforward for application teams to use. You would build platform capabilities, automate changes, observe production behaviour and help improve incident response. The role combines engineering with service ownership: a platform is useful only when teams can deploy and run safely on it. You would balance standardization with the different needs of the services the platform supports. This is an ongoing expression of interest in this role, with assignment specifics discussed later.
What you would work on
- Provision and evolve cloud and Kubernetes environments with infrastructure as code, reviewable changes and clear rollback paths.
- Improve deployment pipelines, secrets handling, access boundaries and workload configuration for teams using OpenShift, EKS or similar platforms.
- Define practical monitoring, alerts and service indicators with application teams, using production evidence to prioritize reliability work.
- Participate in incident response, coordinate recovery steps and turn post-incident findings into automation or platform improvements.
- Document self-service paths, operational runbooks and ownership so engineers can deploy, troubleshoot and request support efficiently.
Essential experience
- Production cloud and container-platform engineering, including Kubernetes concepts, networking, identity and secure configuration.
- Infrastructure automation and CI/CD work where you can explain testing, change control and recovery decisions.
- Ability to diagnose operational problems across infrastructure and applications, communicate during incidents and follow through on fixes.
Useful additional experience
- OpenShift or AWS EKS, policy-as-code, platform self-service and service-level objectives.
- Experience reducing toil or improving observability and incident learning for multiple development teams.
What to include in your application
Send your résumé and describe a platform improvement you delivered. Include the problem teams faced, the automation or architecture you changed, how you measured the result and how it affected operations. If the change followed an incident, describe the immediate recovery and the longer-term fix. Tell us how application teams adopted the new path and what support they still needed. A sanitized configuration example is optional. Please apply to the Cloud Platform Engineer posting so your résumé is linked to this role.