Core objective

- 8+ years of design experience or extensive contributions to an automation framework that configures hypervisor hosts and guest VMs at scale.

- Cover the workflow from bare-metal bootstrap through host configuration, VM configuration, and VM/image lifecycle management.

- Be able to propose and defend architecture decisions around the automation.

Core Hypervisor Experience – Mandatory

- ESXi:

hands-on production experience, including vSphere API/vR OPS, PowerCLI, etc.;

OR

- KVM-based platform:

production expertise in at least one platform such as Proxmox, oVirt, Morpheus, OpenStack/libvirt-based environments.

- Evidence of managing and setting up hypervisor hosts at scale. The attached JD targets

100s–1000s of hosts

, not only a few centralized systems.

Declarative / IaC – Mandatory

- Declarative or idempotent tooling/programming to configure hypervisor hosts and define VM state as code.

- Automation that communicates directly with hypervisor-native APIs or CLIs rather than only public-cloud resources.

Testing and plan-before-apply / dry-run discipline before production changes.

- Understanding of Git repository structures, state files, modules, environments, drift detection and reconciliation.

- Must understand how the hypervisor automation flow is built; design input is strongly valued.

Bare-Metal / Hardware Automation – Mandatory

- PXE/iPXE boot automation; kickstart or autoinstall files.

- BMC protocol experience: Redfish APIs and/or HPE iLO, Dell iDRAC, or equivalent vendor BMC exposure.

- Firmware/BIOS configuration through APIs is relevant.

Networking & Storage as Code – Mandatory





- Declarative automation involving vSwitch/distributed switch or Linux bridge/OVS, VLAN and/or VxLAN.

- Storage provisioning such as datastores, LVM, ZFS or Ceph as part of the automation pipeline.

Nice-to-Have

- OpenStack / oVirt / libvirt.

- Python / Go / PowerShell.

- VM lifecycle automation.

- Drift detection/reconciliation.

- Technical architecture experience.

- The attached JD also identifies VM lifecycle management via API and programming experience as useful additional signals.

Must-Have

- Hypervisor experience:

ESXi OR a qualifying KVM-based platform such as Proxmox/oVirt/OpenStack/libvirt.

- Hypervisor automation:

actual automation experience, not operations/support only.

- IaC / declarative/idempotent approach.

- PowerCLI OR hypervisor-native APIs/CLIs.

- PXE/iPXE provisioning.

- Redfish / iLO / iDRAC.

- Storage automation.

- Networking automation.

- Large-scale host management:

100+ hosts should be the baseline search signal; attached JD describes 100s–1000s.

- Architecture/design capability:

Should be able to explain and defend automation design decisions.

PREFERRED

- OpenStack / oVirt / libvirt

– preferred, not mandatory if another qualifying hypervisor platform is robust.

- Python / Go / PowerShell

– preferred; exact language can vary if you have equivalent automation/programming capability.

- VM lifecycle automation

– preferred.

- Drift detection/reconciliation

– strongly preferred; (Broader state-management/IaC discipline).

- Exact technology within a mandatory category

– flexible where the client explicitly allows alternatives, e.g., ESXi OR KVM platform.

📌 Senior Infrastructure / Platform Engineer (Bengaluru)
🏢 AppExert
📍 Bengaluru