Time since we first saw it
Day 22
Up longer than most. Similar jobs usually come down between day 1 and day 15.
From 1,368 similar postings that came down. Coming down is not always a hire.
London (UK) · London, England, United Kingdom
Live, first seen by us 22 days agoFlexibility: 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 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.Read the full posting
Location type: HybridFrom the employer’s posting
Employment type: Full-timeFrom the employer’s posting
Department: PDE › EngineeringFrom the employer’s posting
: We can currently only accept applications from candidates that are located and have long-term working rights in the UK
Juro exists to help the world agree faster by making it incredibly easy for anyone to agree and manage legal contracts.
In the employer’s words · Read in context · Company website ↗
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 22
Up longer than most. Similar jobs usually come down between day 1 and day 15.
From 1,368 similar postings that came down. Coming down is not always a hire.
1 open job
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
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 and Node.js for users (MongoDB is a plus, not a must). 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.
- 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. You’ll touch React too, but you don’t need deep expertise. *We’re looking for commercial experience: AI systems you’ve built and run in production at a company. Side projects and open source are a plus, not a substitute. The field is young, so we care more about what you’ve built than how many years you’ve been doing it. If you’re earlier in your career, show us a commercial system you built and how you measured its quality.
Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.
Already applied? Track this application
View our much better version of this job spec on our careers page: https://juro.notion.site/aie
***
THE KEY BITSLocation: 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 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
More info: The FAQ below, juro.com/careers, our handbook or ask talent@juro.com anything.
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 FORResearch 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 and Node.js for users (MongoDB is a plus, not a must). 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 built agent features that run in production* inside a product that customers use, and you’ve owned a meaningful part of them for a while. (We’ll ask you for a link or description in our application form.)
Bonus: you’ve worked on AI over documents (search, retrieval or processing). That’s much closer to our work than, say, AI for audio or video.
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. You’ll touch React too, but you don’t need deep expertise.
*We’re looking for commercial experience: AI systems you’ve built and run in production at a company. Side projects and open source are a plus, not a substitute. The field is young, so we care more about what you’ve built than how many years you’ve been doing it. If you’re earlier in your career, show us a commercial system you built and how you measured its quality.
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 only want to build product UI. Most of this work is foundations other engineers build on.
You’re running your own startup or freelance work alongside your job. This role needs your full focus.
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: https://juro.notion.site/aie
Our company handbook: https://juro.notion.site/handbook
Our careers page: https://juro.notion.site
There, you'll find answers on topics such as career progression, inclusion & belonging, the interview process, benefits and more. Or reach talent@juro.com for anything.
New AI Engineer postings at the employers we follow are up 340% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under AI Engineer, by the work the posting describes.
AI engineers build products on top of AI models that already exist, most often large language models: they connect a model to a company's data and tools and ship the assistants, agents and search features people use.
Postings ask for strong Python or TypeScript, experience with model APIs, retrieval and agent frameworks, and ways to test whether the model's answers are good enough.
An ML engineer trains and serves models; an AI engineer usually starts from a model someone else trained and builds the product around it, though titles often mix the two.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
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 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.
London, England, United Kingdom
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.