Mission: To unite humanity and technology in order to make everyday rides welcoming, affordable, and memorable.
I have been working at Lyft part-time (More than a year)
Lyft was made to share your car with others. Honestly, I am ok with that especially if its for gas money. I have been going through job pitfalls recently and have discovered that driving in the morning or evening rushes has giving me the money I need to pay a couple of bills. I love the flexible hours that I have created for myself but I recommend it only for part-time because its your vehicle your vehicle up keep isn't cheap
In my city, its a big city I recommend going to a certain area where you don't have to drive too far. I mean going towards the client, you don't get paid until the client is in your car. That is something I don't like because I take into account traffic and mileage. It may take you 12 min to pick somebody up but once the person is in your car it may take 5 minutes get him or her to its destination and what you gain from those 5minutes in your car is simply not enough. Just Keep in mind that you will drive more than you expect to receive back. It's not always the case but I have been going through some of those lately.
Advice to Management
I like the bonuses but sometimes they are not clear enough, I feel we should get an email instead of explaining on a text what the $300 bonuses work or something like that. I like the idea that y'all keep the constant (don't text and drive). I appreciate that as a driver. So far the updates on how payment works has been great but would like to see an improvement in when we go to pick someone up for over 10minutes of our own destination.
I applied online. I interviewed at Lyft.
Pretty Professional and smooth interview process.
Had a initial recruiter phone call and after that was scheduled to speak to one of the Senior engineers over on their team.
The interview was difficult. There were 2 questions asked in the interview on coderpad.
1.) A small android challenge. Some basic questions about Android and then a deep-dive into a specific topic. Over here looks like the interviewer was looking for a specific answer and i was finding it hard to gauge what he was exactly looking for, in the end he gave me the hint and then i answered.
2.) Coding question. This was a difficult problem to solve. Think about leetcode hard. And he was very specific about what he wanted.
The question was to implement a LRU cache but for the backing data structure only an ArrayList can be used. It is solvable if there is another data structure like a hashmap which you can use or obviously a queue(which kinda beats the point) but a single arraylist was tricky to implement in 25-30 mins and that too a working solution which passes the test cases the interviewer had got with him.
A peek behind the scenes of our office in beautiful downtown Nashville: http://glassdoor.com/slink.htm?key=vQA7P
Co-Founder and President John Zimmer chats with Ty Burrell about the future of transportation for National Geographic: http://glassdoor.com/slink.htm?key=vQA7v
Let us know if we're missing any workplace or industry recognition –