I applied online. I interviewed at Lyft in June 2017
Interview
HR Phone Screen, Technical Phone Screen, CoderPad. Pretty lame in general b/c the first 2 calls were very bullish about the role, and my specific background fit. Then we get to the "CoderPad" session. It was a basic question, but was explained very poorly (on whether/which existing packages could be used or which needed to be written from scratch. The call quality was also difficult. Overall it was challenging but I answered the question fine after figuring out what they wanted. Had a few bugs in the initial solution which required some print outs. But given all the specifics and demonstrable code that was easily shown in my background, to so quickly (1 day) discount a 30 minute mickey mouse coding session seems pretty lame. If you don't have 100% coverage of every possible stupid question you will be asked, or stumble just a bit with Coderpad, they'll cut you free, even if you have worked the EXACT role they are hiring for at another company.
Interview questions [1]
Question 1
One of the silly questions about doing something that you'll never do in the real world.
Jumping into the technical phone screen, I was pleasantly surprised when the interviewer asked me to design a driver-rider matching service, something I had just practiced in-depth on PracHub. The prep I did really paid off, as I navigated the complexities of indexing live driver locations and addressing high write rates with confidence. The full virtual onsite included two coding rounds and a system design question, along with behavioral interviews. While I appreciated the opportunity, I ultimately declined the offer for different reasons unrelated to the team. The overall experience was intense but rewarding.
I applied online. I interviewed at Lyft (Ciudad de Mexico) in May 2026
Interview
Solo llegue al challenge que es leet code hard de los mas comunes es una ventana de desplazamiento esta protectorado con un humano.
El screening es bastante especifico y se hace con recruiter validan ingles y que des ejemplos de proyectos de sistemas distribuidos en tu haber.
El problema con los leetcode es que dejan de lado a los candidatos neurodivergentes que piensan en profundidad.
I applied through a recruiter. I interviewed at Lyft (San Francisco, CA) in May 2026
Interview
the process is pretty straightforward. first recruiter screen, tech screen, and then onsite (system design, behavioral, and laptop). you may or may not meet the manager of the team you are interviewing for during the onsite behavioral. the laptop round is basically OOD.
Interview questions [1]
Question 1
tech screen is leetcode specific, system design is OOD related, and behavioral has bunch of questions instead of talking about one specific projects.
