About the role
What will you do at Lemma?
Lemma reads all of your agent conversations, finds the failures nobody knew to look for, and opens the PR that fixes them. Why this role exists 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. What you'll do 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 logic and evals that catch a given customer's specific failure modes, then generalize the ones that recur Open PRs against unfamiliar codebases and defend them in review to people who didn't ask for your help Be the only Lemma person in the room for the hard conversations.
Security review, deployment architecture, "why should we trust your patches" Feed everything back into the product so the manual version of this job gets smaller every quarter What we'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 We move fast on hiring. Target is an offer within two weeks of first contact. Onsite in San Francisco, with travel to customers.
We sponsor visas.
Which skills does this role require?
Make your next move
Build a shortlist and prepare
Identify the requirements you can demonstrate, then choose examples from your work to discuss with the hiring team.
- Build a focused shortlist before you applyCompare role requirements with your experience and give each application a clear reason.
- Practice explaining your experience in an interviewRehearse your answers before meeting the hiring team.
Other roles to compare
Review the responsibilities and requirements before adding an opening to your shortlist.
AI Workflow Engineer
Scout Motors Inc. · Charlotte, North Carolina, United States
AI Evaluations Engineer, US Decision Intelligence
Apple · Cupertino, California, United States
Research Engineer, Responsible Frontier AI Research, DeepMind
Google · New York, New York, United States
AI Solutions Engineer
Superior Essex · Sandy Springs, Georgia, United States
Applied AI Design Engineer (100 % remote) (m/f/d)
EWOR · Capon Bridge, West Virginia, United States
AI Outcome Customer Engineer, Forward Deployed Engineering
Google · Atlanta, Georgia, United States
Role information can change. Prepin can help you prepare, but does not submit an application for this role.