/ TEAMS · Specialist engineering · Kubernetes
Source engineers experienced in Kubernetes orchestration, workloads, networking, storage and cluster SRE. for business-critical production systems, safe integrations and measurable technical ownership.
2,000+ engineers in our active talent network · Regional recruiters
/ SYSTEM STACK
Kubernetes controllers and workloads
CNI cluster networking
CSI persistent storage
RBAC and admission policies
Helm and GitOps
/ AVAILABLE TO HIRE
Profiles show the experience we can source. Individual candidate availability is confirmed after enquiry.
Mid-level Kubernetes Engineer
Available3+ years of experience · Romania
Kubernetes Engineer with 3 years in production systems, focused on Kubernetes controllers and workloads and CNI cluster networking.
Languages: Romanian, English B2+
Mid+ Kubernetes Engineer
Available5+ years of experience · Romania
Kubernetes Engineer with 5 years in production systems, focused on CNI cluster networking and CSI persistent storage.
Languages: Romanian, English B2+
Senior Kubernetes Engineer
Inquire availability13+ years of experience · Czechia
Kubernetes Engineer with 13 years in production systems, focused on CSI persistent storage and RBAC and admission policies.
Languages: Czech, English B2+
Senior Kubernetes Engineer
Available8+ years of experience · Lithuania
Kubernetes Engineer with 8 years in production systems, focused on RBAC and admission policies and Helm and GitOps.
Languages: Lithuanian, English C1
/ Engineering teams
Onectus uses its active engineering network and regional recruiting partners to search against concrete systems, environments and responsibilities. We evaluate practical experience rather than treating a framework mention or certification as proof of delivery. Particular availability and engagement terms are confirmed after an enquiry. For this role, practical knowledge of Kubernetes controllers and workloads, CNI cluster networking, CSI persistent storage helps define the engineering search.
/ Technical specializations
The right profile depends on your actual architecture, performance constraints, integration boundaries and operational responsibilities.
Kubernetes responsibilities include kubernetes controllers and workloads, related cni cluster networking, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Kubernetes responsibilities include cni cluster networking, related csi persistent storage, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Kubernetes responsibilities include csi persistent storage, related rbac and admission policies, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Kubernetes responsibilities include rbac and admission policies, related helm and gitops, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Kubernetes responsibilities include helm and gitops, related cluster upgrades and sre, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Kubernetes responsibilities include cluster upgrades and sre, related kubernetes controllers and workloads, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
/ Project scenarios
Recover a degraded production cluster. Define constraints around kubernetes controllers and workloads, map dependencies and test how the proposed implementation behaves under real operating conditions.
Improve workload autoscaling. Define constraints around cni cluster networking, map dependencies and test how the proposed implementation behaves under real operating conditions.
Strengthen tenant isolation. Define constraints around csi persistent storage, map dependencies and test how the proposed implementation behaves under real operating conditions.
Run reliable Kubernetes upgrades. Define constraints around rbac and admission policies, map dependencies and test how the proposed implementation behaves under real operating conditions.
/ Practical evaluation
A senior engineering interview should surface directly relevant implementation details, debugging history and operational judgment.
Describe a production issue involving Kubernetes controllers and workloads and what evidence led to a fix.
Which decisions around CNI cluster networking and CSI persistent storage were you personally accountable for?
Describe a production issue involving CSI persistent storage and what evidence led to a fix.
Which decisions around RBAC and admission policies and Helm and GitOps were you personally accountable for?
/ Sourcing process
Define platform versions, deployment constraints, traffic patterns, required integrations and ownership.
Search the active network and partner channels for platform-specific engineering experience.
Discuss real systems, code or configuration decisions, troubleshooting and change control.
Confirm role boundaries, location or remote access, availability, security and interviews.
Profiles, availability and engagement terms are confirmed for each request.
/ Questions
Yes. Tell us the relevant versions, operational environment and the responsibilities connected to Kubernetes controllers and workloads. We qualify hands-on experience during each search.
These can be included when central to the project. We distinguish practical implementation work from general familiarity and ask about failure scenarios and testing.
We look at production decisions, trade-offs, incident diagnosis, code or infrastructure ownership and the ability to explain decisions without relying on a technology checklist.
Share your architecture, technical constraints, collaboration model and priorities. We can then discuss relevant sourcing channels, evaluation criteria and next steps.
/ Onectus · TEAMS
Tell us the technology, production responsibilities, experience level and working model. We'll activate the appropriate engineering sourcing channels.
