I applied online and was contacted by a recruiter on the same day. He briefly went over the teams and the interview process, which consists of one to two 1-hour technical screens and a full day onsite.
We scheduled the technical screen for the following week. For the technical screen, you have the option of visiting their office and doing it onsite, which I'd highly recommend. Interviews over the phone and using CoderPad can be awkward at best due to the lack of face-to-face interaction, and it was also a great opportunity to check out the office and culture before getting too deep into the interview process.
The technical screen itself was fairly straightforward, and the recruiter was very open about what topics to expect. CS fundamentals and good communication were key. The recruiter got back to me with results the next day, and we scheduled an onsite for two weeks later (because of conflicts on my end).
Again, the recruiter was extremely helpful in setting expectations for the onsite. He hopped on a call with me a week before to go over the teams and engineers I'd be meeting with, as well as specific feedback from my screen. It consisted of:
Everyone I spoke to was smart, friendly, and easy to work with, and I received a verbal offer just hours later.
This was definitely the most positive interview experience I've gone through. There were no egos or weird power plays during the interview or negotiation process, and I definitely felt like the recruiter was trying to set me up for success.
Design a coupon system.
The following metrics were computed from 35 interview experiences for the Lyft Software Engineer role in San Francisco, California.
Lyft's interview process for their Software Engineer roles in San Francisco, California is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Lyft's Software Engineer interview process in San Francisco, California.