About the Role
<p style="min-height:1.5em"><em>View our much better version of this job spec on our careers page: </em><a target="_blank" rel="noopener noreferrer nofollow" href="https://juro.notion.site/aie"><em>https://juro.notion.site/aie</em></a></p><p style="min-height:1.5em"></p><p style="min-height:1.5em">***</p><p style="min-height:1.5em"></p><h1>THE KEY BITS</h1><p style="min-height:1.5em"></p><ul style="min-height:1.5em"><li><p style="min-height:1.5em"><strong>Location</strong>: We can currently only accept applications from candidates that are located and have long-term working rights in the UK.</p></li><li><p style="min-height:1.5em"><strong>Flexibility</strong>: We have office hubs in London and Boston, as well as no-office hubs in several European countries. We operate a <a target="_blank" rel="noopener noreferrer" class="postings-link" href="https://juro.notion.site/choice-first-work">choice-first work approach</a> that lets you work fully remotely from Day One even if you’re near an office hub.</p></li><li><p style="min-height:1.5em"><strong>Salary</strong>: We benchmarked £115,000 + equity at IC4 level in our <a target="_blank" rel="noopener noreferrer nofollow" class="notion-page-mention-token notion-text-mention-token notion-focusable-token notion-enable-hover" href="https://juro.notion.site/progression">progression framework</a> for someone based in the UK. What you’ve done in the last ~2 years is far more important to us than how long you’ve been an engineer — so if you think you meet the requirements but are worried you’re not “senior” enough, we strongly encourage you to still apply. If you like the look of the role but the salary doesn’t match what you’re looking for, let us know in your application.</p></li><li><p style="min-height:1.5em"><strong>Interviews</strong>: 3 stages totalling around 3 hours over 2-3 weeks.</p></li><li><p style="min-height:1.5em"><strong>Start date</strong>: As soon as you can start.</p></li><li><p style="min-height:1.5em"><strong>Reporting to</strong>: <a target="_blank" rel="noopener noreferrer" class="notion-link-token notion-focusable-token notion-enable-hover" href="https://www.linkedin.com/in/pavel-e-nekrasov/"><u>Pavel Nekrasov</u></a>, Director of Engineering and lead of the Agentic team at Juro</p></li><li><p style="min-height:1.5em"><strong>More info</strong>: The FAQ below, <a target="_blank" rel="noopener noreferrer" class="postings-link" href="http://juro.com/careers">juro.com/careers</a>, our <a target="_blank" rel="noopener noreferrer" class="postings-link" href="https://juro.notion.site/handbook">handbook</a> or ask ----- anything.</p></li></ul><p style="min-height:1.5em"></p><p style="min-height:1.5em"></p><h1>HELP US HELP THE WORLD AGREE FASTER</h1><h1></h1><p style="min-height:1.5em">Juro has big ambitions: to make it incredibly easy for anyone to agree and manage legal contracts. And we'll need help doing it<strong>.</strong></p><p style="min-height:1.5em">Legal tech is on the rise, with Goldman Sachs estimating that <a target="_blank" rel="noopener noreferrer" class="postings-link" href="https://www.law.com/legaltechnews/2023/03/30/legal-industry-reacts-to-goldman-sachs-generative-ai-report-keep-calm-and-panic/?slreturn=20231019075707">44% of legal tasks can be automated</a> with generative AI. With the brand we have built and the agility of early stage we are well placed to capture this opportunity.</p><p style="min-height:1.5em"></p><p style="min-height:1.5em">Our Agentic team was the first team at Juro to go fully AI-native, and it's been the role model for our other product teams as Juro evolved into an AI company.</p><p style="min-height:1.5em">As the Agentic team, we build the AI foundations the rest of engineering ships on — starting with <a target="_blank" rel="noopener noreferrer nofollow" href="https://juro.com/operator">Operator</a>, the agent that works across contracts inside Juro.</p><p style="min-height:1.5em">We want Operator to do a lot more. That takes more and better tools, solid evals, and a harness that keeps up with a stack that’s still rapidly evolving. And more great people to do it.</p><p style="min-height:1.5em"></p><p style="min-height:1.5em"><code>What you're here to do</code></p><p style="min-height:1.5em">Give Operator the tools it needs to act across Juro and make sure what it does is measurably good. In your first months, success looks like this:</p><ul style="min-height:1.5em"><li><p style="min-height:1.5em">You've shipped new tools that connect Operator to the Juro app, from first idea to production.</p></li><li><p style="min-height:1.5em">What you ship has evals around it, supported by the Quality Assurance team, so we can tell whether a new model, prompt or library version makes things better or worse.</p></li><li><p style="min-height:1.5em">You own parts of the agent harness (planning, tool use, context) without the team becoming a. bottleneck.</p></li><li><p style="min-height:1.5em">You review a lot of agent-writt