Job Title

Job Description – QE Test Lead (Warehouse Automation & WES Domain) Experience: 8–10 YearsLocation: Hyderabad / Hybrid Role Type: Individual Contributor + Technical Domain LeaderMandatory question for candidates: what work they have done on the Material Handling Domain, Warehouse Automation / Warehouse execution systems?Role Summary:We are looking for highly experienced QE Test Leads with deep domain expertise in Material Handling Systems (MHS), Warehouse Execution Systems (WES), and Warehouse Automation to lead quality engineering across complex software–hardware integrated automation solutions. This role goes beyond traditional test leadership. The QE Test Lead is expected to act as a domain enabler and mentor, elevating the overall domain maturity of the QE team, which is currently a known gap. The ideal candidate will: Own end‑to‑end quality for WES and automation solutions Enable and upskill testers on domain workflows, automation logic, and failure modes Drive a high‑automation, AI‑assisted QE strategy with minimal manual testing Lead complex software‑to‑hardware integration testing involving robotics, controls, PLC‑driven systems, and third‑party vendors Key Responsibilities 1. Domain Leadership & Team Enablement (MOST CRITICAL) Act as the domain SME for: Warehouse Execution Systems (WES) Material Handling Systems (MHS) Warehouse Automation and Robotics Enable QE teams to deeply understand: Inbound, outbound, replenishment, picking, packing, sortation, storage, and exception flows Physical vs logical inventory state mismatches Control system handshakes, acknowledgements, and retries Build and continuously refine: Domain playbooks End‑to‑end scenario matrices Failure mode catalogs (happy + unhappy paths) Mentor manual and automation testers to: Design domain‑correct test scenarios Avoid shallow, UI‑only or API‑only testing Actively reduce dependency on a few “domain experts” by scaling domain knowledge across the team 2. End‑to‑End Software–Hardware Integration Testing Lead testing across multi‑system, multi‑vendor automation landscapes, including: WES ↔ WMS / Host systems WES ↔ Robotics / Controls WES ↔ Peripheral automation Hands‑on experience validating integrations with: Robotics vendors: Geek+, AutoStore, NuMove, Movu, Ceratech Peripheral systems: PANDA (Print & Apply) Pick‑to‑Light (PTL) Scanners, conveyors, sorters, VLMs Validate: Message sequencing, acknowledgements, retries, and error recovery Partial failures, degraded modes, and recovery scenarios Latency, throughput, and concurrency impacts Test across: API UI Database Desktop / Control interfaces 3. Automation‑First QE Strategy (Maximum Automation, Minimal Manual) Own and enforce an automation‑first mindset Identify and eliminate unnecessary manual testing Design end‑to‑end automated scenarios that cover: Business workflows Integration points Failure and recovery paths Drive automation across: UI (Angular‑based apps) APIs (microservices) Workflow engines Backend validations Ensure automation is: Stable Maintainable Scalable across projects Tools & Frameworks: Subject7 (Enterprise automation) Playwright Selenium Python scripting for test utilities and data setup 4. Performance, Reliability & Non‑Functional Testing Lead performance and scalability testing for WES and automation solutions Design performance scenarios aligned to real warehouse workloads, including: Peak throughput Concurrent waves Robotics saturation Message backlogs Validate: System stability under load Memory leaks, thread starvation, and message pile‑ups Long‑running endurance and soak tests Drive reliability testing: Failover Restart scenarios Partial system outages Performance Tools: JMeter k6 5. AI‑Enabled Quality Engineering Leverage AI‑assisted testing approaches, especially for: Test case generation Automation optimization Test coverage analysis Use AI to: Reduce manual effort Improve scenario completeness Accelerate automation creation Stay current with emerging AI‑driven QE practices and apply them pragmatically 6. Test Strategy, Governance & Stakeholder Engagement Own QE strategy for assigned products / programs Review and approve: Test plans Automation strategies Regression approaches Ensure strong traceability using: Jira Xray Proactively communicate: Quality risks Release readiness Domain‑specific concerns Partner closely with: Architects Product owners Engineering leads Client stakeholders Technology Stack Application & Platform Spring Boot (Microservices) Camunda (Workflow orchestration) Angular 18 (UI) Testing & QE Jira Xray Subject7 Playwright Selenium JMeter k6 Python (scripting & utilities) Required Skills & Experience Must‑Have 8–10 years in Quality Engineering Strong, hands‑on domain experience in: Warehouse Automation WES / WCS / MHS Proven experience leading software–hardware integration testing Strong automation background with real‑world implementation Solid performance testing experience Experience enabling and mentoring QE teams on domain concepts Nice‑to‑Have Prior experience in automation‑heavy warehouse programs Exposure to PLC / control system concepts (no coding required) Experience with AI‑assisted testing approaches Client‑facing experience in automation programs What Success Looks Like in This Role QE team demonstrates strong domain understanding, not just test execution Significant reduction in domain‑related defect leakage Automation coverage increases release over release Manual testing effort reduces without quality compromise QE is seen as a domain partner, not a downstream function