I applied through a recruiter. The process took 4 weeks.
A Mercury recruiter reached out to me via email. The first step was the phone screen with the recruiter. The second step was an hour-long video call with the hiring manager. We discussed my background, and they asked some basic React, TypeScript, and Redux quiz questions. At the end of the interview, I had to review a snippet of TypeScript code as if I was doing a code review for a junior developer. They were friendly and pleasant to talk to.
The third step was a technical challenge. It was three hours long:
You are given a "real world" problem you might encounter at Mercury. The interviewer told me they care more about your thoughts than the actual code. You can use ChatGPT or even no code. You are given two JSON files, and you must determine if the objects in one array are a match or a mismatch based on names, emails, etc. The data is formatted slightly differently in each file. Although the interviewer was friendly, they seemed nervous. I did not make it past this stage.
The final round is a virtual onsite. I was told it would involve a TypeScript code review, peer interview, product thinking interview, and a wrap-up with the hiring manager.
Overall, I thought the process went smoothly.
What is a ref?
Why would you not want to use refs too much?
How do you use state management?
Why would you not want to use Redux?
Can you use TypeScript in the browser?
When TypeScript is compiled to JavaScript, can there still be errors?
The following metrics were computed from 3 interview experiences for the Mercury Frontend Engineer role.
Mercury's interview process for their Frontend Engineer roles is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Mercury's Frontend Engineer interview process.