Startups · AI

Forward Deployed Engineer

Lemma · San Francisco, CA, US · On-site

← All jobs
About Lemma

Production Monitoring for AI agents. Backed by Y Combinator.

About the role

Lemma reads all of your agent conversations, finds the failures nobody knew to look for, and opens the PR that fixes them. This role is that motion, productized. You go into a new customer, get them to the moment where Lemma surfaces something that makes them sit up, and then take everything you learned doing it by hand and turn it into product so the next customer doesn't need you in the room.

What they're looking for

  • 3+ years shipping production software, plus something in your history that shows you're good in front of customers. Forward deployed, solutions engineering, consulting, founding, running your own thing
  • Strong TypeScript. You'll be reading unfamiliar agent codebases constantly and writing patches for them
  • You've built with agents and have real opinions about why they fail
  • Genuinely fast. Our whole pitch is compressing the time between "something is broken" and "it's fixed." You should embody that
  • Comfortable with the ambiguity of walking into a company you don't know and figuring out what matters in a week
  • Bonus: you were the customer once. You ran agents in production and got burned
More about this role

Lemma reads all of your agent conversations, finds the failures nobody knew to look for, and opens the PR that fixes them.

For our first design partners we didn't sell software. We embedded. We sat in their Slack, read their traces at odd hours, learned their agent's failure modes better than they had, and opened PRs against their repo. Wordware shipped 8 PRs in one morning off issues we surfaced. Issues they didn't know they had.

It worked, and it doesn't scale as a founder activity.

This role is that motion, productized. You go into a new customer, get them to the moment where Lemma surfaces something that makes them sit up, and then take everything you learned doing it by hand and turn it into product so the next customer doesn't need you in the room.

If you want a clean separation between customer work and engineering work, this isn't it. The whole job is the seam between them, and roughly half of it is committing to our codebase rather than theirs.

  • Own new customers end to end: integration, first traces, first surfaced failure, first merged PR
  • Live in customer Slack channels. You'll know their agent architecture better than most of their engineers do
  • Write the detection...

Read the full posting on Lemma's site ↗

Engineering

Build your edge while you search

Free tools for founders and investors, plus VC Unfiltered, our take on startups, venture and the people who build them.