← Back to results

Applied AI Engineer

Take ownership of AI platforms and tools at Legora, building internal agents and systems to enhance legal workflows.

Location
Stockholm HQ
Compensation
Not disclosed
Level
mid
Type
full time · On-site

Posted by employer 1 month ago

First seen on Joblaze 1 month ago

Last verified on the company career page 16 hours ago

Apply at Legora → Save job Scanned from legora.com

Skills & Technologies

What you'll build

  • Build internal agents, tools and platforms
  • Own what you build end to end
  • Shape what we should build and in what order
  • Design the foundations: knowledge architecture, access and permissions
  • Work directly with users across the company

Must have

  • Strong engineering fundamentals
  • Real depth with LLM-based systems
  • Ownership by instinct
  • Three kinds of understanding: technical, domain, and business
  • Openness to feedback
  • Comfort with ambiguity

Nice to have

  • Experience with cloud providers

AI in the day-to-day

We work with internal AI tools and platforms to enhance legal workflows and build internal agents.

Not disclosed in this posting: compensation, years of experience, visa sponsorship.

Joblaze summary

In this role, the AI Engineer at Legora is responsible for developing and managing internal AI tools and platforms, ensuring they meet the needs of the business and are utilized effectively. The position requires strong engineering skills, particularly with LLM-based systems, as well as proficiency in TypeScript and infrastructure management. Ideal candidates will have a blend of technical, domain, and business understanding, along with a proactive approach to ownership and problem-solving. The team operates in a fast-paced environment, emphasizing high standards and collaboration.

Joblaze insights

  • Listed about a month ago — first seen on Joblaze September 27, 2026. Last confirmed on Legora's careers page November 14, 2026.

Quick facts

Is the Applied AI Engineer role remote?
No — this is an on-site role in Stockholm HQ.
Where is the role based?
Legora is hiring for this position in Stockholm HQ.
What's the tech stack?
Joblaze extracted these technologies from the posting: LLM-based systems, Terraform, TypeScript.
What seniority level is this role?
Legora targets mid-level candidates for this position.
Is this full-time or contract?
Full-time for this Applied AI Engineer role at Legora.

From the original posting

Joining Legora means three things.

  • We lean in: ownership over titles, outcomes over intentions.

 

Stockholm | Full-time | Onsite, five days a week

The team

AI Enablement makes Legora AI-native by default. We work across three streams in parallel: building internal agents and tools, equipping teams to build their own, and owning the standards, access and guardrails that let everyone move fast safely.

We own the AI platforms and the internal products built on them. So far that includes Leya, an internal knowledge agent live in Slack that answers questions about Legora with cited sources and automates parts of our RFP and security questionnaire work. A structured, agent-readable knowledge base assembled from knowledge each domain continues to own, where agents propose changes and humans approve them. Leyf, a platform for internally built apps that lands anyone's app on shared infrastructure with guardrails scaled to how much damage it could do. And a Skills Hub, so that something one person works out becomes something the whole company can use rather than staying on their laptop.

The team is small and the mandate is large. That is the job.

What makes this hard

Legora is an AI company of around a thousand people, most already fluent and on current tools. Internal AI here is not an adoption problem. Nobody needs convincing, which means there is nowhere to hide behind change management or training. If something we build is not used, it is because it was not good enough.

Our colleagues know what good looks like and will not use something worse than what they think they could build themselves in an afternoon. So we ship things people genuinely want, and the foundations arrive with them. That constraint does not go away.

The mandate is also larger than the team. The part no individual can do for themselves is the infrastructure, the access model and the architecture underneath, and getting that right across a company this size is the actual work. It does not come with a specification.

What you will do

You will take broad ownership of how AI works inside Legora and of the platforms we build to make it work.

  • Build internal agents, tools and platforms, and treat them as products rather than projects. Quality, reliability and whether they actually serve the business are yours, not someone else's

  • Take a broad goal, work out what is actually required, and break it into the work yourself

  • Own what you build end to end, from the architecture through to whether people use it and it holds up in production

  • Shape what we should build and in what order, and argue for it

  • Design the foundations: knowledge architecture, access and permissions, evaluation and monitoring, the guardrails that scale with risk

  • Work directly with the people who will use what you build, across the whole company, including the parts furthest from engineering

Who we are looking for

  • Strong engineering fundamentals. You build production systems, not prototypes that need someone else to finish them

  • Real depth with LLM-based systems. Agents, retrieval, evaluation, tool use. You know where these systems break and you design for it

  • Ownership by instinct. You do not wait for a specification. When the requirement is unclear or wrong, you say so and propose something better

  • Three kinds of understanding at once. Technical, domain and business. You can hold a conversation about architecture and a conversation about what the business actually needs, and connect them

  • Openness. You take feedback, build on other people's ideas, change your mind when the evidence moves, and push for the strongest outcome rather than the one you proposed first

  • Comfort with ambiguity. New team, fast growth, decisions that get revisited as we learn. That should sound appealing rather than annoying

  • TypeScript. It's what we work in, and where our shared patterns live

  • No aversion to infrastructure. We own ours, so Terraform and cloud providers are part of the work rather than someone else's problem

  • You work with code agents daily. Not as an experiment, as how you build

 

Standard company text repeated across Legora's postings is omitted here.

Similar positions

Legora
AI Software Engineer
Legora · Stockholm HQ
Legora
AI Enablement Lead
Legora · New York City
Legora
AI Enablement Lead
Legora · London
Legora
Legal Engineer Associate
Legora · San Francisco