Companies / HCLTech
HCLTech practice pack
IT services. 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.
Skills this role is usually tested on
- Automation framework design
- API and database testing
- Embedded or product testing basics
- CI/CD
- Debugging
Business areas used for scenarios
- engineering services
- BFSI
- healthcare
- software products
6 questions
Answer out loud first, then open the guide. Most people read the guide too early.
- 1
How do you design reporting so that a failure tells you why, not just that it failed?
mediumFrameworkA strong answer covers
Attach screenshot, console and network logs, test data id, build and environment, and step names in business language. Group failures by cause.
- 2
After a UI action you must verify the database state. How do you do it safely?
mediumDatabaseA strong answer covers
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.
- 3
A test fails once in fifty runs. Walk through your approach.
hardDebuggingA strong answer covers
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.
- 4
How do you test an API that is paginated and sorted?
mediumAPI testingA strong answer covers
First, last and middle pages, page size limits, stable sort with ties, adding or deleting while paging, invalid cursors, and total count consistency.
- 5
Write a function that finds duplicate records in a list of dicts by a key and explain how you would test it.
mediumPython or JavaA strong answer covers
Use a set or counter keyed on the field, return the repeats. Tests: empty, none, all duplicates, missing key, differing case, large input.
- 6
What should a pull request check run for a test repository?
mediumCI/CDA strong answer covers
Lint, unit tests for helpers, a smoke subset, and a dry-run of the suite collection. Fast enough that people wait for it.
Now say it to an interviewer
Reading a guide is not the same as answering under a clock. Run a mock interview and get scored feedback.