Great team – good at what they do and fun to be with. I look forward to seeing my team at work. Most of the people at Lyft are very friendly, willing to help you, and better socially than the stereotypical engineer.
High technical quality. There are some very good engineers at Lyft who I can learn from.
Fast-paced: There aren't many organizational barriers (as opposed to a larger company) to shipping code. You don't need to go through a hierarchy to get an idea across. At the same time, there is enough infrastructure (definitely could be better, but better than nothing) that you can mostly focus on your job (assuming you're not an infrastructure engineer) instead of figuring out your environment (e.g., why deploys don't work, problems with the data platform).
High impact to effort ratio. There were four server engineers on my team (two at one point), and we shipped a completely new product.
Good compensation (good enough that I never think about this. I only remembered when I had to rate my compensation down below).
The development environment can still be improved.
A few teams need to work quite long hours, so work-life balance is harder to get right.
Some teams need to do a lot of work, so it's important those team members are able to develop in a sustainable way (i.e., they don't burn out).
Overall, I think it's incredible (especially the culture), and I can't imagine myself enjoying another tech company more.
It was 2 rounds; the first was HR, followed by a technical round. It was a great interview with a good coding question, which I was able to solve, but I still couldn't make it to the next round.
During the first round, I talked to a recruiter very generally. The next round was a phone interview where I was asked a LeetCode problem. A few days later, I was told that I did not pass that interview.
One phone screen, followed by an onsite with 4 interviews. The interview consisted of: * 2 system design questions * 2 coding interviews One of the coding interviews was a laptop test, which is essentially an open-book coding problem.
It was 2 rounds; the first was HR, followed by a technical round. It was a great interview with a good coding question, which I was able to solve, but I still couldn't make it to the next round.
During the first round, I talked to a recruiter very generally. The next round was a phone interview where I was asked a LeetCode problem. A few days later, I was told that I did not pass that interview.
One phone screen, followed by an onsite with 4 interviews. The interview consisted of: * 2 system design questions * 2 coding interviews One of the coding interviews was a laptop test, which is essentially an open-book coding problem.