Juro has big ambitions: to make it incredibly easy for anyone to agree and manage legal contracts. And we'll need help doing it.
Legal tech is on the rise, with Goldman Sachs estimating that 44% of legal tasks can be automated https://www.law.com/legaltechnews/2023/03/30/legal-industry-reacts-to-goldman-sachs-generative-ai-report-keep-calm-and-panic/?slreturn=20231019075707 with generative AI. With the brand we have built and the agility of early stage we are well placed to capture this opportunity.
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.
As the Agentic team, we build the AI foundations the rest of engineering ships on — starting with Operator https://juro.com/operator, the agent that works across contracts inside Juro.
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.
What you're here to do
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:
- You've shipped new tools that connect Operator to the Juro app, from first idea to production.
- 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.
- You own parts of the agent harness (planning, tool use, context) without the team becoming a. bottleneck.
- You review a lot of agent-written code and decide quickly what's safe to merge and what will break three cycles later.
We care about building a diverse team where everyone feels they belong. That’s why our perks & benefits https://juro.notion.site/benefits and choice-first work https://juro.notion.site/choice-first-work approach are designed with inclusivity in mind. Read more in our diversity, inclusion & belonging hub https://juro.notion.site/dei.