/ TEAMS · VMware / vSphere Engineering
Source engineers who can operate established VMware estates, improve recovery and capacity, and execute carefully staged virtualization migrations or modernization.
2,000+ engineers in our active talent network · Regional recruiters
/ SYSTEM STACK
ESXi · VM lifecycle · vMotion
vCenter · Clusters · DRS / HA
Datastores · vSAN · Backup
vDS · VLAN · NSX integration
Assessment · Migration · Rollback
/ AVAILABLE TO HIRE
Profiles show the experience we can source. Individual candidate availability is confirmed after enquiry.
Senior VMware vSphere Engineer — ESXi & Migration
Available14+ years of experience · Poland
VMware vSphere Engineer — ESXi & Migration with 14 years in production systems, focused on VMware vSphere Engineer — ESXi & Migration and Production systems.
Languages: Polish, English B2+
Mid-level VMware vSphere Engineer — ESXi & Migration
Inquire availability3+ years of experience · Czechia
VMware vSphere Engineer — ESXi & Migration with 3 years in production systems, focused on Production systems and Technical delivery.
Languages: Czech, English B2+
Mid+ VMware vSphere Engineer — ESXi & Migration
Available6+ years of experience · Serbia
VMware vSphere Engineer — ESXi & Migration with 6 years in production systems, focused on Technical delivery and VMware vSphere Engineer — ESXi & Migration.
Languages: Serbian, English B2+
Senior VMware vSphere Engineer — ESXi & Migration
Inquire availability7+ years of experience · Romania
VMware vSphere Engineer — ESXi & Migration with 7 years in production systems, focused on VMware vSphere Engineer — ESXi & Migration and Production systems.
Languages: Romanian, English B2+
/ Engineering teams
Onectus recruits across Linux, Ceph storage, private cloud and virtualization specializations. A VMware/vSphere engagement is scoped for its own ESXi/vCenter landscape, support model, licensing constraints and migration needs. Candidate experience is checked against the specific environment and operational duties.
/ Technical specializations
Focus on real platform responsibilities such as vCenter configuration, HA, datastore dependencies, network connectivity and repeatable recovery rather than a generic VM administration title.
Host lifecycle, vCenter inventory, resource pools, roles, templates, updates and configuration baselines.
Cluster capacity, host admission control, vMotion, DRS placement and incident behavior.
Datastores, multipathing, vSAN architecture, VM storage policies, snapshots and performance.
vSphere Distributed Switch, VLAN, uplinks, virtual NICs, NSX touchpoints and network fault isolation.
VM-consistent backup, recovery validation, RPO/RTO, restore testing and infrastructure hardening.
Inventory and dependency mapping, platform transitions, compatibility testing, cutover and rollback.
/ Project scenarios
Standardize host configuration, improve observability and plan supported upgrades.
Validate HA/DRS behavior, capacity policies, maintenance procedures and failure recovery.
Assess guest, storage, network and downtime dependencies for a controlled transition.
Correlate datastore, hypervisor scheduling, uplink and guest symptoms.
/ Practical evaluation
A senior platform engineer should explain failure scenarios, real capacity tradeoffs and how a change was executed without disrupting workloads.
What clusters, patch cycles, HA/DRS policies and host lifecycle changes were owned?
Can they trace VM latency through datastores, multipathing, vDS and guest behavior?
How were VMs classified, compatibility assessed, rollback rehearsed and cutovers sequenced?
What restore tests, role policies, audits and production safeguards were implemented?
/ Sourcing process
vSphere versions, vCenter, nodes, vSAN/storage, networks, backups and target outcome.
Find VMware engineers with environment-specific operation or migration experience.
Assess incidents, HA/DRS, network/storage paths, recovery and migrations.
Align maintenance windows, access, location, onboarding and availability.
Profiles, availability and engagement terms are confirmed for each request.
/ Questions
Yes. Define inventory, compatible guest OS, network/storage mapping, allowed downtime and the destination so we screen relevant migration experience.
Yes when required. We separately assess hypervisor operation, cluster management and storage architecture to avoid broad but shallow matches.
Potentially. Specify NSX products, virtual networking ownership and the handoff with your networking team.
Share vSphere/ESXi versions, cluster scale, backup design, storage/networking, operational ownership and target migration dates.
/ Onectus · TEAMS
Tell us the technology, production responsibilities, experience level and working model. We'll activate the appropriate engineering sourcing channels.
