Senior Selenium Test Lead - Java
About this role
Job Summary
| Skill | Category | Requirement | Required expertise |
| MANDATORY SKILLS — all required | |||
| Playwright – UI automation | Test Automation | Mandatory | Locators, auto-waiting, fixtures, parallel execution, trace viewer; functional, integration and E2E coverage |
| TypeScript | Programming | Mandatory | Types, interfaces, async/await, modules, reusable utilities and typed test helpers |
| API automation | Test Automation | Mandatory | REST automation via Playwright request context: auth flows, cookies and tokens, headers, multipart, JSON schema validation |
| Framework development and maintenance | Framework Engineering | Mandatory | Building a framework from scratch; page-object and reusable component patterns; config, utilities, reporting; ongoing refactoring |
| Regression automation | Test Strategy | Mandatory | Suite design and scope selection, stability, execution time control, coverage of critical journeys |
| CI/CD integration | Engineering Practice | Mandatory | Integrating suites into Jenkins, GitHub Actions or Harness; triggers, parallel runs, artifacts, published reporting |
| Debugging, triage and failure analysis | Test Automation | Mandatory | Trace and report analysis; isolating product defects from test defects; root cause of intermittent failures |
| Test data management | Engineering Practice | Mandatory | Repeatable, independent test data; setup and teardown; environment-specific handling |
| Git and version control | Engineering Practice | Mandatory | Branching, pull requests, code review and merge discipline on GitHub or equivalent |
| Test and defect management | Process | Mandatory | JIRA and Xray or equivalent for test cases, execution records and defect tracking |
| Automation coding standards | Framework Engineering | Mandatory | Establishing and upholding standards; reviewing peers' automation code |
| Agile and Scrum delivery | Process | Mandatory | Working within sprints, refinement, estimation and retrospectives |
| Total mandatory weight | |||
| GOOD TO HAVE — none required, used to differentiate between candidates who meet the bar | |||
| Playwright with Python | Test Automation | Good to have | Cross-language capability where a team standardises on Python |
| GCP data validation | Data Validation | Good to have | Verifying behaviour beyond the UI via Pub/Sub events, Cloud Storage and BigQuery read-backs |
| SQL and database validation | Data Validation | Good to have | Querying to validate data created or changed by a test |
| Docker | Engineering Practice | Good to have | Containerised, consistent test execution across environments |
| Contract testing | Test Strategy | Good to have | Consumer-driven contract verification between services |
| Accessibility automation | Test Strategy | Good to have | Automated accessibility assertions within the UI suite |
| Visual regression | Test Strategy | Good to have | Screenshot comparison and visual diffing |
| Performance testing exposure | Test Strategy | Good to have | Awareness of load and performance validation approaches |
| Cross-browser and responsive coverage | Test Automation | Good to have | Executing suites across browser engines and viewports |
| Reporting dashboards | Engineering Practice | Good to have | Allure, Playwright HTML reporting or equivalent published to stakeholders |
Key Responsibilities
| Skill | Category | Requirement | Required expertise |
| MANDATORY SKILLS — all required | |||
| Playwright – UI automation | Test Automation | Mandatory | Locators, auto-waiting, fixtures, parallel execution, trace viewer; functional, integration and E2E coverage |
| TypeScript | Programming | Mandatory | Types, interfaces, async/await, modules, reusable utilities and typed test helpers |
| API automation | Test Automation | Mandatory | REST automation via Playwright request context: auth flows, cookies and tokens, headers, multipart, JSON schema validation |
| Framework development and maintenance | Framework Engineering | Mandatory | Building a framework from scratch; page-object and reusable component patterns; config, utilities, reporting; ongoing refactoring |
| Regression automation | Test Strategy | Mandatory | Suite design and scope selection, stability, execution time control, coverage of critical journeys |
| CI/CD integration | Engineering Practice | Mandatory | Integrating suites into Jenkins, GitHub Actions or Harness; triggers, parallel runs, artifacts, published reporting |
| Debugging, triage and failure analysis | Test Automation | Mandatory | Trace and report analysis; isolating product defects from test defects; root cause of intermittent failures |
| Test data management | Engineering Practice | Mandatory | Repeatable, independent test data; setup and teardown; environment-specific handling |
| Git and version control | Engineering Practice | Mandatory | Branching, pull requests, code review and merge discipline on GitHub or equivalent |
| Test and defect management | Process | Mandatory | JIRA and Xray or equivalent for test cases, execution records and defect tracking |
| Automation coding standards | Framework Engineering | Mandatory | Establishing and upholding standards; reviewing peers' automation code |
| Agile and Scrum delivery | Process | Mandatory | Working within sprints, refinement, estimation and retrospectives |
| Total mandatory weight | |||
| GOOD TO HAVE — none required, used to differentiate between candidates who meet the bar | |||
| Playwright with Python | Test Automation | Good to have | Cross-language capability where a team standardises on Python |
| GCP data validation | Data Validation | Good to have | Verifying behaviour beyond the UI via Pub/Sub events, Cloud Storage and BigQuery read-backs |
| SQL and database validation | Data Validation | Good to have | Querying to validate data created or changed by a test |
| Docker | Engineering Practice | Good to have | Containerised, consistent test execution across environments |
| Contract testing | Test Strategy | Good to have | Consumer-driven contract verification between services |
| Accessibility automation | Test Strategy | Good to have | Automated accessibility assertions within the UI suite |
| Visual regression | Test Strategy | Good to have | Screenshot comparison and visual diffing |
| Performance testing exposure | Test Strategy | Good to have | Awareness of load and performance validation approaches |
| Cross-browser and responsive coverage | Test Automation | Good to have | Executing suites across browser engines and viewports |
| Reporting dashboards | Engineering Practice | Good to have | Allure, Playwright HTML reporting or equivalent published to stakeholders |
Skill Requirements
Other Requirements
Frequently Asked Questions
Is the salary disclosed for the Senior Selenium Test Lead - Java position at HCLTech?
The salary for this Senior Selenium Test Lead - Java role at HCLTech is not publicly listed. Click "Apply Now" to learn more about the compensation package on their official careers page.
Where is the Senior Selenium Test Lead - Java position at HCLTech located?
This Senior Selenium Test Lead - Java role at HCLTech is based in Hyderabad, India. The position is listed as on-site or hybrid. Check the full job description or apply directly to confirm the work arrangement.
How do I apply for the Senior Selenium Test Lead - Java position at HCLTech?
Click the "Apply Now" button on this page. You will be redirected to HCLTech's official application portal hosted on successfactors where you can submit your application directly.
When was the Senior Selenium Test Lead - Java job at HCLTech posted?
This Senior Selenium Test Lead - Java position at HCLTech was posted on Sep 28, 2026. Apply as soon as possible — early applications are often reviewed first.
Senior Selenium Test Lead - Java
HCLTech
You'll be redirected to HCLTech's official application page on successfactors.