Lyft interview guide¶
Rideshare, bikes and scooters in North America plus FREENOW in Europe; interviews mix LeetCode screens with 90-minute laptop rounds, Byteboard assessments and product system design. Updated October 2026.
| Lyft at a glance | |
|---|---|
| Category | High-growth tech |
| Intern level | Software Engineer Intern (Summer 2027 tracks: Backend, Frontend, Fullstack, Machine Learning, Test Automation; SF, Toronto, Montreal, Mexico City). |
| New grad level | T3 (Software Engineer). |
| 0 to 3 years | T3 for 0 to about 2 yrs; T4 (Software Engineer II) for roughly 2 to 5 yrs; T5 is Senior. |
| Online assessment | Varies: CoderPad (non-proctored multi-file assessment), Byteboard (doc review + implementation), or a timed OA (90 min or 2 hours) on an unnamed platform. : Examples: 90-min OA with two problems (array transformation, graph traversal) for an SDE (Jul 2025 review, location not stated); 2-hour OA for a SWE intern (Nov 2025 review, location not stated); Byteboard with a design doc to annotate then a related implementation (Mexico City intern Jan 2025; Toronto and Mexico City SWE 2025). |
| Coding rounds | Interns: 1 technical (60 min) plus 1 to 2 laptop rounds (90 min) after an OA/Byteboard. T3/T4: 1 phone screen plus laptop round plus sometimes a coding/CS fundamentals round onsite. |
| Behavioral | Lyft does not publish a values list on its careers pages as of Oct 2026; pages describe the purpose 'to serve and connect' and say culture 'revolves around our core values'. Third-party guides cite older values such as 'Disagree and Commit', 'Dive Deep' and 'All-in ownership' (unverified). Use STAR with metrics. |
| Timeline | Summer internship postings open in September (Summer 2027 postings dated Sep 2026). Reported: 2 to 3 weeks for Toronto SWE loops (2025); about 4 weeks for an intern loop (Nov 2024); 2 months for a Toronto iOS loop (Nov 2024); 7 weeks of repeated postponements for a Sr SWE (2025); staff onsites can be split over days; team matching can stretch for weeks and some candidates who clear the loop get no team match (Jul and Dec 2025 reviews). CHANGE: Lyft acquired FREENOW in July 2025 for EUR 175M (Wikipedia), and the careers site now links to European roles on free-now.com; Lyft also partnered with Waymo (Nashville, Sep 2025). |
| New grad pay | Levels.fyi (US, read 2026-10-04): T3 average total comp $188,100/yr (base $129,400, stock $57,700/yr, bonus $1,000; 10 data points, 5 in last 12 months); 2026 SF T3 offers $177k to $194k. T4 average $238,219. Intern pay (official SF Backend Intern posting, Summer 2027): $52 to $58/hour base. |
| Official links | Careers, Students, Values |
Interview process¶
New grad¶
- Application. Lyft's early talent page covers interns, new graduates and apprentices, but no US new grad SWE posting was open on Lyft's Greenhouse board on 2026-10-04 (only Summer 2027 internships and experienced roles). Most early-career SWE openings in 2025 to 2026 reports are in Toronto, Montreal and Mexico City. Two generic 'Software Engineer' postings went up in Sep 2026 (San Francisco, base $136,000 to $162,000; Seattle, requiring an MS plus 2 years of experience); neither is labeled new grad.
- Recruiter screen (about 30 min). Resume walkthrough, interests, past experience and why Lyft; the recruiter also explains the interview process (Aced). Toronto 2025 reports put it at about 30 min.
- Technical screen (about 60 min) or Byteboard. Live LeetCode-style problem on CoderPad, usually medium (sometimes hard: sliding window median, minimum window substring), with follow-ups. Toronto and Mexico City candidates in 2025 report a Byteboard take-home or proctored session first (read a design doc, comment on it, then implement related features).
- Onsite (virtual). Reported rounds for T3/T4: laptop round (about 90 min on your own setup; reports range from an OOD-style practical problem with your own tests to a plain DSA problem, e.g. a Toronto candidate who expected OOP got a meeting-rooms style problem and ran out of time writing a heap in Go), coding / CS fundamentals (60 min), system design (60 min, product flavored), behavioral (30 to 45 min, often with an engineering manager; includes inclusion questions). Toronto SWE example (Oct 2025): recruiter 30 min, coding screen 60 min, onsite system design 60 min, coding 60 min, behavioral 30 min.
- Team matching. Matching with teams happens after the onsite; candidates report long waits and no offer when no team picks them (Dec 2025).
Intern¶
- Application. Summer 2027 postings went live in Sep 2026. Requirement example (Backend, SF): pursuing a BS or MS in CS graduating Dec 2027 to Summer 2028; master's students with prior work need under 2 years full-time experience. SF interns work hybrid, in office Mon, Wed and Thu.
- Online assessment or Byteboard. Reports vary by track: a 2-hour OA (SWE intern, Nov 2025 review, location not stated); a non-proctored multi-file CoderPad assessment with written and coding questions (intern, interviewed Nov 2024, location not stated); a Byteboard interview (read a document and comment, then implement) for interns in Mexico City (Jan 2025) and another Oct 2025 intern (location not stated); ML intern OA built around a provided class (Toronto, Dec 2025).
- Technical interview (about 60 min). LeetCode-style on CoderPad, medium (e.g. rotting oranges; binary search through a provided class for ML interns).
- Laptop interview(s) (about 90 min). One SWE intern (Nov 2025 review, location not stated) had two 90-min laptop rounds after the technical. Mobile interns build on starter code (Android 2026: finish an icon-matching app; passing needs at least 3 of the steps).
- Behavioral (some tracks). Short behavioral or recruiter conversation in some loops; the Toronto ML intern loop (Dec 2025) ended with an ML interview instead.
With 1 to 3 years of experience¶
T4 and above: recruiter call, technical phone screen (often a well-known LeetCode medium or hard; staff candidates report a Blind-list hard), then a virtual onsite of about 4 rounds that can be split over days: laptop round (Senior SF 2026: 'basically OOD'; Staff 2026: algorithm plus your own test cases), system design (pagination API, real-time chat with delivery guarantees, 1:1 chat, product voting, donations site, social feed), behavioral/experience (bar-raiser style for staff), sometimes a domain round (cloud security for staff security roles; data engineers report 7 interviews incl. Lyft driver-rider data models and a real-time driver-request API, Toronto Feb 2026). A Senior AI Engineer report (Jun 2026) describes 1 coding round followed by 4 loop interviews. Candidates who pass the DSA round but lose the role may be allowed to skip to the final stage within six months (Toronto, 2025).
Online assessment¶
- Platform: Varies: CoderPad (non-proctored multi-file assessment), Byteboard (doc review + implementation), or a timed OA (90 min or 2 hours) on an unnamed platform.
- Format: Examples: 90-min OA with two problems (array transformation, graph traversal) for an SDE (Jul 2025 review, location not stated); 2-hour OA for a SWE intern (Nov 2025 review, location not stated); Byteboard with a design doc to annotate then a related implementation (Mexico City intern Jan 2025; Toronto and Mexico City SWE 2025).
- Notes: Byteboard reports mention it is closer to real work than LeetCode; one Toronto mobile candidate said they used ChatGPT during a Byteboard take-home and passed (allowed use is not confirmed). Follow the rules stated in your invite.
Prepare with How to pass an OA and compare formats in OA formats by company.
Coding rounds¶
- Rounds: Interns: 1 technical (60 min) plus 1 to 2 laptop rounds (90 min) after an OA/Byteboard. T3/T4: 1 phone screen plus laptop round plus sometimes a coding/CS fundamentals round onsite.
- Style: LeetCode medium with Lyft framing; frequent patterns are sliding window (minimum window substring, sliding window median), intervals (meeting rooms II, car pooling, merge intervals), BFS/DFS on grids (rotting oranges) and hash maps with state. Laptop round is practical: design classes for a real problem, make it work, add tests, then extend for new requirements.
- Environment: CoderPad for screens (Lyft-provided docs and a mock-interview video for mobile tech screens per a 2025 iOS review). Laptop round on your own machine; a third-party guide says internet use is allowed. Frontend screens may use CodePen (build a 7-segment clock in HTML/CSS, 30 min). Mobile rounds use Xcode or Android Studio starter projects.
- Graded on: Correctness and tests, clean structure, performance, communication. Aced (formerly Exponent) reports the laptop round weighting as correctness 45%, clean code 35%, performance 20% (not confirmed by Lyft).
- Reported focus topics: Sliding window (minimum window substring, sliding window median), Intervals and sweep line (meeting rooms, car pooling, merge intervals), BFS/DFS on grids and graphs, Hash maps with state management, Practical OOP with tests (laptop round), Reading and extending code from a spec (Byteboard), Product system design: chat, voting, feeds, crawlers, pagination APIs, Behavioral: ownership, failure, inclusion, Design data structures with timestamps and binary search (time-based key-value store)
Run every practice problem through the 45-minute framework and the code quality rubric.
What they ask (data)¶
Based on 5 distinct problems tagged to Lyft in the last 6 months (2 in the last 30 days, 3 in the last 3 months, 25 all-time) across two open datasets of LeetCode company tags. Tags are user-reported, so treat frequency as a signal, not a promise.
Difficulty mix (last 6 months): Medium 60%, Hard 40%
Most tagged topics (share of problems): Array 40%, Hash Table 40%, String 40%, Design 40%, Simulation 20%, Interactive 20%, Binary Search 20%, Sliding Window 20%, Breadth-First Search 20%, Matrix 20%
Watch out: Lyft has thin LeetCode data. Weight the reported questions and the format notes above more than this list.
Most frequent problems¶
Ranked by frequency, weighted toward the last 30 days. Classics like Two Sum sit near the top of almost every company's list because users tag them everywhere. Solve those fast. The signature list below is more specific to this company.
| # | Problem | Difficulty | Last seen | Topics |
|---|---|---|---|---|
| 1 | Read N Characters Given read4 II - Call Multiple Times | Hard | 30 days | Array, Simulation, Interactive |
| 2 | Time Based Key-Value Store | Medium | 30 days | Hash Table, String, Binary Search, Design |
| 3 | Minimum Window Substring | Hard | 3 months | Hash Table, String, Sliding Window |
| 4 | Rotting Oranges | Medium | 6 months | Array, Breadth-First Search, Matrix |
| 5 | Min Stack | Medium | 6 months | Stack, Design |
Signature problems¶
Problems where Lyft accounts for a large share of all recent tags across companies. These are the most Lyft-specific questions in the data.
| # | Problem | Difficulty | Last seen | Topics |
|---|---|---|---|---|
| 1 | Read N Characters Given read4 II - Call Multiple Times | Hard | 30 days | Array, Simulation, Interactive |
Reported in 2025 to 2026 interviews¶
Questions candidates said they got, each linked to the post where it was reported.
| Question | Role | When | Source |
|---|---|---|---|
| Two 90-min laptop rounds after a 60-min CoderPad technical (LeetCode-style) | SWE Intern (location not stated) | 2025-11 | post |
| Byteboard: read a design document and comment, then implement a related program | Software Engineer Intern (location not stated) | 2025-10 | post |
| Byteboard: add features to an internship-management system | Software Engineer, Mexico City | 2025-09 | post |
| Rotting oranges in a matrix | SWE Intern (interviewed 2024-11, reported 2025-10; location not stated) | 2024-11 | post |
| Android starter app: finish an icon-matching game (complete at least 3 steps to pass) | Android Software Engineer Intern, Toronto | 2026-09 | post |
| Binary search implemented through a provided class (OA and two technicals) | ML Intern, Toronto | 2025-12 | post |
| LeetCode medium in the technical round | Full Stack Developer Intern, Toronto | 2026-01 | post |
| Sliding window median (asked as 'find median in a sliding window' in the coding screen) | Software Engineer, Toronto | 2025-10 | post |
| Laptop round problem similar to Meeting Rooms II / Car Pooling | Software Engineer, Toronto (final round) | 2025-09 | post |
| Smallest window in a string containing all target characters | Mid-level to senior (Hello Interview; 8 Lyft reports, last Jul 2026; also in a Jul 2026 Glassdoor review) | 2026-07 | post |
| Design a scalable real-time chat system with delivery guarantees (system design) | Mid-level to senior (Hello Interview; 8 Lyft reports, last Aug 2026; also in a Jul 2026 Glassdoor review) | 2026-08 | post |
| Design 1:1 chat (system design) plus a HashMap and state-management coding question | Software Engineer (location not stated) | 2026-07 | post |
| Merge overlapping time intervals (calendar bookings, unsorted input); then basic cache and rate-limiter design | SDE (location not stated) | 2025-07 | post |
| Build a real-time HH:MM:SS clock from 7-segment digits with HTML and CSS (CodePen, 30 min) | Front End Developer, San Francisco | 2025-11 | post |
| Create a minesweeper game in Kotlin (mobile technical) | Android Engineer, New York | 2025-12 | post |
| Design a pagination API (system design) | Staff Software Engineer, Cloud Security, US | 2026-05 | post |
| First missing positive | Mid-level (Hello Interview reports) | 2026-05 | post |
| Design a product voting system (system design) | Mid-level and manager (Hello Interview reports) | 2026-07 | post |
| Design a Wikipedia crawler (system design) | Mid-level (Hello Interview; Lyft report Apr 2026; also asked at Meta, Glean, Google) | 2026-04 | post |
| Maximum candies from locked boxes with keys | L5 phone screen (2024, older data) | 2024-12 | post |
| Design a donations website for a charity event (system design) | Mid-level (Hello Interview; Lyft report Aug 2026, also DoorDash and Whatnot) | 2026-08 | post |
| Time based key-value store | Mid-level to senior (Hello Interview; 3 Lyft reports, last Jul 2026) | 2026-07 | post |
Beyond LeetCode¶
Laptop round (90 min, practical OOP with your own tests, extend for new requirements). Byteboard (annotate a technical design doc, then implement part of it). Mobile build-on-starter-code rounds (Android icon matching, Kotlin minesweeper, iOS Xcode starter project). Frontend CodePen UI tasks (7-segment real-time clock). Domain rounds for security and data engineering (data modeling).
System design¶
Expected from T4; Toronto T3/T4-level SWE loops in 2025 to 2026 also included a 60-min system design, so new grads should prepare basics. Flavor is product design with APIs and data models: real-time 1:1 chat, product voting, donations website (Lyft mid-level, Aug 2026; shared with DoorDash), social feed generation, Wikipedia crawler (Lyft mid-level, Apr 2026; the intern-level report on that page is Meta), pagination API, ride-sharing data models. Laptop rounds double as LLD/OOD.
Start with who needs system design, then the framework.
Behavioral¶
Framework: Lyft does not publish a values list on its careers pages as of Oct 2026; pages describe the purpose 'to serve and connect' and say culture 'revolves around our core values'. Third-party guides cite older values such as 'Disagree and Commit', 'Dive Deep' and 'All-in ownership' (unverified). Use STAR with metrics. (official page)
What they look for:
- Ownership of a project you are proud of: your role, impact, and how you measured it
- Handling failure and production bugs you caused
- Persuading colleagues and disagreeing with cross-functional partners constructively
- Inclusion and belonging: repeated questions on what inclusion means to you and how you promote it
- Collaboration in a low-ego, cross-functional team (stated in job postings)
- Structured answers; one 2025 report calls the behavioral round 'very strict and structured'
Questions to prepare:
- What's inclusion for you? (SWE, Jul 2026)
- Tell me about a recent project you're proud of. What was your role, impact, and how did you measure it? (SWE, Jul 2026)
- Tell me about a failure. (SWE, Jul 2026)
- Did you convince a colleague about your solution, and how? (SWE, Jul 2026)
- What does diversity and inclusion mean to you? (Hello Interview, mid-level, 2025-07)
- Tell me about a time you promoted inclusion in the workplace. (Hello Interview, 2026-05)
- Tell me about something you are most proud of and why. (Hello Interview; Lyft listed among askers)
- Tell me about a time you disagreed with a cross-functional partner. (Hello Interview, mid-level, 2026-04)
- Tell me about how you handled a production bug you caused. (Sr SWE, 2025)
- Tell me about the project that was most challenging. (SWE, Toronto, Oct 2025)
- What was a situation where you didn't agree with your manager or superior's decision? (Hello Interview, mid-level, May 2026)
Build your answers with the story bank. Company detail: behavioral guide.
Tips¶
- Rehearse a 90-minute laptop round: build a small class-based solution in your own environment, write tests, then extend it for a new requirement without rewriting.
- If you get a Byteboard invite, practice reading a short design doc, leaving specific review comments, and then implementing a feature from it.
- Prepare an inclusion story; Lyft behavioral rounds repeatedly ask what inclusion means to you and how you promoted it.
- Drill sliding-window and interval problems until you can code them in under 25 minutes; screens have included hard variants (sliding window median, minimum window substring).
- Interns: Summer 2027 postings opened in Sep 2026; apply in the first week and expect hybrid office days (Mon, Wed, Thu in SF).
- US new grad SWE postings were not open in Oct 2026; watch Toronto, Montreal and Mexico City postings and the early talent page.
- Keep other processes alive after a good onsite: team matching decides the offer and can take weeks.
- If you clear the coding round but lose the role, ask the recruiter about skipping to the final round on a new role within six months.
- Ask the recruiter whether your laptop round is OOD-style or algorithmic, and pick a language with a built-in heap or priority queue; a Toronto candidate lost time writing a heap from scratch in Go.
4-week plan for Lyft¶
Do this after you finish a core list like Grind 75 or NeetCode 150.
- Week 1: Solve problems 1 to 20 from the most frequent list. Time-box each at 30 minutes.
- Week 2: Solve problems 21 to 40. Re-solve any you failed in week 1 without looking.
- Week 3: Solve the signature problems and every reported question above. Do 2 timed mock interviews.
- Week 4: Write 8 stories for the Lyft does not publish a values list on its careers pages as of Oct 2026; pages describe the purpose 'to serve and connect' and say culture 'revolves around our core values'. Third-party guides cite older values such as 'Disagree and Commit', 'Dive Deep' and 'All-in ownership' (unverified). Use STAR with metrics. round. Do 2 full mock loops. Review the online assessment and system design notes above.
Sources¶
- Question data: liquidslr/leetcode-company-wise-problems and snehasishroy/leetcode-companywise-interview-questions, merged and ranked by scripts/build_question_data.py.
Watch out: Data for Lyft is thinner than for the other three companies: few 2025 to 2026 LeetCode posts, no public official interview guide, and no published values list. Process details come mostly from Glassdoor reviews (permalinks confirmed in a browser session) and third-party guides (Aced 2026, Prepfully 2023). Formats vary by office: Toronto, Montreal and Mexico City loops use Byteboard more often; US loops lean on CoderPad screens plus the laptop round. Laptop-round grading weights are third-party claims. Several reported questions are from Canada/Mexico roles and some from senior levels (labeled). No US new grad SWE posting was open on 2026-10-04, so the new grad loop is inferred from early-career SWE reports. Older 2024 items are labeled. Reddit and Blind were not covered because the web search budget ran out. FACT-CHECK (2026-10-04, second agent): all URLs re-fetched (lyft.com, Greenhouse API, Levels.fyi, Wikipedia via curl; LeetCode via GraphQL; Glassdoor and Hello Interview in a browser). Fixed: many Glassdoor reviews do not state a location, so 'Canada' and 'US' labels were removed; the Wikipedia-crawler 'intern' report belongs to Meta; product voting and diversity question dates corrected; the laptop round is not always OOP. Wikipedia confirms FREENOW acquisition (Jul 2025, EUR 175M) and the Waymo Nashville partnership (Sep 2025). One Glassdoor review used for two questions (min window substring, real-time chat) reads like a question-bank promotion; treat as low confidence. Removed two unsourced claims: recruiter multiple-choice technical questions (Android, 2026) and a separate stats/product loop for data science interns (not found in Glassdoor pages 1 to 18 or other sources). The min-window-substring and real-time chat questions now cite Hello Interview (8 Lyft reports each) instead of the promotional Glassdoor review. Timeline rewritten: 'onsite invites within hours' and 'auto-rejections 2 days after onsite' were not found in Glassdoor pages 1 to 12; the 'Freenow by Lyft' Glassdoor listing claim was dropped.
Next: All companies