/ TEAMS · KubeVirt Engineering
Define virtual-machine workloads, CDI disk imports, storage classes, Multus networking, live migration and cluster version. KubeVirt experience is not identical to generic Kubernetes operations.
2,000+ engineers in our active talent network · Regional recruiters
/ SYSTEM STACK
Kubernetes · Operators · CRDs
KubeVirt · virt-launcher · QEMU/KVM
CDI · DataVolumes · Imports
CNI / Multus · CSI · StorageClasses
Live migration · HA · Observability
/ AVAILABLE TO HIRE
Profiles show the experience we can source. Individual candidate availability is confirmed after enquiry.
Mid+ KubeVirt Engineer — Kubernetes Virtual Machines
Inquire availability5+ years of experience · Lithuania
KubeVirt Engineer — Kubernetes Virtual Machines with 5 years in production systems, focused on KubeVirt Engineer — Kubernetes Virtual Machines and Production systems.
Languages: Lithuanian, English B2+
Senior KubeVirt Engineer — Kubernetes Virtual Machines
Available11+ years of experience · Poland
KubeVirt Engineer — Kubernetes Virtual Machines with 11 years in production systems, focused on Production systems and Technical delivery.
Languages: Polish, English B2+
Senior KubeVirt Engineer — Kubernetes Virtual Machines
Available14+ years of experience · Bulgaria
KubeVirt Engineer — Kubernetes Virtual Machines with 14 years in production systems, focused on Technical delivery and KubeVirt Engineer — Kubernetes Virtual Machines.
Languages: Bulgarian, English C1
Mid-level KubeVirt Engineer — Kubernetes Virtual Machines
Available3+ years of experience · Bulgaria
KubeVirt Engineer — Kubernetes Virtual Machines with 3 years in production systems, focused on KubeVirt Engineer — Kubernetes Virtual Machines and Production systems.
Languages: Bulgarian, English B2+
/ Specialist sourcing
Define virtual-machine workloads, CDI disk imports, storage classes, Multus networking, live migration and cluster version. KubeVirt experience is not identical to generic Kubernetes operations.
Ask for an actual VM migration or storage-performance investigation and how the engineer handled node failure, networking and operator upgrades.
Role-specific sourcing, not a promise of current candidate availability.
/ Engineering teams
Our cloud infrastructure recruiting experience includes Ceph storage and private-cloud engineering searches. KubeVirt adds specific Kubernetes control-plane, VM lifecycle, storage and networking responsibilities. We assess each candidate's experience in those layers rather than treating all hypervisor specialists as interchangeable.
/ Technical specializations
A Kubernetes-native virtualization role must account for declarative VM resources, storage claims, multi-network attachments and availability behavior across the cluster.
VirtualMachine and VirtualMachineInstance resources, virt-controller, virt-launcher, scheduling and machine maintenance.
CDI DataVolumes, disk imports and cloning, snapshots, storage access modes and image pipelines.
Pod networking, Multus secondary interfaces, bridged/SR-IOV networking and reachability.
StorageClasses, PVCs, volume modes, Ceph RBD where applicable and migration-ready data paths.
Live migration preconditions, eviction strategies, HA expectations and node draining.
Cluster upgrades, RBAC, observability, capacity, network policies and incident recovery.
/ Project scenarios
Assess guest compatibility, disk import, network attachment and cutover strategy.
Define tenant boundaries, storage access, scheduling and lifecycle automation.
Trace shared storage, network continuity, CPU compatibility and node constraints.
Handle upgrades, node maintenance, metrics, VM availability and recoverability.
/ Practical evaluation
Look for cluster-level evidence: precise CRDs, storage design, VM lifecycle and incident diagnostics, not just Kubernetes badges.
Can they explain VMI scheduling, virt-launcher and operator-managed lifecycle changes?
Have they diagnosed CDI, PVC/storage mode issues and migration blockers?
Can they explain Multus, secondary networks, CNI behavior and VM guest reachability?
What upgrades, failures, cluster policies and capacity decisions have they managed?
/ Sourcing process
Kubernetes distribution, KubeVirt version, guest OS, storage/CSI, networks and SLAs.
Identify engineers with verified KubeVirt and Kubernetes operations experience.
Review VMI, CDI, networking, migrations, incident and automation examples.
Agree environment access, change windows, availability and working arrangements.
Profiles, availability and engagement terms are confirmed for each request.
/ Questions
Not entirely. KubeVirt relies on Kubernetes resources, operators, CNI, CSI and workload scheduling; familiar hypervisor concepts alone do not cover production operation.
Yes. Describe your VM inventory, image formats, DataVolume flows, storage access modes and target cutover conditions.
Yes. Specify the storage model and CSI/RBD integration; relevant production experience is evaluated per engineer.
Potentially. Clarify whether responsibility includes cluster networking/storage, KubeVirt operators, guests or application teams.
/ Onectus · TEAMS
Tell us the technology, production responsibilities, experience level and working model. We'll activate the appropriate engineering sourcing channels.
