Senior Software Engineer - Mercury Command

The job

LIVE Employer public job feed (private-sector employer) Source: the employer's public careers feed · Data: listed 2026-02-13

Job description

In 1965, an engineer in Scotland was given a mundane task with a tricky problem to it - banks wanted to close on Saturdays and still serve customers, but they didn’t know how to solve the authentication of the right user. James Goodfellow, working at Smiths Industries, uncovered the insights that you needed something you have (a card) and something you know (a PIN). Because someone told him they could only remember 4 digits instead of his proposed 6, today over 3 million ATMs use a card+4 digit PIN over 60 years later. 

Like the ATM, Mercury is building technology that pushes forward financial interfaces for the long term. Command is Mercury's LLM-powered financial assistant, launched to all customers in June 2026. It lets users understand their finances and take action in plain language, from asking about cash flow to sending payments, issuing cards, and managing invoices. With the product now in customers' hands, the work is to evolve it, extend its capabilities, and find new ways to leverage LLMs to give Mercury customers a more powerful banking* experience.

What you'll do

Ship new capabilities users love:

• Design and ship new Command skills, the domain-specific instruction sets that teach the model how to handle workflows like sending money, managing invoices, and understanding cash flow
• Design and build agentic workflows in Command, defining the architecture for how multi-step agent interactions should work as we extend what the product can do on a customer's behalf
• Work with backend teams to define tool schemas for new capabilities, shaping the data contracts between Mercury's business logic and the model
• Own new capabilities end to end, from the system prompt to the frontend component that renders the response

Own the LLM layer:

• Maintain and evolve Command's prompt architecture: the system prompt, skill loading system, session context, and the policy and compliance layers underneath
• Tune model behavior: reasoning effort, prompt caching strategy, fallback chains, and the streaming patterns that make the product feel fast
• Stay current with how models are evolving and bring that knowledge back to how Command is built

Build quality in:

• Write and expand Command's eval harness, adding cases that cover new capabilities and scoring rubrics that detect regressions before users do
• Partner with product and compliance teams to define what "working correctly" means for each new capability, then build the tests that prove it
• Own the reliability and quality of what you ship, from initial design through post-launch monitoring

This list is illustrative. Command is a product in motion and priorities will shift as we learn. The right person will help choose the next highest-leverage work.

The ideal candidate

• Has 7 or more years of software engineering experience, with deep technical expertise building and scaling LLM-powered applications in production
• Has gone beyond shipping a first version: you have scaled an LLM-powered product, dealt with the reliability and performance problems that come with real usage, and made it better over time
• Has experience designing agentic systems and has opinions about how to architect multi-step workflows that are reliable, explainable, and safe to run on behalf of real users
• Has built eval infrastructure and can write cases that actually measure whether the product works, not just whether the model outputs something plausible
• Understands the real tradeoffs in LLM deployments: latency, cost, compliance, and what breaks in production that doesn't show up in demos
• Has opinions about what makes an AI product trustworthy, not just impressive, and can build toward that bar
• Is comfortable with TypeScript and willing to learn Haskell for backend tool work, or already comfortable with both
• Can work across the full stack of an AI product, from the system prompt to the streaming frontend
• Has a track record of mentoring engineers and raising the technical bar of their team

If this role interests you, we invite you to explore our public demo at demo.mercury.com.

*Mercury is a fintech company, not an FDIC-insured bank. Banking services provided through Choice Financial Group and Column N.A., Members FDIC.

Mercury values diversity & belonging and is proud to be an Equal Employment Opportunity employer. All individuals seeking employment at Mercury are considered without regard to race, color, religion, national origin, age, sex, marital status, ancestry, physical or mental disability, veteran status, gender identity, sexual orientation, or any other legally protected characteristic. We are committed to providing reasonable accommodations throughout the recruitment process for applicants with disabilities or special needs. If you need assistance, or an accommodation, please let your recruiter know once you are contacted about a role.

#LI-RA1

Total Rewards
The total rewards package at Mercury includes base salary, equity (stock options/RSUs), and benefits.

Our salary and equity ranges are highly competitive within the SaaS and fintech industry and are updated regularly using the most reliable compensation survey data for our industry. New hire offers are made based on a candidate’s experience, expertise, geographic location, and internal pay equity relative to peers.

Our target new hire base salary ranges for this role are the following:

Explore around this job

Field: Technology Sub-niche: Software engineering All jobs at Mercury

View this job and apply on the employer's page →

You apply on the employer's page; AtiveSite does not receive or process applications and is not affiliated with the employer. The description above is shown as the source published it.

About the role

This is a — role in the Technology field (Software engineering) at Mercury.

We could not match this job title to one occupation in the official wage statistics, so no pay estimate is shown. Pay is not in the source listing; ask the employer for the range and compare in the 240 job niches.

How to prepare and behave

This is editorial guidance, not information from the employer.

• Read the whole description and match your examples to its requirements; use the same words the posting uses where they are true for you.
• Research the employer before the interview: what it does, who its customers are and recent news; prepare two or three questions about the work.
• Arrive early (or log in early for a video call), dress one step above the daily dress code, and test your camera and audio beforehand.
• Answer with short stories: the situation, what you did and the result. Give numbers when you have them and never invent them.
• Be honest about gaps; say what you did to learn and how fast you can close them.
• Ask about the team, the first 90 days, how success is measured and the schedule; do not open with salary and time off.
• When pay comes up, know the market range for the occupation and your lowest acceptable offer before you answer; ask for the full package in writing.
• Send a short thank-you message within a day, mentioning one thing you discussed.
• The listing mentions a remote or flexible location. Confirm with the employer whether remote work applies to your state: taxes, licensing and benefits can depend on where you live.
• Have code, data work or projects you can show, and be ready to think aloud: many technical interviews test how you reason, not only the answer.

Know your rights as a candidate and an employee:

• U.S. Equal Employment Opportunity Commission: prohibited employment practices
• U.S. Department of Labor: Wage and Hour Division
• CareerOneStop (U.S. Department of Labor): job search help, interview tips and resumes
• USA.gov: avoiding job scams

The city

The listing is remote or has no US state we could identify. Read the country guide for pay, taxes, law and cost of living by state.

Where to live

The job city has no coordinates we can place on the map, so no housing comparison is shown. Use the 250 largest cities table to compare rent and income.

Career paths

We could not match this title to one occupation, so here are the other sub-niches in Technology, where your skills may carry over:

Cybersecurity (713) Data, analytics and AI (3366) Cloud, IT and infrastructure (1040) Product management (836)

Distances

This job has no single city we can place on the map (remote, flexible or unmatched location), so no distance table is shown. Browse all Technology jobs with distances from any of the 20 largest cities.

The employer

Mercury is the employer in this listing. See all its open jobs here →

We do not hold headcount or revenue for this employer. Check its careers site and, if it is listed on a stock exchange, its public filings (SEC EDGAR search).

What it is like to work at a company (culture, schedules, benefits) is not in the source data, so we do not describe it. Read the description and ask the questions under "How to prepare".

Other open jobs at Mercury

Similar jobs

Same sub-niche: Software engineering

All Software engineering jobs → · All Technology sub-niches →

FAQ

What is the Senior Software Engineer - Mercury Command job at Mercury?

A private-sector role in technology (software engineering) listed 269 days ago. The full description is on this page and on the employer's page.

Where is this job?

Remote / flexible (United States). A remote or flexible location is listed; confirm with the employer which states are accepted.

How do I apply?

Use the "View this job and apply on the employer's page" button. AtiveSite does not receive applications.

How much does it pay?

The listing does not publish pay, and we could not match the title to one official occupation.

What is the cost of living there?

See the state or country guide for rent, income and taxes.

How old is this listing?

It was posted on 2026-02-13 (269 days ago). Jobs older than 90 days are not shown.

Are there similar jobs?

Yes: browse software engineering jobs in the United States.

Sources and terms

• Job data: Mercury careers page public feed (listing dated 2026-02-13). The job disappears from this site when it disappears from the source.
• Wages and projections: BLS OEWS (May 2025) and Employment Projections 2025–35.
• City and county figures: Census Bureau ACS 2020–2024, BEA, BLS QCEW and LAUS, NASA POWER climatology; distances from Census Gazetteer coordinates.

AtiveSite is not affiliated with or endorsed by the employer or any government agency, and does not process applications. Verify every detail with the employer before acting.

Sources

• BLS OEWS (wages and employment by occupation, May 2025)
• BLS Employment Projections 2025–35
• BLS Local Area Unemployment Statistics
• BLS JOLTS
• BLS State and Metro Area Employment
• Census Bureau American Community Survey (via Census Reporter)
• BEA GDP by state and Regional Price Parities
• IRS 2026 tax adjustments
• U.S. Department of Labor, minimum wage by state
• Tax Foundation state income tax rates 2026
• USAJOBS
• USCIS
• U.S. Department of State, visas
• NASA POWER climatology
• GeoNames / Census Gazetteer (coordinates)