My process ran a long time—over eight weeks—and it never felt fully coordinated. I started with multiple technical rounds and, in general, I cleared four of them with feedback that was described as good. The interviews themselves reflected a Staff SDET / solutions-team flavor, with both deep domain discussion and hands-on automation thinking.
For the domain portion, the conversations went broad and deep, touching security and networking-style areas like SSL, zero trust, TCP, and CA topics. My automation-focused rounds included things like end-to-end automated testing and an algorithm question, and there was also a coding round delivered by an engineer who seemed to have a very rehearsed approach. I ended up getting the feeling that the team leaned manual-test heavy, with automation handled more primitively than I expected for this level.
3 months ago
Average Negative India
My process started with a recruiter screen where they basically checked my background and experience against what the role needed. After that, I got pulled into technical work that felt very SDET-shaped rather than purely algorithmic. One round had two coding problems—one centered on strings and another involving trees—and I was expected to show a clear approach as I worked through them.
The next stage got more practical. I was asked to create a test plan for a specific feature with P0 coverage, and I also had to debug a flaky automation test scenario, which matched the kind of day-to-day pain around unstable tests. Then I moved into a deeper automation framework design exercise where I had to think end to end: high-level design, how I’d structure directories, what classes and methods I’d create, plus validations and expected outcomes. A hiring-manager conversation followed that focused on past project decisions and how I’d handle tricky challenges. Overall, it felt like a real evaluation of how I build and maintain testing systems.
6 months ago
Average Negative Guadalajara, Jalisco
My interview journey was mostly coding-heavy, but with a sharp edge toward specific tooling and “exact syntax” rather than general problem-solving. Af…
> 1 year
Difficult Negative India
My interview started fairly structured: I first went through a company or department introduction phase and then did a self introduction, tied into th…
> 1 year
Average Positive India
My process felt surprisingly smooth and grounded, starting with an initial conversation that was friendly and targeted. It wasn’t just about checking …
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process can be lengthy, often taking over eight weeks, with multiple technical rounds and limited communication during the waiting periods. Candidates reported feeling uncertain due to long gaps without updates, which can lead to frustration.
TimelineCommunicationProcess Length
Technical Rounds Focus
Candidates experienced a mix of coding challenges and domain-specific questions, particularly around automation, networking, and security topics. The technical interviews often included practical exercises like test planning and debugging flaky tests, reflecting the role's responsibilities.
Coding ChallengesAutomationNetworking
Coding & Tooling Expectations
Interviews emphasized specific coding syntax and familiarity with tools like Unix and Kubernetes, which some candidates found challenging. The focus on exact command knowledge sometimes overshadowed broader problem-solving skills.
UnixKubernetesCoding Syntax
Behavioral & Managerial Conversations
Initial conversations often included a recruiter screen followed by discussions with hiring managers that focused on past experiences and role expectations. Some candidates appreciated the respectful tone and scenario-based questions that aligned with the job's daily tasks.
BehavioralManagerialScenario-Based
Interview Environment & Engagement
Candidates reported mixed experiences regarding interviewer engagement, with some finding the atmosphere supportive while others felt it was unfriendly or disengaged. This inconsistency affected their overall impression of the process.
Interviewer EngagementAtmosphereSupportive vs. Unfriendly
Outcome & Feedback
Many candidates did not receive offers, often citing mismatches in expectations or unclear evaluation criteria. Feedback was sometimes lacking or felt disconnected from their performance, leading to confusion about their standing in the process.