I applied online. The process took 1+ week.
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.
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 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.
The following metrics were computed from 1 interview experience for the BrowserStack Senior Software Engineer role in Dublin, County Dublin.
BrowserStack's interview process for their Senior Software Engineer roles in Dublin, County Dublin is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for BrowserStack's Senior Software Engineer interview process in Dublin, County Dublin.