Taro Logo

Software Quality Assurance Engineer Interview Experience

October 1, 2021
Negative ExperienceNo Offer

Process

The first round was a 1-hour technical coding round, which happened on the third attempt. The first time it was cancelled on the day of the interview. The second time, no one showed up for the interview, and no information was provided. The HR representative was also unaware of the situation.

After selection in the first round, there was a virtual onsite technical interview that was 3 hours long:

  • 1 hour for algorithm and technical Selenium coding, and behavioral questions.
  • 1 hour for QA approach and philosophical questions.
  • 30 minutes to meet with engineering team members to get to know the team better.
  • 30 minutes for a retro meet-up with the QA manager.

The entire process took more than 2 months, and the recruiter experience was really bad.

Questions

CoderPad round technical coding round: There was a REST API framework along with a few test cases to automate. Write test scripts using your preferred language.

Algorithm (Easy): Missing number in the array.

Selenium pseudo code: Window handling scenario.

Lot of behavioral questions:

  • How do you fit yourself in a team?
  • Who is responsible for the quality of a product?
  • Tell me a time you handled conflict with a manager.
  • Major challenges faced during automation.
  • What are the steps followed when you find a bug? And many more...

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Checkr Software Quality Assurance Engineer role in United States.

Success Rate

0%
Pass Rate

Checkr's interview process for their Software Quality Assurance Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Checkr's Software Quality Assurance Engineer interview process in United States.

Checkr Work Experiences