Mercury - Banking for Startups

VISION: We’re shaking up one of the least innovative, most powerful industries around, eliminating pain points faced by every startup, and filling a crucial missing piece in the tech ecosystem. Building a bank from the ground up is a big project; the product is complex and cannot break, there are stringent regulations, and we’ll have to outcompete some of the largest, most entrenched corporations in the world. But overcoming these challenges means we’ll have built something that lasts.

IMPACT: Working on a lean, self-motivated team means autonomy, broad experience across projects, and seeing your contributions directly shape the product and impact users. Working on a greenfield project means you’ll have to make foundational decisions; starting from scratch requires more thought than adding to existing infrastructure, and your architectural choices will serve as the bedrock of future development.

QUALITY: Building things correctly is fundamental to being a bank. There’s no room for sloppy code or technical debt, which means doing things like using static typing and immutability, designing database schemas with checks and foreign key constraints, and carefully reviewing teammates’ code. One of the core complaints about banking is usability, so we try to think hard about how to build features that users love; see our blog post on our date picker (https://medium.com/mercury-bank/a-magic-date-input-using-parser-combinators-in-typescript-3c779741bf4c) for an example. Our goal is to be proud of what we’ve crafted.