Legora interview, decoded.

Updated · Sources at the end

Legora's engineering loop turns on one artefact: a take-home build of an end-to-end chat application, on a stack the team names so they can read your code the way they read their own, finished inside six hours, then walked through with the manager and the team. Around it sit a recruiter screen that says the quiet part out loud (fast pace, in the office every day) and a manager call about what you have shipped. Legora was founded in Stockholm in 2023, where its engineering still sits, and now describes its headquarters as New York; it raised $550M in March 2026 at a $5.55B valuation, and Bloomberg reported on 22 September 2026 that it was in talks to raise at least $300M at about $8.5B before the new money.

Free · 2 minutes · no account

The questions for your exact Legora role and level.

See the questions Legora asks ↓Run a free mock interview →

Interviewing at Legora? Below are the questions candidates report. For the ones your exact role and level will get, paste the posting. Your first mock is free.

01

Who Legora hires

Legora hires software engineers for its Stockholm engineering team, with offices in London and New York, and a second, distinct track of legal engineers: lawyers who configure and demonstrate the product to law firms. Both tracks are in-office by default. Engineering candidates report a loop built around a take-home; legal engineers report a demo presentation to the Head of Legal Engineering.

Two tracks, two loops. The engineering loop tests whether you can build a working LLM application under a clock; the legal engineer loop tests whether a lawyer can run the product in front of a sceptical partner.

  • Track · Eng

    Software engineering

    Recruiter screen, manager call, the six-hour build, the build review. Reported themes are retrieval over legal documents, citation accuracy and keeping a model from inventing a case that does not exist.

  • Track · Legal

    Legal engineering

    An HR interview, an interview with the lead manager, a demo presentation, and a final with the Head of Legal Engineering. Reported questions are about day-to-day work, talking to clients about AI and practical scenarios, much more than legal doctrine or how LLMs work.

02

What is the Legora interview process?

Legora publishes five stages for every role: an application, a People Team interview, a hiring manager interview, a case and presentation, and a final interview with its CEO or the head of the department. It says most candidates finish in two to four weeks and hear back within three to five business days after each interview, though some candidates for sales and operations roles report six rounds. The engineering shape below is from candidate reports; the legal engineer shape is from Glassdoor.

01
Recruiter screen
A short call

Motivation, tolerance for pace, and the office question: candidates report the recruiter saying plainly that the company runs fast and expects people at a desk every day. Relocation to Stockholm comes up here.

02
Manager call
A conversation with the hiring manager

What you have shipped, how you reason about trade-offs, and how much you can run on your own.

03
Take-home build
Six hours, fixed stack

An end-to-end chat application: a message from a text box to a model and back to the screen, then made good. Streaming responses are reported to matter; retrofitting streaming in the last hour is how people run out of clock.

Engineering track
04
Build review
A walkthrough with the manager and the team

Your code, read the way they read their own: why this structure, what you would do with another day, where it breaks.

Engineering track
05
Demo presentation
A presentation, then a final with the Head of Legal Engineering

Running the product for a legal audience and handling the practical questions a firm asks about AI.

Legal engineer track
06
Final interview
With the CEO or the head of the department

Legora calls it a final conversation to make sure of mutual fit and alignment. Bring your questions about the team, the office and the first months.

03

Legora case and presentation interview: how to prepare

What Legora says, and what candidates report

Every Legora process includes a case. Legora's own description is short: you receive a case or challenge relevant to the role, then give a 60-minute presentation and discussion with the team. It doesn't say how long you get to prepare, so ask the recruiter. For engineers the case is the six-hour build; for legal engineers and customer roles, candidates describe a demo to a law firm and hard questions about how a firm adopts the product.

  • Build a demo for a law firm and sell them the platform: Reported by a customer engagement candidate in 2025, who was given a generic use case with no specific requirements beyond repetitive work and a need to be more efficient. Supply the requirements yourself: pick a practice area and one repetitive task, say what it costs the firm in hours today, demo that one workflow in Legora, and close on the time saved and the next step.
  • Answer hard questions about firm adoption: Reported for legal engineer candidates. Legora's ads describe the job as running pilots, onboarding new users and guiding full-firm adoption, so prepare that path: which practice group pilots first, what counts as success, how you win over a sceptical partner, and how billable hours and client expectations shape the case for the product.
  • Present to the team, then take questions: Plan for the discussion as much as the slides: the presentation and the questions share the 60 minutes. Keep the demo short, leave room for pushback, and answer questions about AI in plain language, the way you would to a partner who has never used it.
  • Prepare the way Legora suggests: Legora's advice is to review the job description, explore the platform, reflect on past achievements and come with questions. Use the product before the case, and know which of your past results you will use as evidence.

Legora says it is an in-office company and that it runs fast. Candidates for customer-facing roles report up to six rounds, so ask the recruiter for the full plan on the first call.

The rest of the loop depends on your role. Pick it, or paste the posting, and Calibrd predicts the rounds and questions you are likely to get at Legora.

Predict my Legora questions →
04

What Legora screens for

Speed and ownership dominate the reports, and the office requirement is stated up front rather than discovered late.

  • Speed: the company runs fast and says so in the first call
  • Ownership of a build from empty repo to working product
  • Accuracy where errors carry real cost: a fabricated case or clause is unacceptable
  • In-person by default, in Stockholm, London or New York
  • For legal engineers, credibility in front of lawyers who are sceptical of AI
05

Legora interview questions

Candidate-reported themes

The reported questions cluster around the product's hard problem: retrieval over legal documents where a wrong citation is worse than no answer.

Behavioural & motivation

  • Why Legora, and why legal AI in particular?Listening for: Specificity · Connection · Research
  • Walk me through something you shipped end to end, and the trade-offs you made on the way.Listening for: End to end · Trade-offs named · What shipped
  • How do you work when nobody hands you a spec?Listening for: A real case · How you defined it · Shipped and checked
  • Legal engineer track: a partner is sceptical about AI accuracy on document review. How do you handle the conversation?Listening for: Takes the concern seriously · Concrete safeguards · A practical next step

Technical

  • You have six hours to build a chat app: text box to model and back. What do you build in the first hour, and when do you add streaming?The six-hour chat app: Text box to model to screen first, then streaming, then make it not embarrassing; on the stack they nameListening for: Right order · Sensible scope · Made presentable
  • A law firm uploads 10,000 contracts. Design retrieval that answers a question and cites the exact clause.Retrieval over legal documents: Chunking, indexing, ranking and source citation over a firm's documentsListening for: Chunking · Retrieval and ranking · Exact citation
  • How do you stop a model from citing a case that doesn't exist?Hallucination and accuracy: How you would keep a model from inventing a case or clause that does not existListening for: Grounding · Verification · Measured
  • A legal research answer takes 40 seconds and costs too much. Where do you look first?LLM application architecture: Prompts, tool calls, context, latency, cost, failure handlingListening for: Measure first · Real levers · Keeps quality
  • Design data isolation so one law firm's documents can never appear in another firm's results.Backend and platform: APIs, data models, queues, multi-tenant data isolationListening for: Tenant model · Enforced everywhere · Proof it holds

These are the reported themes, and your loop is role-specific. Paste the actual posting and Calibrd predicts the questions for that exact role and level. How the questions are predicted →

Predict my Legora questions →
06

Pay

Legora publishes no pay bands and Levels.fyi had no usable Stockholm sample when this was written (13 September 2026). Reports describe base plus equity, with US offices higher in cash and Europe trading cash for a stronger overall package. Ask for the range on the recruiter call, and cross-check against Spotify, Klarna and Truecaller on Levels.fyi for the Stockholm level. Calibrd benchmarks the pay on any posting you scan against its level and location.

Software engineer salary in Stockholm, by level and by employer →

07

How to prepare for a Legora interview

  1. Build a chat app before they ask you to. Text box, model call, response on screen, then streaming. Do it once on a fixed stack you are told to use, under a clock, so the real one is a repeat.
  2. Get streaming in early. The reported failure mode is retrofitting it in the last hour.
  3. Have a retrieval design ready to draw: chunking, indexing, ranking, and how every answer cites its source, for documents where a fabricated citation is unacceptable.
  4. Decide about the office before the loop. In-person in Stockholm is the default, the recruiter says so on the first call, and relocation is part of the conversation.
  5. Legal engineers: rehearse a demo for a sceptical partner, out loud, with the accuracy question answered before it is asked.

This guide covers Legora's software engineering loop and the legal engineer track, which is a role for lawyers rather than developers. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

Also interviewing at Tandem Health, King or Klarna? Their guides follow the same format, from the first screen to the offer.

Knowing the questions isn’t the same as answering them out loud. Run a Legora mock: spoken answers, coached on the spot. Your first mock is free.

Run a Legora mock →
08

FAQ & sources

What is Legora's interview process?

Legora publishes five stages for every role: an application, a People Team interview, a hiring manager interview, a case and presentation, and a final interview with its CEO or the head of the department. The stages, in order: Recruiter screen; Manager call; Take-home build; Build review; Demo presentation; Final interview.

What does Legora look for in candidates?

Speed and ownership dominate the reports, and the office requirement is stated up front rather than discovered late. Speed; Ownership of a build from empty repo to working product; Accuracy where errors carry real cost; In-person by default, in Stockholm, London or New York.

What questions does Legora ask in interviews?

The reported questions cluster around the product's hard problem: retrieval over legal documents where a wrong citation is worse than no answer. Technical themes: The six-hour chat app; Retrieval over legal documents; Hallucination and accuracy; LLM application architecture; Backend and platform.

What is the Legora case study interview?

Every Legora process includes a case. Legora's own description is short: you receive a case or challenge relevant to the role, then give a 60-minute presentation and discussion with the team. Covered on this page: Build a demo for a law firm and sell them the platform; Answer hard questions about firm adoption; Present to the team, then take questions; Prepare the way Legora suggests.

How do I prepare for a Legora interview?

Build a chat app before they ask you to. Text box, model call, response on screen, then streaming. Do it once on a fixed stack you are told to use, under a clock, so the real one is a repeat. Get streaming in early. The reported failure mode is retrofitting it in the last hour.

Prep for a real Legora role

Practise your Legora interview, out loud.

Paste a real Legora posting and Calibrd predicts the questions for that role and level, benchmarks the pay, and flags the gaps an interviewer will probe in your CV — then listens to your spoken answers and coaches them. Your first mock is free. Calibrd is built in Stockholm, by a hiring manager who has run engineering hiring here, so this is a loop we know from the other side of the table.

Free to start · No card · Encrypted at rest, never used to train AI, remove anytime

Two weeks out?

Email me the Legora prep checklist

The round that decides it, the questions they ask, and what to do before, in one email. Nothing else unless you sign up.

Legora Interview: The Six-Hour Build, Pay — Calibrd