OpenShift Engineer/Consultant (Architecture & Cluster Engineering)

The ideal candidate for this OpenShift Engineer role will be responsible for the architecture, design, engineering, deployment, and ongoing optimization of enterprise OpenShift environments supporting Customer’s Platform-as-a-Service (PAAS) offerings.

This is not primarily an OpenShift application support or cluster administration role. Candidates should have demonstrated hands-on experience designing and implementing OpenShift/Kubernetes platforms, preferably in greenfield environments., * Strong hands-on OpenShift architecture and engineering experience.

• Demonstrated experience designing and building OpenShift clusters from the ground up, not solely administering existing environments.
• Experience with OpenShift cluster installation, configuration, topology, and infrastructure planning.
• Strong understanding of OpenShift/Kubernetes architecture, including control plane, worker nodes, operators, networking, storage, and cluster services.
• Experience making VM sizing, compute, memory, storage, and capacity planning decisions for OpenShift clusters.
• OpenShift Administration.
• OpenShift Data Foundation.
• OpenShift Platform Plus.
• Advanced Cluster Management (ACM).
• Advanced Cluster Security (ACS).
• Ceph Administration.
• Extensive knowledge of Linux containers/Docker, Kubernetes, and containerized application/microservices architectures.
• Strong understanding of enterprise networking concepts including protocols, firewalls, load balancers, ingress, routing, and connectivity.
• Experience with automated deployment and infrastructure automation tools.
• Conceptual and applied understanding of DevOps concepts, tools, and practices.
• Hands-on experience with CI/CD tools such as GitLab.
• Experience designing platforms capable of supporting enterprise-scale workloads, high availability, and resiliency.
• Strong analytical and troubleshooting skills with the ability to work across multiple technical projects.
• Ability to communicate complex technical concepts and architecture decisions to technical and non-technical stakeholders.
• Willingness to document solutions, share knowledge, and train other team members.