Senior Software Engineer applicants have rated the interview process at BrowserStack with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 31.6% positive. This is according to Glassdoor user ratings.
Candidates applying for Senior Software Engineer roles take an average of 11 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at BrowserStack overall takes an average of 22 days.
Here are the most commonly searched roles for interview reports -
I applied online. The process took 1+ week. I interviewed at BrowserStack (Dublin, Dublin) in Mar 2019
Interview
Phone screen; interview involving discussion about background; remote technical test.
You are given two days ("from now") to complete the technical test, but also told that you can ask questions to people who won't answer, because I got mine at the start of the weekend...
This information needs to be provided in advance so that they can ensure that they have the time to dedicate to it, not sprung on a candidate.
Interview questions [2]
Question 1
Write a basic clone of tail that supports the -f flag.
Write a websockets-enabled 'tail -f' server that will not keep files open, but will repeatedly poll the mtime of the file and not return the whole output each time a user connects.
The requirements were simultaneously vague (in terms of what needed to actually happen) and uncomfortably specific (development, i.e. step-by-step instructions for how to handle the mtime polling).
The use of third-party libs that would significantly increase the productivity were not allowed.
There was no rationale provided in the spec for some of the design and unfortunately, I've dealt with bad specs long enough to know that the company wasn't for me.
I applied online. The process took 1+ week. I interviewed at BrowserStack (Mumbai) in Feb 2017
Interview
Browserstack had reached out to me via Linkedin. After an introductory call with the HR, they took about 5 days to review my profile with the technical panel. It was a little bit weird considering they had gone through my Linkedin profile and hence reached out to me. The first interview was telephonic and this round went pretty well. The interviewer was polite and the questions were related to java and architecture designs. After the interview, the interviewer asked me my willingness to work on other technologies other than Java as Browserstack doesn't have Java at all in its technical stack and me being predominantly a Java professional.
Browserstack's tech stack consists of nodejs, ruby, MySQL, NoSQL etc and some minor modules in golang. After the telephonic interview, I was called for a face to face interview which was for the whole day. It included 2 assignments for 2 hours and normal technical discussions. The assignment questions were related to problems that Browserstack is facing. The interviewer was friendly but there was no hints or help from him. I completed the assignments and then I was told to leave. The HR emailed the next day mentioning that I was rejected. Emailed them back asking for the reasons for rejection but never got to hear back which is expected.
Browserstack has a really good cool office with really good food which I happened to have during my lunch. The Cafe is stocked with munchies and juices. It does get pretty loud as there are no cubicles and the people working there don't care who is sitting next to them. I left pretty late after the interview as my interviewer went into meetings in between and while I was leaving, there were people in the office which give you hints of the work-life balance. All in all, it was an average interview.
Interview questions [1]
Question 1
1. Java, J2EE, Design and Architecture
2. Sort an array in O(N) which is of size N and contains elements from 0 to N - 1 without duplicates.
2. Multi-client web application to simulate "Tail -f <filename>"
3. A standalone application which gets the screenshot and the URL of the last opened web page in the currently running browser instance. The screenshot should the full web page and not just what is shown on the screen i.e. its a web page shot.