← Back to Directory

Lyft

Large Enterprises

Most of these Lyft write-ups come from Software Engineers (13), then Data Scientists (4) and AI Engineers (3). The most reported rounds are the technical phone screen (13), the system design round (4), the onsite coding round (2) and the online assessment (1).

22 interview notes · updated Jun 2026

Lyft·Software Engineer·Online Assessment (OA)

Jun 2026
Did an OA for a software engineer role at Lyft. Just one problem, Rotting Oranges, nothing else to report.
  • Given a grid of oranges where some are rotten and some are fresh, determine how many minutes it takes for all fresh oranges to rot (each minute, rotten oranges spread to adjacent fresh ones). Return -1 if it's impossible.

“Classic BFS multi-source problem.”

View Post

Lyft·Software Engineer·Technical Phone Screen

Jun 2026
Lyft SWE coding round last month. The problem was a classic key-value store thing you've probably seen before, but the twist nobody warns you about is that you also have to write and actually run your own test cases, which ate up way more time than the actual coding.
  • Implement a key-value store that parses command strings line by line, where each line can be a standalone command, a command with a key and value, or a command with a single value. You also need to write and execute your own test cases.

“The parsing part is where I lost it.”

View Post

Lyft·Software Engineer·Take-home Assignment

Jun 2026
Lyft sent over a take-home written exercise instead of a coding screen, which I was not expecting at all. You get a doc full of PM comments and have to respond in-line, basically simulating a real async back-and-forth with a stakeholder. Weird format but kind of refreshing compared to grinding leetcode.
  • Given a document with a Product Manager's comments, questions, and pushback on technical decisions, how do you respond in writing to clarify your reasoning, agree or disagree with feedback, propose alternatives, and ask follow-up questions where needed?

“The format threw me off more than the actual content.”

View Post

Lyft·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Lyft coding round for a software engineer role, 90 minutes, centered entirely on building an in-memory key-value store from scratch. The interviewer pushed pretty hard on design decisions and wanted a second implementation approach, which I wasn't fully expecting.
  • Implement an in-memory key-value store with put, get, and delete operations. Walk through your data structure choice and then sketch out an alternative implementation with trade-off discussion.

“Went with a hashmap first, which felt obvious, and it was.”

View Post

Lyft·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Lyft system design round, one big question that sprawled into about five different topics. The payment reliability stuff was where I spent most of my time and honestly felt like I was just barely keeping up with the follow-ups.
  • Design a charity donation website that uses an external payment SDK as a black-box dependency. How do you handle payment failures, partial failures, and ensure no donations are lost or recorded with wrong amounts?
  • How would you design the system to handle sudden traffic spikes during a high-profile fundraising campaign?
  • Design the APIs for donating, viewing donation history, and generating receipts.
  • What does your data model look like for donations, donors, and campaigns?
  • How would you approach observability for this system, and what fraud signals would you watch for?

“This is where I got turned around.”

View Post

Lyft·Data Scientist·Technical Phone Screen

Jun 2026
Second round coding interview at Lyft for a data scientist role. Just one problem but it was a real one.
  • Implement stratified k-fold cross validation from scratch.

“Not the kind of thing you'd expect to code live.”

View Post

Lyft·AI Engineer·Technical Phone Screen

Jun 2026
Lyft AI Engineer interview that went deep on ML fundamentals, specifically the distinction between generative transformer models and embedding models. One question but it covered a lot of ground and I felt like I was being tested on whether I actually understood the architectural tradeoffs or just knew the buzzwords.
  • Walk me through the differences between a generative transformer model like GPT or T5 and an embedding model like sentence-BERT or OpenAI's text-embedding series. Cover what each is trained to do, the training objectives, what the output actually is, typical use cases, and when you'd pick one over the other in something like a RAG system.

“This felt like five questions stapled together and I kind of answered them in the wrong order.”

View Post

Lyft·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Lyft gave me a 1.5-hour laptop coding round for a software engineer role and it was rougher than I expected. The problem itself wasn't exotic but the edge cases piled up fast and I ran out of time before I had something fully working.
  • Build an in-memory key-value database that supports transactions, including begin, commit, and rollback operations.

“I knew the basic idea going in but underestimated how many edge cases show up once you start implementing.”

View Post

Lyft·Data Scientist·Technical Phone Screen

Jun 2026
Did a Lyft DS interview round focused on ML system design, specifically passenger churn prediction. Pretty standard for this type of role but the data schema angle made it more grounded than the usual open-ended design questions.
  • Given a data schema, how would you build a model to predict whether a passenger will churn in the coming weeks?

“Having the schema handed to you sounds like a gift but it kind of paralyzed me at first because I kept second-guessing which features were actually signal vs noise.”

View Post

Lyft·Software Engineer·Technical Phone Screen

May 2026
Lyft SWE interview with a scheduling/assignment problem that looks straightforward until you actually have to implement it cleanly under pressure. Classic greedy with a heap, but the details trip you up.
  • Given a list of jobs each with a start time and end time, assign jobs to workers so no worker handles two overlapping jobs simultaneously. Use the fewest workers possible and return the worker assignment for each job.

“I knew the general shape of the solution pretty fast, sort by start time, use a min-heap tracking when each worker becomes free, greedily assign to whoever's free earliest.”

View Post

Lyft interview FAQ

What rounds are in the Lyft interview?

Candidates most often report a technical phone screen (13 write-ups), a system design round (4), an onsite coding round (2) and an online assessment (1).

What does the Lyft technical phone screen cover?

Across 13 technical phone screen write-ups, the most tagged question topics are Algorithms & Data Structures (9 questions), Technical Trade-offs (9) and System Design (3).

Lyft interview guides by role

13 notes

Lyft Software Engineer interview questions