Company
Legora interview questions
7 practice questions in the style of Legora's interviews, covering Behavioral & Leadership, System Design, Software Engineering Fundamentals.
0 easy6 medium1 hard
Legora interview questions by the numbers
Last updated
Katkat has 7 Legora interview questions. The largest topics are Behavioral & Leadership (43%), Software Engineering Fundamentals (29%) and System Design (29%). By difficulty: 86% medium and 14% hard. The most common round is Onsite (86%). Frequent concepts include System Design, api-design, Behavioral and cloud-storage.
Topics
- Behavioral & Leadership43% · 3
- System Design29% · 2
Difficulty
- Medium86% · 6
- Hard14% · 1
Interview rounds
- Onsite86% · 6
- Technical Screen14% · 1
Roles
- Software Engineer71% · 5
- Backend Engineer14% · 1
- Site Reliability Engineer14% · 1
Frequent concepts
- System Design43% · 3
- api-design29% · 2
- Behavioral29% · 2
- cloud-storage29% · 2
- Distributed Systems29% · 2
- object-oriented-design29% · 2
Most mentioned in interview experiences
- 1.Senior engineer project deep dive: trade-offs, scale, challenges, hardest part2 reports
- 2.Deep-Dive into a Technical Project1 report
- 3.Design a Cloud-Provider Upload Adapter1 report
- 4.Design Direct File Uploads for a Chat Application1 report
Counted from 2 candidate interview experiences on Katkat. How we collect and count
Showing 1–7 of 7 results
Tests an engineer's ability to articulate, defend, and reflect on a complex technical project, demonstrating clear ownership, architectural decision-making, and self-awareness about trade-offs and failures.
LegoraSoftware EngineerBehavioral & LeadershipOnsiteDesign a scalable direct-to-object-store file upload pipeline for a chat platform, focusing on presigned authorization, durable lifecycle tracking, asynchronous validation, and orphan reconciliation.
LegoraSoftware EngineerSystem DesignOnsiteDesign a provider-neutral object storage upload client that unifies cloud SDK behaviors while supporting streaming, multipart uploads, error normalization, and provider-specific escape hatches.
LegoraBackend EngineerSoftware Engineering FundamentalsOnsiteDesign a modular, provider-agnostic upload adapter interface that enables clients to perform direct uploads to cloud storage (e.g., S3, GCS, Azure Blob). The problem evaluates object-oriented API design, error normalization, capability negotiation, and idempotent verification workflows.
LegoraSoftware EngineerSoftware Engineering FundamentalsOnsiteDesign an immutable, multi-tenant compliance audit logging platform that supports canonical ingestion, cryptographic tamper evidence, gap detection, and efficient legal investigation queries at scale.
LegoraSite Reliability EngineerSystem DesignOnsiteTests a candidate's ability to communicate complex technical work, defend architectural decisions under scrutiny, and demonstrate end-to-end ownership from problem formulation to production operations.
LegoraSoftware EngineerBehavioral & LeadershipOnsiteBehavioral question for senior software engineers: lead a 20-minute deep dive into a past project and answer probing questions about trade-offs, operating scale, challenges and the hardest part. It assesses ownership, engineering judgment, use of concrete numbers, and clear technical communication under time pressure.
LegoraSoftware EngineerBehavioral & LeadershipTechnical Screen
Legora interview experiences
All 2 →- Fumbled the Live Coding, Rejected the Next DayLegora · Software Engineer · Senior+ · Technical Screen · Oct 2026Rejected
Sharing my interview experience at Legora for Senior Software Engineer in Stockholm, Sweden. First was a recruiter call to chat about my past experience, background and interest in the company. Second was a technical screen (45 mins) with one of the engineers on the team. Out of the 45 mins, 20 mins were for a project deep dive. They asked questions about tradeoffs, scale, challenges faced and wh…
- A System Design Round with Almost No CodingLegora · Software Engineer · Onsite · Aug 2026
This one was basically the same as another writeup I'd already seen about this company's process. Round 1 was a project deep dive. Round 2 was system design + coding, though the coding part was so small it felt kind of pointless. I originally thought the coding portion would take 45 minutes, but this second round actually leaned much more toward system design. They gave me a chat app setup, asked…
More companies
- Meta666
- Amazon653
- Google486
- OpenAI342
- Capital One268
- Microsoft252
- DoorDash241
- Anthropic225
- Uber217
- Apple177
- TikTok176
- Pinterest161
- ByteDance160
- LinkedIn154
- Stripe139
- Snowflake130
- Databricks122
- Airbnb112
- Rippling106
- Oracle104
- Coinbase99
- Netflix97
- NVIDIA95
- Snapchat94
- Citadel90
- Waymo90
- Instacart87
- Roblox84
- Salesforce77
- Optiver76
- Shopify63
- Robinhood60
- Atlassian55
- Hudson River Trading55
- Two Sigma55
- J.P. Morgan53
- PayPal53
- xAI53
- Lyft52
- Tesla52