Process
I applied online.
Recruiter phone screen, 1 hour practical technical interview, 2 hour live coding assessment (display a list of items and a detail view, with relevant details and a debugging component), and a virtual on-site (30 min with engineering exec, 45 with PM+designer, 30 with hiring manager).
The recruiter was very responsive and helpful, and the process was respectful and realistic to the role.
Questions
How would you debug glitching on a list?
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Mercury iOS Engineer role.
Success Rate
Mercury's interview process for their iOS Engineer roles is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for Mercury's iOS Engineer interview process.
Mercury Work Experiences
- 5.0Nice place to workSenior Engineer • Current EmployeeAugust 5, 2026Pros: WLB is pretty balanced, and there is always a good sense of people who want everyone to succeed as much as possible (whether it comes to learning and writing Haskell, new AI tooling, specing out new greenfield projects, etc.).Cons: Proper prioritization of impactful projects.
- 5.0Best job I’ve ever hadSenior Software Engineer • Current EmployeeNew York, NYSeptember 21, 2026Pros: Friendly people, great benefits, competitive salary, and many learning opportunities.Cons: No cons that I can think of.
- 4.0Flexible work environment hindered by micromanagementSenior Software Engineer • Current EmployeeJuly 30, 2026Pros: Very, very, very, very flexible.Cons: Managers are micromanaging us.
