/ TEAMS · OpenShift Platform Engineering
Specify OpenShift version, operators, GitOps, cluster authentication, networking, RBAC and upgrade policies. Experience with generic Kubernetes alone may not cover enterprise OpenShift constraints.
2,000+ engineers in our active talent network · Regional recruiters
/ SYSTEM STACK
OpenShift · Kubernetes · Operators
GitOps · Pipelines · Images
Routes · Ingress · OVN-Kubernetes
RBAC · SCC · Identity
etcd · Upgrades · SRE
/ AVAILABLE TO HIRE
Profiles show the experience we can source. Individual candidate availability is confirmed after enquiry.
Mid-level OpenShift Platform Engineer — Operators & GitOps
Available3+ years of experience · Romania
OpenShift Platform Engineer — Operators & GitOps with 3 years in production systems, focused on OpenShift Platform Engineer — Operators & GitOps and Production systems.
Languages: Romanian, English B2+
Mid+ OpenShift Platform Engineer — Operators & GitOps
Inquire availability5+ years of experience · Poland
OpenShift Platform Engineer — Operators & GitOps with 5 years in production systems, focused on Production systems and Technical delivery.
Languages: Polish, English C1
Senior OpenShift Platform Engineer — Operators & GitOps
Inquire availability9+ years of experience · Czechia
OpenShift Platform Engineer — Operators & GitOps with 9 years in production systems, focused on Technical delivery and OpenShift Platform Engineer — Operators & GitOps.
Languages: Czech, English B2+
Senior OpenShift Platform Engineer — Operators & GitOps
Available12+ years of experience · Serbia
OpenShift Platform Engineer — Operators & GitOps with 12 years in production systems, focused on OpenShift Platform Engineer — Operators & GitOps and Production systems.
Languages: Serbian, English B2+
/ Specialist sourcing
Specify OpenShift version, operators, GitOps, cluster authentication, networking, RBAC and upgrade policies. Experience with generic Kubernetes alone may not cover enterprise OpenShift constraints.
Assess a controlled cluster upgrade, operator failure or policy issue and how the specialist maintained service availability.
Role-specific sourcing, not a promise of current candidate availability.
/ Engineering teams
Onectus sources infrastructure and cloud-native engineering specialists, including OpenStack, Ceph and Kubernetes-adjacent virtualization. OpenShift requires platform-specific operational knowledge—operator lifecycle, security controls, cluster upgrades and networking—validated separately for every candidate.
/ Technical specializations
An enterprise OpenShift role is not just generic Kubernetes administration. Cluster versioning, SCC policy, CVO/operator health and integration with infrastructure have their own failure modes.
Cluster Version Operator, Operator Lifecycle Manager, release channels, component health and change windows.
Deployments, BuildConfigs where used, Argo CD/OpenShift GitOps, Pipelines and image lifecycle.
RBAC, Security Context Constraints, service accounts, identity providers and policy enforcement.
OpenShift Routes, IngressControllers, OVN-Kubernetes, NetworkPolicy and service connectivity.
CSI drivers, PVCs, storage classes, Ceph-backed storage as applicable and node operations.
Monitoring/Alertmanager, logging, etcd health, capacity, failure investigation and recovery.
/ Project scenarios
Assess operator compatibility, machine pools, rollout sequencing and rollback constraints.
Establish promotion workflows, RBAC boundaries, secrets handling and workload health checks.
Trace Routes, OVN, DNS, network policies and services across platform layers.
Improve operator alerts, etcd monitoring, node capacity, storage and incident runbooks.
/ Practical evaluation
Review real platform events, not Kubernetes terminology alone: OpenShift upgrades, operator health, Routes, SCC and day-two production responsibilities.
Can they explain CVO/OLM status, degraded operators and upgrade blockers?
How did they manage SCC, identities, namespace RBAC and workload admission?
Can they investigate OVN-Kubernetes, Routes, CSI/PVC or node disruptions?
What GitOps changes, monitoring, incidents and recovery drills were owned?
/ Sourcing process
OpenShift version, deployment model, operators, storage/network, IAM and SLOs.
Identify OpenShift engineers with verified cluster operation experience.
Discuss upgrades, SCC, OVN, GitOps, storage, monitoring and incident resolution.
Align platform access, change windows, on-call, availability and collaboration.
Profiles, availability and engagement terms are confirmed for each request.
/ Questions
OpenShift adds platform-specific operators, upgrades, Routes, SCC, identity and managed enterprise controls that require hands-on experience.
Yes. Explain your deployment model, workload promotion practices, policies and how application teams interact with the platform.
Yes where required. Specify CSI, storage backend, OVN-Kubernetes, Routes and integration responsibilities.
Yes. We screen experience with operator compatibility, staged changes, incident response and agreed support boundaries.
/ Onectus · TEAMS
Tell us the technology, production responsibilities, experience level and working model. We'll activate the appropriate engineering sourcing channels.
