Quality Assurance Engineer (ITOM)
Hewlett Packard Enterprise (HPE) (company site, opens in a new tab)3+ yrsHyderabadOn-siteDirect career pageEst. 10–18 LPA
Posted 1d ago
Reach people at Hewlett Packard Enterprise (HPE)
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at Hewlett Packard Enterprise (HPE) you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Own quality engineering for IT infrastructure discovery, monitoring, topology/service mapping, events, alerts, and incident workflows.
- Define risk-based test strategies and validate end-to-end behavior across infrastructure, collectors, integrations, APIs, data processing, and the user interface.
- Investigate complex defects, build reproducible test environments and automation, and communicate release risks and coverage gaps to Product and Engineering.
Minimum Requirements
- Work Experience Required: 3+ years of hands-on QA experience; ITOM, infrastructure monitoring, observability, or enterprise infrastructure experience is preferred.
- Strong enterprise infrastructure understanding and hands-on experience testing infrastructure discovery, monitoring, and configuration-management capabilities; familiarity with discovery methods such as SNMP, WMI, SSH, REST APIs, or agents.
- REST API testing experience and ability to use Python, JavaScript, or Shell scripting for automation, data validation, or troubleshooting.
- Role is designated onsite, with an expectation to primarily work from an HPE office.
Ideal Candidate Profile
- Has tested ITOM or similar infrastructure platforms and can reason across servers, networks, storage, virtualization, cloud, and hybrid environments.
- Can validate operational workflows and failure/recovery scenarios, including discovery accuracy, stale or missing metrics, topology changes, event correlation, and integration failures.
- Uses exploratory, risk-based testing and technical evidence to trace issues across components; can build reliable automation and work through evolving requirements.