Lyft Software Engineer interview questions

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 1-2 1hr 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 coderpad at awkward at best because of 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 four technical sections (two design, two coding), lunch, and a chat with a hiring manager. 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.

They contacted me by email and scheduled a phone call with a recruiter. There was a misunderstood with the time, so we had to reschedule the call (I read this also happened to someone else). After this call I had a 45 minutes technical call with one of their engineers, we had an interesting conversation about the role and the company. Finally, they asked me to do a homework task, which was supposed to take 2 days and I did it. I'm really used to build mobile apps, I've been working as iOS developer for over 5 years, and I've built several apps featured on the appstore, so the task was quite easy to implement. I was really confident with the solution I implemented, but after 5 days they just told me they were not moving forward with my application. Exactly the same I read in other comments. It's fine if you don't get hired, I'm sure there must he great engineers appliying for the same position, but they should at least give you a useful feedback about why you're not the proper candidate. Read all the comments before applying, otherwise you will waste so much time for nothing... Uber does much better on this.