AI Engineer

View our much better version of this job spec on our careers page:

***

THE KEY BITS

• Location: We can currently only accept applications from candidates that are located and have long-term working rights in the UK.

• Flexibility: We have office hubs in London and Boston, as well as no-office hubs in several European countries. We operate a choice-first work approach that lets you work fully remotely from Day One even if you’re near an office hub.

• Salary: We benchmarked £115,000 + equity at IC4 level in our progression framework 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.

• Interviews: 3 stages totalling around 3 hours over 2-3 weeks.

• Start date: As soon as you can start.

• Reporting to: Pavel Nekrasov, Director of Engineering and lead of the Agentic team at Juro

HELP US HELP THE WORLD AGREE FASTER

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 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, 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 and choice-first work approach are designed with inclusivity in mind. Read more in our diversity, inclusion & belonging hub.

WHO WE LOOK FOR

Research shows that while men apply to jobs if they meet ~60% of criteria, women and those in traditionally under-represented groups tend to apply only if they check all boxes. So if you think you have what it takes but don't meet every single point above, please still get in touch. We'd love to have a chat and see if you could be a great fit.

To succeed here:

Every Juror finds their balance across our four core Principles — we hire, develop and celebrate people who live them every day.

Curious how you’d fit? Try our personality quiz to see how you map against our principles.

On top of that, you have been part of a journey where:

• You’re a programmer first, and you now build with AI and LLMs. You’ve written production TypeScript/Node.js and MongoDB for users. Agents write most of the code today, but you can still tell when an agent’s output shouldn’t go through.

• You’ve built agentic systems yourself, including the tools that let agents act on APIs and integrations. You can explain the parts of an agent (planning, tools, context, the loop around them) because you’ve built them.

• You’ve written and run evals and think about quality in probabilities.

• You’ve shipped something people can use: a product, an open-source project or a tool. (We’ll ask you for a link or description in our application form.)

• Bonus: you’ve used our AI stack before. It changes often, so understanding why things break matters more than knowing the tools already.

Day to day, you’ll work with Node.js, TypeScript, MongoDB, Redis and pgvector on AWS, plus Bedrock, LiteLLM and Mastra for the AI layer.

These requirements can come from a job, a side project or open source. The field is about two years old, so we care about what you've built, not how many years you've been doing it.

This job likely isn’t for you if:

• You need a polished setup before you can ship. We'd rather ship a small, good version this week than a perfect one in two weeks, by which time the stack has moved on.

• You want a stable roadmap. Priorities here can change week to week.

• You want to rebuild things whenever you'd have done them differently. We disagree a lot and openly, but once a call is made, we commit and move.

• You've only ever worked inside one opinionated framework and never looked under the hood.

• You'd rather build product UI. Most of this work is foundations other engineers build on.

OUR MISSION

Juro exists to help the world agree faster by making it incredibly easy for anyone to agree and manage legal contracts.

The load on legal teams is increasing as business teams move faster with the help of AI. The only way out is to deploy AI within the legal team so that (a) routine contract work can be executed autonomously and (b) lawyers’ time is reserved for problem solving.

It’s like having an extra team member that is always on and takes on heavy lifting. Just like an in-house lawyer, Juro:

• is present for, and trusted by, business teams

• owns contracts from first draft to signature and beyond

• builds judgement from every contract it works on

…all within guardrails controlled by the legal team.

GOT MORE QUESTIONS?

Check if they're answered on:

• Our extended job description for this role:

• Our company handbook:

• Our careers page: