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.
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
