Skills this job asks for
LLMsComplianceTypeScript
Add your CV (free) to see which of these your CV is missing.
Where you can work from
Several countries
Based on the listing's location: San Francisco, CA, New York, NY, Portland, OR, or Remote within Canada or United States.
The company's headquarters is not the same as where you may work from. Visa sponsorship only matters if you would relocate; see below.
Visa sponsorship, if you would relocate
Sponsorship verdict
Sponsorship possible
One solid signal, not two. Worth applying, and worth asking about sponsorship early.
-
✓
Employer is on a government sponsor recordThe US Department of Labor certified 6 H-1B/E-3 labor condition applications for this employer between Oct 2025 and Jun 2026 (latest Jun 2026) — the step every H-1B hire needs first.
-
?
The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
-
?
No salary bar for this routeH-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area.
-
✓
What Mercury Financial LLC paid sponsored hires in similar roles2 certified filings for “DevOps Engineer” (Software Developers) in TX: $158k–$165k, median $161k.
-
✓
Confirmed live todayWhen a source last listed this job as open.
Details and sources
- Employer is on a government sponsor record
- The US Department of Labor certified 6 H-1B/E-3 labor condition applications for this employer between Oct 2025 and Jun 2026 (latest Jun 2026) — the step every H-1B hire needs first. Source: LCA disclosure data (US Department of Labor (OFLC)).
- No salary bar for this route
- H-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area. Cap-subject employers enter a lottery weighted by wage level. Source: https://www.federalregister.gov/documents/2025/12/29/2025-23853/weighted-selection-process-for-registrants-and-petitioners-seeking-to-file-cap-subject-h-1b, rules effective 2026-02-27.
- What Mercury Financial LLC paid sponsored hires in similar roles
- 2 certified filings for “DevOps Engineer” (Software Developers) in TX: $158k–$165k, median $161k. Most were filed at wage level III (50%) — 3 lottery entries, ≈46% projected selection odds for cap-subject employers. Source: US Department of Labor LCA disclosure data (Oct 2025 – Jun 2026).
US H-1B: cap-subject employers enter a lottery weighted by wage level — Level I gets 1 entry, Level IV gets 4 (DHS projected selection odds ≈15% at Level I to ≈61% at Level IV). Universities and non-profit research employers are cap-exempt. The $100,000 fee for new petitions from abroad is currently blocked by a court order (appeal pending).
A verdict summarises public evidence. It is not legal advice and never a guarantee: the employer and the immigration authority decide. Sign in to factor in where you can already work.
About the role
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 al
Apply on employer site ↗