Are these based on real engineering roles?
Yes. The catalog is built around real engineering role patterns so the practice round feels closer to a live interview.
Company practice
Mercury mock interviews
Pick a role, answer follow-up questions out loud, and get a scored verdict after the interview.
4 rolesHaskellTypeScriptCI/CDLLMs
Create custom interviewRoles to practice
Mercury
Backend
Senior Backend Engineer - Product
Build and own backend services in Mercury's roughly two-million-line Haskell codebase that powers banking, payments, and treasury products for over 300,000 startups, designing type-safe APIs and data models on PostgreSQL while collaborating closely with product and frontend teams. You'd ship features end-to-end against high-availability, money-movement systems where correctness is non-negotiable. A technical interview would probe your ability to model a domain with strong static types, reason about purity and effects in Haskell, and design schemas and transactions that keep financial state consistent under concurrency.
HaskellYesodPostgreSQLMercury
DevOps / SRE
Senior Engineering Manager - Release Engineering
Lead the team that owns Mercury's build, test, and deployment pipeline, keeping CI fast and reliable across a massive Haskell monorepo where compile times and developer feedback loops are a first-order concern (Mercury maintains open-source tooling like ghciwatch and static-ls for exactly this). You'd manage engineers improving release safety, rollout tooling, and developer productivity. An interview would explore how you scale CI/CD for a large compiled codebase, design safe deployment and rollback strategies for financial services, and lead a team balancing velocity against reliability.
CI/CDHaskellNixMercury
Fullstack
Senior Full-Stack Engineer
Work across Mercury's stack, writing Haskell on the server and React with TypeScript on the client to deliver complete product experiences in the banking dashboard, from account flows to dashboards startups use daily. You'd own features from API design through polished UI, balancing performance and product craft. An interview would likely cover building a small full-stack feature, designing a clean component and state model in React/TypeScript, and wiring it to a well-typed backend endpoint while reasoning about edge cases and error states.
HaskellReactTypeScriptMercury
ML / AI
Senior Software Engineer - AI Engineering
Build AI-powered features into Mercury's product, integrating large language models into workflows like transaction categorization, support automation, and financial insights while keeping outputs safe and reliable in a regulated banking context. You'd design prompts, evaluation pipelines, and the surrounding application plumbing in Haskell and TypeScript. A technical interview would probe how you structure LLM workflows, guard against hallucination and prompt injection in a fintech setting, and build evaluations to measure whether an AI feature is actually correct and trustworthy.
LLMsHaskellTypeScript
ExoForm is not affiliated with Mercury. This is an independent practice page.
FAQ
Is the interview voice-based?
Yes. ExoForm runs a live voice interview, asks follow-ups, and produces structured feedback after the session.
Can I try it for free?
Yes. You can start with the free interview allowance before upgrading for more practice.