IT services
HCLTech
Automation depth with engineering and product testing.
These are our own practice questions for the kind of QA/SDET role this company hires for. They are not the company's real interview questions. Confirm the current process on the company's official careers page.
What they tend to probe
- Automation framework design
- API and database testing
- Embedded or product testing basics
- CI/CD
- Debugging
Question 1 · Framework · Medium
How do you design reporting so that a failure tells you why, not just that it failed?
Answer guide
Attach screenshot, console and network logs, test data id, build and environment, and step names in business language. Group failures by cause.
Question 2 · Database · Medium
After a UI action you must verify the database state. How do you do it safely?
Answer guide
Read-only credentials, query by a unique key created in the test, wait with a bounded poll, never depend on row order, and clean up through the app or API.
Question 3 · Debugging · Hard
A test fails once in fifty runs. Walk through your approach.
Answer guide
Capture state on failure, run it in a loop locally, add structured logs, look for shared data, timing, ordering and resource limits. Fix the cause, then prove it with a long run.
Question 4 · API testing · Medium
How do you test an API that is paginated and sorted?
Answer guide
First, last and middle pages, page size limits, stable sort with ties, adding or deleting while paging, invalid cursors, and total count consistency.
Question 5 · Python or Java · Medium
Write a function that finds duplicate records in a list of dicts by a key and explain how you would test it.
Answer guide
Use a set or counter keyed on the field, return the repeats. Tests: empty, none, all duplicates, missing key, differing case, large input.
Question 6 · CI/CD · Medium
What should a pull request check run for a test repository?
Answer guide
Lint, unit tests for helpers, a smoke subset, and a dry-run of the suite collection. Fast enough that people wait for it.