Candidates describe Lyft's Software Engineer loop as a recruiter screen, a coding screen, then a virtual onsite with coding, system design and behavioral rounds. Several report hard-leaning algorithm problems and slow recruiter communication.
$165K
Avg. Base Comp
$260K
Avg. Total Comp
5-7 rounds
Typical Rounds
Not reported
Process Length
Candidates who describe Lyft's Software Engineer interview most often report a recruiter conversation, a technical screen, and then a virtual onsite that combines a laptop coding round, a system design discussion and behavioral questions. The coding bar is the most debated part. Some candidates describe medium LeetCode-style problems, while others report harder ones such as Minimum Window Substring, a median in a sliding window, or an interval-scheduling problem similar to Meeting Rooms II. One candidate who chose Go ran short on time writing a heap from scratch, so language choice and built-in data structures are worth deciding before the interview.
System design questions that candidates mention are practical: a driver-rider matching service with live location indexing and heavy writes, a real-time one-to-one chat system with delivery guarantees, and caching and rate limiting. A few candidates also describe object-oriented design exercises, and one reports writing their own test cases in the laptop round. Behavioral rounds range from standard STAR-style project questions to a strict, structured format. One candidate was also asked about measuring project impact.
Outcomes in these reports are mostly rejections. Several candidates mention slow scheduling, little feedback, or roles closing or lacking a team match even after interviews went well. One candidate who passed the hiring bar was put into team matching when the original opening closed. It makes sense to ask your recruiter early about team matching and timelines.
Synthesized from 22 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Lyft process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Lyft
What is the probability that it's actually raining in Seattle?
| Question | |
|---|---|
| P-value to a Layman | |
| Three Zebras | |
| Success Measurement | |
| Rider Discount | |
| Ride-Sharing App Schema | |
| CTR by Age | |
| Converted Sessions | |
| Uber Eats Customer Experience | |
| Two Cars | |
| Sports App Cheater | |
| Justify a Neural Network | |
| Accessible Data | |
| Statistically Significant Test | |
| Stratified Split | |
| Parking Application System Design | |
| Meta in an Emerging Market | |
| Employee Salaries | |
| 2nd Highest Salary | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Weighted Keys | |
| Retailer Data Warehouse | |
| Top 3 Users | |
| Bagging vs Boosting | |
| Daily Retention Summary | |
| Sum to N |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a short recruiter call of roughly 15 to 30 minutes covering background, work experience and why Lyft. One candidate says the recruiter also asked for examples of distributed-systems projects. Expect to summarize your experience clearly, since this step typically sets up the technical screen.
Candidates describe a timed or live coding screen, with problems ranging from medium to hard LeetCode-style questions. One reports a proctored sliding-window problem, another a timed assessment they did not finish, and another a Blind 57-style hard question. One candidate was sent starter code to open in Xcode. Practice under time pressure and ask what format to expect.
Onsite reports include one or two coding rounds, sometimes on a laptop. Problems candidates mention include interval scheduling, binary search and object-oriented design. One candidate had to write their own test cases. Interviewers may care about code quality and clear explanation as well as a correct answer, so narrate your approach and validate it.
Candidates report system design prompts such as driver-rider matching, a real-time chat system, caching and rate limiting. Expect to discuss tradeoffs, scalability and reliability. Interviewer engagement reportedly varies, with one candidate describing a mostly silent interviewer, so be ready to drive the conversation yourself.
Candidates describe behavioral questions about a project they are proud of, its measured impact, failures, disagreements and inclusion. Formats are reported as both strict and structured and as conversational. Prepare several specific STAR stories. Some candidates mention a hiring manager or bar raiser here, though one reports never meeting the team.
