Mercury Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 13 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Mercury.
Mercury
Software Engineer
Entry Easy Positive experience No offer 2 rounds
Interview process
Technical screen Take home
Interview formats
Technical Coding
So far, the interview process included a SQL PR review for the first round. The second round was a 3-hour take-home test. An engineer explained the test parameters for about 15-30 minutes. Then, I had 2 hours to code, followed by a 40-minute session to review my code.
Confirmed questions2 questions
- SQL PR review
- Take home test
Mercury
Senior Software Engineer
Senior Average Neutral experience No offer 6 rounds
Interview process
Technical screen Technical screen Technical screen Technical screen Technical screen Technical screen
Interview formats
Coding Coding Coding Technical Behavioral Behavioral
The interview process included a 1-hour initial TypeScript code review with the FE eng leader, followed by a 3-hour live coding exercise over Zoom. Then there was another 1-hour continuation of the TypeScript code review with the FE eng leader. The process also included a 45-minute product thinking exercise, a 30-minute peer interview, and a 30-minute hiring manager interview. I didn't get past the TypeScript round.
Confirmed questions8 questions
- Given that `isNotNill` incorrectly returns true for empty strings in JS/TS, how would you implement `isNotNullOrUndefined` to return false for empty strings?
- Can you share an instance where you utilized refs in React?
- Could you explain the concept of state management in React?
Mercury
Software Engineer
Mid Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Take home Onsite
Interview formats
Behavioral Technical Coding Presentation
The interview process had 4 rounds. First, a recruiter call where the recruiter asked basic questions about my background and interest in the company. Then, a 1-hour technical interview with a senior engineer, which included questions about my background and some React fundamentals. After that, there was a 2-hour take-home coding interview that was challenging but not as difficult as Leetcode. The final round consisted of three 1-hour interviews with various engineering and product people, covering product and engineering principles, along with more background questions.
Confirmed questions1 question
- Could you explain the function and purpose of the Virtual DOM in React?
Mercury Software Engineer Interview Questions
Quoted word for word from Mercury interview reports.
“Given that `isNotNill` incorrectly returns true for empty strings in JS/TS, how would you implement `isNotNullOrUndefined` to return false for empty strings?”
Read reports →“Is TypeScript code executed directly in the browser?”
Read reports →“What types of errors are detectable by TypeScript?”
Read reports →“Can you identify the error in the provided SQL statement?”
Read reports →“Could you explain the function and purpose of the Virtual DOM in React?”
Read report →“How do Redux and Hooks function, and what distinguishes them?”
Read report →“Can you refactor the database schema for a pull request?”
Read report →“At what point is it advisable to transition from managing state locally to using global state in React?”
Read report →“What drawbacks are associated with employing TypeScript?”
Read report →Formats, difficulty and experience
Across all 13 Mercury interview reports.