Key Takeaways
- Sign up for a free Mercury account and explore the product before applying — firsthand familiarity with the interface, onboarding flow, and feature set will inform your resume language, interview responses, and demonstrate genuine interest that most candidates lack
- Tailor your resume to emphasize fintech, regulated-industry, or B2B SaaS experience prominently, and mirror specific terminology from Mercury's job descriptions to optimize for both Greenhouse's keyword matching and human reviewers
- Prepare a clear, specific answer to 'Why Mercury?' that goes beyond fintech enthusiasm — reference their design philosophy, their position in the startup ecosystem, a specific product feature you admire, or a blog post that resonated with you
- For design and product roles, curate your portfolio to emphasize complex information design, financial interfaces, or B2B products — Mercury's design challenges center on making dense financial data clear and actionable, not consumer-style visual flair
- Invest in your written communication artifacts — a well-crafted cover letter, thoughtful answers to application questions, and clear documentation of your portfolio projects all signal alignment with Mercury's async, writing-heavy culture
- Research Mercury's competitive landscape (Brex, Ramp, traditional business banking) so you can speak intelligently about market positioning and why Mercury's approach is differentiated during interviews
About Mercury
Application Process
-
1
Explore Mercury's Careers Page and Select a Role
Visit mercury.com/jobs to browse open positions, which are typically organized by team (Design, Engineering, Data, Growth, Operations, Compliance). Mercury's job descriptions tend to be unusually detailed and well-written — read them closely, as they often reveal the specific problems the team is solving and the craft expectations for the role. Pay attention to location requirements, as some roles are fully remote while others may require proximity to San Francisco or New York.
-
2
Submit Your Application Through Greenhouse
Mercury uses Greenhouse as its applicant tracking system, so all applications flow through structured forms that parse your resume and collect supplementary information. You'll typically upload your resume, provide links to relevant work (portfolio, GitHub, LinkedIn), and answer role-specific questions. Some roles — particularly in design — may require a portfolio URL, so have this ready before starting your application.
-
3
Recruiter Screen
If your application advances, a Mercury recruiter will reach out to schedule an introductory call, typically 30 minutes. This conversation commonly covers your background, your interest in Mercury specifically, compensation expectations, and logistical fit (timezone, remote work setup). Recruiters at Mercury tend to be well-versed in the product, so demonstrating genuine familiarity with Mercury's banking platform and its role in the startup ecosystem will distinguish you.
-
4
Hiring Manager Conversation
The next round typically involves a deeper conversation with the hiring manager for the team you'd be joining. Expect questions about your relevant experience, how you approach problems, and how you'd handle scenarios specific to Mercury's domain — whether that's designing financial interfaces, building data pipelines for compliance, or scaling growth channels in fintech. This is where Mercury assesses both your technical depth and your product thinking.
-
5
Technical or Domain-Specific Assessment
Depending on the role, you may complete a take-home exercise, case study, or live working session. Design roles commonly involve a design exercise or portfolio deep-dive; engineering roles may include a coding challenge or system design discussion; data roles often feature SQL assessments or analytics case studies. Mercury is known for assessments that mirror actual work you'd do on the job rather than abstract puzzles.
-
6
Cross-Functional Interview Panel
The final round typically includes multiple conversations with team members across functions. For a design role, you might speak with engineers and product managers; for a data role, expect conversations with stakeholders who consume your work. Mercury values collaborative, low-ego teammates, so these conversations often probe how you work with others, handle disagreement, and communicate complex ideas to non-experts.
-
7
Offer and Onboarding
Mercury's offers commonly include base salary, equity, and benefits. As a remote-first company, onboarding typically involves structured virtual sessions, access to internal documentation, and pairing with teammates. Many employees report that Mercury invests meaningfully in onboarding, with clear 30/60/90-day expectations to help new hires build context on the product and codebase quickly.
Resume Tips for Mercury
Lead with Fintech, Banking, or Regulated-Industry Experience
Mercury operates in one of the most heavily regulated industries in tech. If you have experience working in fintech, banking, payments, compliance, or any regulated domain, make this the most prominent part of your resume. Even tangential experience — like building products that handle sensitive financial data, working with KYC/AML processes, or navigating regulatory requirements — signals that you understand the constraints and complexities Mercury faces daily. Position these experiences in your summary and top bullet points.
Demonstrate Craft and Attention to Detail in Your Resume's Design
Mercury is a design-forward company that ships products celebrated for their polish and thoughtfulness. Your resume's visual quality, clarity, and information hierarchy are themselves a signal — especially for design, product, and marketing roles. Use clean formatting, consistent typography, and deliberate whitespace. This doesn't mean flashy graphics; it means every element should feel intentional. A sloppy resume at Mercury sends a stronger negative signal than it might at other companies.
Quantify Impact with Metrics That Matter to a Growth-Stage Fintech
Mercury cares about outcomes — deposits managed, users onboarded, conversion rates improved, processing times reduced, compliance incidents prevented. Frame your accomplishments in terms of business impact: revenue influenced, user growth driven, operational efficiency gained, or risk mitigated. For example, 'Redesigned onboarding flow, increasing activation rate by 23% across 50K monthly signups' is far stronger than 'Improved user onboarding experience.' Use numbers that demonstrate you understand what moves the needle at a company like Mercury.
Mirror Mercury's Job Description Language in Your Bullet Points
Greenhouse parses resumes for keyword alignment with the job description. Study the specific language Mercury uses — terms like 'banking infrastructure,' 'treasury management,' 'startup ecosystem,' 'product-led growth,' 'design systems,' or 'data pipelines' — and naturally incorporate relevant terms into your experience descriptions. Don't keyword-stuff, but do ensure your resume speaks the same vocabulary as the role you're targeting. This improves both ATS scoring and human readability.
Highlight Remote Work and Async Communication Skills
As a remote-first company, Mercury values candidates who thrive in distributed environments. If you've successfully worked remotely, led cross-timezone projects, or built processes for asynchronous collaboration, call this out explicitly. Mention specific tools and practices: 'Led a distributed team of 8 across 4 time zones using async documentation, Loom walkthroughs, and structured Notion RFCs.' This signals you won't need hand-holding in Mercury's remote culture.
Showcase Startup and High-Growth Company Experience
Mercury serves startups and is itself a high-growth company. Experience at startups, YC-backed companies, or fast-scaling organizations demonstrates you're comfortable with the pace, ambiguity, and ownership expectations that define Mercury's culture. If you've worn multiple hats, shipped quickly, or built something from zero to one, make this visible. Even if your most recent role is at a large company, earlier startup experience should be highlighted rather than buried.
Include Relevant Portfolio Links, GitHub, or Writing Samples
Mercury's Greenhouse application often includes fields for portfolio URLs, personal websites, or GitHub profiles. For design roles, a polished portfolio with fintech or B2B SaaS case studies is essentially mandatory. For engineering and data roles, public repos, technical blog posts, or open-source contributions provide strong supplementary evidence. For growth and marketing roles, link to campaigns, case studies, or analytical writing that shows strategic thinking. Don't leave optional link fields blank.
Use a Clean, ATS-Compatible File Format
Submit your resume as a PDF with selectable text — not a scanned image, not a heavily designed Figma export with text-as-vectors. Greenhouse handles PDFs well, but complex layouts with multiple columns, text boxes, or graphics can cause parsing errors that scramble your information. Use standard section headers (Experience, Education, Skills) so Greenhouse can correctly populate your candidate profile. Test by copying text from your PDF — if it pastes cleanly, the ATS will parse it correctly.
ATS System: Greenhouse
Greenhouse is a structured hiring platform used by Mercury to manage its entire recruitment pipeline, from application intake through offer. It parses uploaded resumes to auto-populate candidate profiles, scores applications based on configurable criteria and keyword alignment, and routes candidates through Mercury's customized interview stages. Greenhouse also powers Mercury's internal evaluation process, with structured scorecards that interviewers complete after each conversation.
- Submit your resume as a text-selectable PDF — Greenhouse's parser struggles with image-based files, multi-column layouts, and heavily designed templates that use text boxes or non-standard formatting
- Use standard section headers like 'Experience,' 'Education,' and 'Skills' so Greenhouse correctly categorizes your information into the right profile fields
- Incorporate keywords from Mercury's job descriptions naturally into your resume — Greenhouse allows recruiters to search and filter by keywords, so alignment with terms like 'banking infrastructure,' 'design systems,' or 'data modeling' directly affects your visibility
- Complete all optional fields in the application form, including portfolio URLs, LinkedIn profiles, and role-specific questions — Greenhouse presents these prominently to reviewers, and blank fields can signal low effort
- Avoid using headers, footers, tables, or graphics to convey critical information — Greenhouse's parser often ignores these elements entirely, meaning your contact information or key skills may be lost
- If applying to multiple Mercury roles, submit separate tailored applications rather than one generic submission — Greenhouse tracks applications per role, and recruiters can see your full application history across positions
Interview Culture
Mercury's interview process reflects its core values: craft, intellectual curiosity, and collaborative ownership.
What Mercury Looks For
- Exceptional craft and attention to detail — Mercury ships products known for their polish, and they expect the same standard from every team member's work, whether it's code, designs, analyses, or documentation
- Genuine interest in fintech and banking infrastructure — candidates who are curious about how money moves, how regulatory systems work, and why most banking software is poorly designed tend to thrive here
- Product thinking regardless of role — Mercury values people who think beyond their function to consider how their work impacts the end user, whether you're an engineer, data analyst, or operations specialist
- Comfort with ambiguity and ownership — as a growth-stage company, Mercury needs people who can define problems, not just solve well-scoped ones, and who take initiative without waiting for detailed instructions
- Strong written communication skills — as a remote-first company, Mercury relies heavily on written communication through documentation, RFCs, and async updates, making clarity in writing a core competency
- Collaborative, low-ego working style — Mercury's cross-functional teams require people who give and receive feedback gracefully, defer to expertise, and prioritize the best outcome over being right
- Startup speed with enterprise-grade rigor — banking demands reliability and compliance, so Mercury seeks people who can ship quickly while maintaining the high standards required in financial services