Legora interview, decoded.

Published accounts describe four to five stages over roughly five weeks. The engineering shape below is from candidate reports; the legal engineer shape is from Glassdoor.

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

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

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.

1. 01Build 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. 02Get streaming in early. The reported failure mode is retrofitting it in the last hour.
3. 03Have 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. 04Decide 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. 05Legal 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.

• 01TechInterview, what Legora tests when it interviews engineersthe four stages (recruiter screen, manager call, six-hour take-home build, build review), the end-to-end chat application on a fixed stack, the streaming advice, the retrieval, citation and hallucination themes, the in-office default, and the recruiter saying the company runs fast
• 02TechInterview, Legora interview guide 2026the five-week timeline, what the loop screens for (retrieval over legal documents, hallucination prevention, evaluation, LLM application architecture, backend and platform work), the Stockholm, London and New York offices, and the pay caveat: base plus equity, no published figures
• 03Glassdoor, Legora legal engineer interview questionsthe four-interview legal engineer loop (HR, lead manager, demo presentation, Head of Legal Engineering) and the report that questions were about day-to-day work, talking to clients about AI and practical scenarios rather than legal knowledge or LLM internals
• 04TechCrunch, Legora reaches a $5.55 billion valuationthe $550M Series D on 10 March 2026 led by Accel, the founding in Stockholm in 2023, the New York headquarters, and the US expansion
• 05Y Combinator, jobs at Legorathe open roles and locations at the time of writing

Interview processes change. This reflects widely-reported and sourced conditions as of 2026 — confirm specifics with your recruiter, and treat it as a map rather than a guarantee.