Baselayer
Baselayer

Forward Deployed Engineer

$160–230kSan Francisco, CaliforniaHybridSeniorFull-time

Posted Sep 1, 2026

The role in short

Build and ship production integrations, verification APIs, and AI agent surfaces for partners in the agentic economy.

ABOUT BASELAYER


Every business in America needs a bank account to exist. The system that decides whether they're real, who's behind them, and whether they're a risk, runs on infrastructure from the 1980s. We're rebuilding that layer from scratch.

Baselayer is the identity layer for institutions across the United States — the most complete business graph in America and every human tied to it. We fuse public records, IRS data, sanctions lists, web signals, and fraud telemetry from 2,200+ financial institutions into a single graph that resolves any business and the humans behind it in milliseconds. The legacy credit bureaus took 50 years to build something that gets 60% match rates. We've built something that gets 98% in under two years.

Today we're trusted by over 20% of financial institutions in America — including FIS, Rho, Socure and leading loan infrastructure providers. But the graph is becoming infrastructure for anyone who needs to know if a business is real and worth trusting: gig platforms, marketplaces, AI companies, and commerce infrastructure at scale.

Trust is the substrate of every financial transaction. We're rebuilding it.

ABOUT THE TEAM


AI agents are starting to transact: opening accounts, buying services, moving money on behalf of the businesses and people behind them. Every one of those transactions has a counterparty asking the question banks have always asked: who am I dealing with, and can I trust them? Today's identity infrastructure wasn't built to answer it at agent speed.

The Agentic Economy team is extending Baselayer's business graph into the trust layer for agentic commerce: verifiable credentials that bind an agent to the verified business and human behind it, a registry counterparties can query in real time, and verification APIs that plug into the networks, platforms, and protocols where agent transactions happen.

We run like a startup inside a startup: a small senior team led by our GM of Agentic Economy, working directly with payment networks, banks, wallet providers, and agent platforms. The category is being defined right now; the standards, seats, and infrastructure decisions of the next 18 months will be consequential for a decade.

ABOUT THE ROLE


You're the engineering arm of the Agentic Economy team: the person who turns partner conversations into working software. You'll ship the surfaces partners and their agents actually touch: verification APIs, our MCP server, credential flows, demos, and reference implementations. When a payment network wants to see real-time counterparty verification inside an agentic checkout, you build it, often within days.

You'll sit in technical calls with partners, scope integrations on the spot, and work closely with our core platform engineering while owning the last mile yourself. This is a role for an engineer who wants the field, not just the repo.

WHAT YOU'LL DO


  • Ship partner integrations of our agentic economy products from first technical call to production
  • Build prototypes, demos, and reference implementations for partner meetings, communities, and conferences, often on short notice
  • Own the developer- and agent-facing quality of our surfaces: API ergonomics, documentation, sample repos, sandbox environments, integration guides, technical posts
  • Get our MCP server listed, featured, and performing in the connection hubs, directories, and marketplaces where agent builders look
  • Optimize the agent-facing experience itself: tool descriptions, response design, error handling
  • Show up in agent builder communities (Discord servers, hackathons, working groups, open-source repos) as a builder
  • Be the engineering voice in partner calls; translate partner constraints into clear specs for the core platform team
  • Feed field learnings back into the product roadmap alongside our PM and GM

MINIMUM REQUIREMENTS


  • 5+ years shipping production software; strong TypeScript and/or Python
  • Deep API design and integration experience: REST, webhooks, OAuth/JWT auth flows
  • You've worked directly with customers or partners
  • Hands-on with the modern agent stack: MCP, LLM tool-calling, agent frameworks
  • Can take a demo from idea to working in days, and an integration to production in weeks
  • Thrive in ambiguity: startup pace, end-to-end ownership

WHAT SETS YOU APART


  • You've built with MCP, LLM tool-calling, or agent frameworks
  • Familiarity with verifiable credential standards (SD-JWT-VC, DIDs, HTTP message signatures) and/or identity infrastructure
  • Payments or fintech background
  • Prior forward-deployed, solutions engineering, or founding engineer experience
  • An existing footprint in AI and agent-builder communities

WORK LOCATION


  • Based in SF; 4 days per week in office

COMPENSATION


  • Salary Range:$160,000 - $230,000 + Equity

BENEFITS


  • Time off when you need it: Flexible PTO so you can recharge without red tape
  • In-person energy: We're based in SF and meet in the office 4 days a week
  • Competitive compensation: We pay well and back it with equity. We want you to think and act like an owner
  • Career rocket fuel: You'll help build the foundation of a high-growth startup, working side by side with experienced founders and team members who've done it before
  • Benefits on us: We cover 100% of your health, dental, and vision premiums. No surprise deductions from your paycheck
  • 401(k) with company match: We match your contributions so your future self benefits too
  • HSA contributions included: We contribute to your HSA on applicable plans, so your coverage works as hard as you do
  • Stay healthy, stay sharp: A $250 annual gym stipend to help you bring your best self to work, and everywhere else
  • ***Lunch on us:***Lunch stipend so you can stay fueled and focused without thinking about it
  • A seat at the table: We believe in transparency, radical candor, and giving every team member a voice 🔥

Prep for this interview

4 questions likely to come up at Baselayer, each matched to a line in this posting.

  1. 1Integrations and APIs
    They wrote: “Deep API design and integration experience: REST, webhooks, OAuth/JWT auth flows”

    Walk me through connecting our product to a customer's internal system that has no documentation.

    How to answer

    Why they ask: This happens weekly in the job. They want a calm, step-by-step method.

    1. Find who owns the system and get read access to a test environment
    2. Watch real traffic or logs to learn the data shapes
    3. Build a thin adapter with logging around every call
    4. Agree on how failures get reported, and who fixes what

    Tip: Talk about finding the owner of the system first. The code is the easy part.

  2. 2Coding
    They wrote: “5+ years shipping production software; strong TypeScript and/or Python”

    Here's a CSV export from a customer. Write a script that cleans it and loads it into our API.

    How to answer

    Why they ask: Very close to real FDE work. They watch how you handle bad rows and failures.

    1. Read with a proper CSV parser; check the header first
    2. Validate each row and collect errors, not crash on the first one
    3. Send in batches with retries and a clear report at the end
    4. Write one or two quick tests for the parsing

    Tip: Talk through edge cases out loud: encodings, missing fields, duplicates, rate limits.

  3. 3Ownership and working with customers
    They wrote: “Thrive in ambiguity: startup pace, end-to-end ownership”

    Tell me about a project where the requirements kept changing. What did you do?

    How to answer

    Why they ask: Ambiguity is the norm. They want proof you can keep moving without a clear spec.

    1. The project and why requirements kept moving
    2. What you did to pin them down (short demos, written decisions)
    3. The trade-offs you made to keep shipping
    4. The result, with a number if you have one

    Tip: Show how you reduced the change, beyond how you coped with it.

  4. 4LLMs, RAG and agents
    They wrote: “Ship partner integrations of our agentic economy products from first technical call to production”

    When would you use an agent that takes actions, and how do you keep it safe?

    How to answer

    Why they ask: Agent work is growing fast in FDE postings. Senior candidates are expected to know where agents fail.

    1. Use agents for multi-step tasks with clear success checks; avoid them where one wrong action is costly
    2. Give the agent narrow tools and permissions, not broad access
    3. Require human approval for risky actions
    4. Log every step so the customer can audit it

    Tip: Start from the cost of a wrong action. Limit what the agent can do, and log everything.

Not the one? Get the next one by email

New roles land here every day. Pick what you want to hear about.

FDE Info

Want the job, not just the posting? Learn how FDEs work.

FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.

Free. One email a week. Unsubscribe in one click.

Similar roles at other companies

Baselayer

$160–230k · Hybrid

Apply