
- PM-meets-sales-engineer for legal, not deep coding
- JD strongly preferred; or PM from a legal-AI startup
The Legal Engineer is the conduit between customers, the legal team, and the engineering team: they own the front end and the end result, take onboarding and customization calls, customize the platform for each customer (building custom workflows, often around a client’s commercial contracts, in an hour or less using the existing LLM tooling), and when the lawyers need something, they define it, scope it, and hand tickets to engineering, then own delivery, testing, and output quality. This is post-sales work with existing clients.
The “engineering” here is about speaking the product language and bridging lawyers and engineers, not writing data pipelines or production code. Gabe framed it as a technical-product-manager vision applied to legal. Coding is effectively solved by the tooling and the core engineers; what they need is someone who can understand a legal problem, translate it into workflows and product, and own the result. Evan’s ideal is “a PM meets a sales engineer, focused on the legal aspects of the world.” They want someone AI-fluent (not someone they have to teach AI tooling to), who thinks in systems (“if I’ve done this once, let me build a repeatable mechanism”), asks the right questions to find what a customer really needs, and can listen for signal in the noise from both customers and the internal legal team.
On background, Evan has a strong preference for a JD (he wouldn’t fully rule out a non-JD, but strongly prefers it), with at least some startup legal experience, ideally in-house/transactional, who has moved toward a product motion. They do not need to be a world-class lawyer or engineer. Two archetypes both qualify: a former lawyer (JD, some startup exposure) who moved into product, or a strong product manager from a top legal-AI startup (Harvey, Legora).
Requirements
- JD strongly preferred (ideally with some startup legal experience, in-house/transactional); at minimum real startup legal exposure
- Product-minded: can understand a legal problem, translate it to workflows and product, and own delivery end to end
- AI-fluent (uses AI tooling fluently; no need to be taught)
- Systems thinker who builds repeatable mechanisms
- Asks the right questions; strong at eliciting what customers and lawyers really need
- Some technical background helpful (to speak the product/engineering language); not a deep coding role
Signal (Evan/Gabe’s stated)
- Experience at a legal-tech / legal-AI company (Harvey, Legora, or one of the ~70-80 smaller legal-tech startups, which are easier poaches)
- A former startup in-house lawyer who moved into product
- Worked on something adjacent to what OneGC is building (big win)
- High agency, high slope, ex-founder or very-early-at-a-company background
Who Will Thrive Here
- A lawyer-turned-product person who wants to own a legal product end to end, not practice law
- A PM from a legal-AI company who can speak both the lawyer and engineer languages
- A high-agency builder who figures out their own way without a guidebook
- Someone who wants real room to grow (toward head of legal engineering or a forward-deployed customer-success leader)
No benefits listed yet.