Taro Logo

Software Development Engineer in Test (SDET) Interview Experience

December 1, 2025
Negative ExperienceNo Offer

Process

I applied through a recruiter. The process took 3 days.

The interview was rushed. I felt like I was being interrogated. It felt like the interviewers didn’t know how to solve the problems at their job and were instead trying to extract ideas for solutions for free. At the same time, I felt uncomfortable because they kept asking me the same questions, as if they were trying to expose me, and their tone was unfriendly. I still didn’t understand what they were doing, but I clearly remembered phrases like "we don’t trust our developers," "our developers don’t want to improve quality," and "there’s a lot of bad code and we don’t know what to do about it."

At a certain point, I realized I didn’t want to work there and asked to end the interview. It is also worth saying there was nothing about software testing at the interview; they seemed to be looking for someone who could do the DevOps and CI/CD stuff for them.

Questions

There was a lot of stuff about how they made their CI/CD without telling you how they made their CI/CD, so it was purely a guessing game. Then they showed me bad code with bugs and asked me to find issues. I found some, but they weren't satisfied.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Tabby Software Development Engineer in Test (SDET) role.

Success Rate

0%
Pass Rate

Tabby's interview process for their Software Development Engineer in Test (SDET) roles is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Tabby's Software Development Engineer in Test (SDET) interview process.

Tabby Work Experiences