Updated by Lyft candidates
Interview process
Started with background discussion. Interviewer asked about a specific project i mentioned on the resume and dug into details. As for the coding challenge, I was given an existing package which contained an API for reading 4 bytes of data at a type from a file. To read 10 bytes, we had to call this underlying API 3 times to get 12 bytes, respond back with the requested 10 bytes, and keep the extra 2 bytes of data in memory for future calls. I solved this with a queue-based implementation, handling edge cases around reaching the end of the file. Got follow-up questions related to handling API call failures, retries, and streaming the output.
- Technical interview
Interview rounds
1 question across 1 roundTechnical interview
1 questionQuestion types asked
Specific questions asked
Read data from file using a buffer. (Similar to leetcode 158)
Interview tips
Go through the company's coding question bank.
Get full access with a membership, or share your experience to try it free.
More Lyft interview experiences
“The process wasn’t as long as I expected. My onsite was supposed to be four rounds, but they cut it to just two, and one of them was a time-based key value store with delete at a specific timestamp given in the full spec up front.”
“Pretty standard interview process - the recruiter was very nice and collected information, and guided me through the expectations for the interview. The sense and execution interviews were also pretty standard - interviewers help you along if you get stuck. I had to answer some questions related to Lyft as well as a spotify question.”
