Lyft Software Engineer Interview Questions
& Process

I had an interview experience with Lyft in August 2025. I passed the initial DSA round, but unfortunately, another candidate was selected for the offer. I was informed that I could reapply for other positions and would be able to skip to the final stage for a period of six months. In September, I applied for a different role and successfully advanced to the final round. This round involved a laptop interview, a system design component, and an experience-based interview. Based on their description, I anticipated the laptop round to be a task related to day-to-day operations or object-oriented programming. I opted to use Go to demonstrate my abilities. However, it turned out to be another DSA interview, and I didn't finish implementing a heap data structure from scratch within the given time. Even the interviewer seemed unaware of this limitation in Go. The system design and experience interviews went well. I didn't get to meet any members of the actual team I would be working with, including the person listed as the 'hiring manager,' who was actually from a different department. It felt like the recruitment wasn't genuinely for the specific role advertised.

So, the whole thing kicked off with a 90-minute online assessment, basically two coding problems. One was about transforming arrays, and the other involved graph traversal. They were pretty standard difficulty, but it felt a lot like those timed Hack2Hire tests. After that, I had two technical interviews. The first one was a deep dive into merging intervals, focusing on all the edge cases. The second was a basic system design question, covering cache and rate-limiting. In one interview, the engineer was super late, showed up 10 mins after it started, and then just stayed quiet the whole time. The other interview was more open, talking about how the team is being reshuffled. Even though I passed everything, I was told there wasn't a team match, which is what I'd heard on Blind and 1point3acres. Seems like a lot of people are clearing the interviews but then just stuck in limbo. It's a good practice run if you need to get better at live coding interviews, but honestly, don't get your hopes up for a definite outcome.

So the interview for Lyft was pretty structured and they really wanted to see if I was a good fit technically and culturally. It started with a call from a recruiter where we talked about my background and why I was interested in the job. They also laid out what the interview process would be like and what they look for. Then, I had a technical phone screen with one of their engineers. It was a one-hour coding session where I had to solve algorithmic and data structure problems, and I had to explain how I was thinking. The engineer was pretty cool and it felt more like a conversation. The toughest part was the on-site interviews. There were a few different types: coding interviews where I had to solve tough coding problems efficiently, a system design interview where I had to design a scalable system for Lyft, which was a good way to show my architecture skills, a laptop assignment where I did a practical coding challenge, and a behavioral interview with an engineering manager where I talked about my past experiences and how I align with Lyft's values. They really seemed to care about how I work with others and solve problems. Lastly, there was a team matching part where I met potential team leads to see if we'd be a good fit. I liked that they put effort into making sure the role was right for me. It was tough but fair, and I got a good feel for their engineering culture, which is all about being good at tech, working together, and innovating.