I applied through a recruiter. The process took 1 week.
There were 4 rounds in total. 1. Technical Round: This was the first level, where questions were asked on Java and Selenium. They did not ask about API or mobile testing in this round. 2. Assignment Round: After clearing Round 1, they conduct a drive for the subsequent rounds on a single day (usually Saturday). In this round, you and other participants join a call where the interviewer explains the problem statement. After that, each person receives instructions and then moves to a separate breakout room to work independently for about 2 hours. During my assessment, the problem was to automate several processes on an e-commerce website: search for a product, sort results, assert whether sorting is correct, apply filters, and then assert that all products shown fit within the filter criteria.
Technical Round 3 with Engineering Manager (EM): If you pass Round 2, you move to a 30-minute discussion with the Engineering Manager. One thing I found odd was that although BrowserStack shares topics for each round to help candidates prepare, Round 3 did not stick to those topics. The interviewer asked questions that were not relevant to my role or my opening. Even though I answered the majority of questions, the interviewer focused more on those I couldn’t answer. For example, I generated 14–15 test cases across different testing types, but the interviewer was only interested in the one type I didn’t cover. Perhaps this was just my experience, but it felt strange. Ultimately, I did not make it past this round.
Director Round: This round was mainly for cultural fit and other non-technical aspects. Overall, the experience was positive. The first two rounds were tough but enjoyable due to engaging discussions. However, Round 3 was a departure from the rest of the process. Another thing that bothered me was that the HR suddenly stopped responding. I attempted to get an official update several times over the day after Round 3, but there was no email, and calls were not answered HR immediately ghosted me. So, I had to assume on my own that I was no longer in consideration.
For assignment round practice on Ecommerce apps mainly, I had heard they ask this a lot, and for me also they had asked ecommerce app only. Also, they ask easy to medium level Java DSA questions. I was asked an anagram with different approaches and another was about arrays.
The following metrics were computed from 6 interview experiences for the BrowserStack Software Development Engineer in Test (SDET) role in Mumbai, Maharashtra.
BrowserStack's interview process for their Software Development Engineer in Test (SDET) roles in Mumbai, Maharashtra is very selective, failing most engineers who go through it.
Candidates reported having good feelings for BrowserStack's Software Development Engineer in Test (SDET) interview process in Mumbai, Maharashtra.