The interviewer asked anything whatever came to his mind. SQL,Selenium,SOAP,REST,Agile,Unix,Linux,windows,manual testing concepts, anything. There were so many things which I never heard of in any interview,or are usually not asked in interview.They were not even related to the opening.
In the first screening call, I was asked what differentiates a good QA engineer from a bad one. The second interview was more technical, focusing on how I approached tasks and challenges in my previous role.
Shuffle the deck of card and return a random array
Assessment Details: Objective: To assess UI automation and coding proficiency Tool & Language: Playwright + JavaScript/TypeScript Task: Choose any website Create at least 10 unique test cases Use a standard test runner (e.g., Jest or Playwright’s built-in) Document how to set up and run the project No use of BDD tools like Cucumber or SpecFlow Evaluation Criteria: Code quality and SOLID principles Test design techniques Adherence to best practices Clarity of setup documentation Submission: GitHub public repo or Google Drive link (no GitLab) Timeline: 4 days I completed the task and submitted it on time, but unfortunately, I was rejected. I wasn’t given specific feedback on what went wrong, so I’m unsure where I fell short.
What are you doing currently in the job and why are you looking for a change
- What is best approach for agile ? - How you deal with non reproducible bugs ? - Terms and methodologies. Many mores
qa related questions and few on automation and java
1.About previous Experience,Technologies,Processes,Testing Skills.
hexadecimal to decimal Ether type values How TTL used in DNS Radius Port mirroring
Coding round was unexpected. They asked me to write a sorting algorithm, some previous question, writing and reading from a file
Viewing 111 - 120 interview questions