Requirements
Required Skills & Qualifications:Education: Bachelor's degree in computer science, Computer Engineering, Information Technology, or a closely related technical system discipline.Core Engineering Track Record: Deep, practical engineering experience managing production-grade Red Hat OpenShift clusters and administering IBM Cloud Pak for Integration (CP4I) components.Architecture & Pattern Competency: Solid knowledge of Software-Defined Networking (SDN/OVN), Ingress/Route architectures, service meshes (Istio), network policies, and container security compliance scanning.Security & Protocol Familiarity: Strong technical comprehension of enterprise integration patterns, containerized message-queuing mechanics, and API lifecycle architectures.Analytical Evaluation: Exceptional analytical and systemic debugging capabilities, possessing a high technical attention to container density logs and compute sizing variables.Technical Toolkit & Systems:Core Development Environments: Red Hat OpenShift Container Platform (RHOCP), OKD, Kubernetes, CoreOS, IBM CP4I, IBM MQ, API Connect, ACE, Event Streams, DataPower.Programming Languages & UI Engines: Linux CLI, Bash, Python scripting, OpenShift CLI (oc), kubectl.Networking, Core APIs & Engines: Red Hat OpenShift Data Foundation (ODF), Ceph, Portworx, CSI plugins, AWS EBS/EFS.Dependency & Repository Managers: Ansible, Terraform, ArgoCD, Helm Charts, Customize, OLM Operators, Jenkins, GitLab CI/CD, Tekton, Prometheus, Grafana, OpenShift Logging, Sysdig.Enterprise Project Management Suites: Jira, Azure DevOps (ADO), or Microsoft TFS.Collaboration & Soft Skills:High-Stakes Resolution & Composure: Maintains absolute composure and structured focus when critical, production cluster failures or microservice outages emerge. Coordinates systematic fixes and clear mitigation strategies under pressure, keeping high-availability platforms operational.Distributed Workspace Collaborative Partner: Highly capable of performing smoothly across remote or hybrid team environments, translating complex container infrastructure realities into actionable deployment guidelines for integration teams.Pristine Quality Advocate: Constantly champions structural automation, infrastructure-as-code consistency, and strict platform compliance, steering teams away from localized, manually modified configuration anti-patterns.Language & Communication Excellence: Fluent English (written and verbal) is required. Spoken and written Arabic is highly advantageous and preferred.
Description
Position Overview:The IBM CP4I OpenShift Operations/Administrator is a systems infrastructure specialist responsible for designing, deploying, securing, and maintaining our enterprise hybrid-cloud integration architecture. Sitting at the intersection of Cloud DevOps and Middleware Engineering, this role focuses on the end-to-end administration of IBM Cloud Pak for Integration (CP4I) running on Red Hat OpenShift Container Platform (RHOCP) to guarantee high availability and continuous automated pipeline scaling.Core Responsibilities:Cluster & CP4I Deployment: Plan, architect, install, and configure Red Hat OpenShift clusters across hybrid cloud environments, provisioning the core IBM Cloud Pak for Integration (CP4I) platform using Operator Lifecycle Managers (OLM).Integration Component Management: Manage and lifecycle-configure core CP4I capabilities via their respective IBM operators, including IBM MQ, API Connect, App Connect (ACE), Event Streams (Kafka), and Aspera.Security & Identity Governance: Secure cluster infrastructures by enforcing Role-Based Access Control (RBAC), managing Red Hat OpenShift OAuth integrations, Keycloak/IAM identity layers, and SSL/TLS certificate configurations.Compute, Storage & Lifecycle: Architect container persistent storage layers using Software-Defined Storage engines and schedule seamless cluster upgrades, security patching, and node updates with a zero-downtime objective.Performance Diagnostics & Triage: Configure APM surveillance dashboards, automate multi-tenant provisioning using GitOps paradigms, and systematically troubleshoot complex cluster degradation events, persistent volume failures, and pod networking drops.