Taro Logo

Software Engineer Interview Experience - San Francisco, California

January 1, 2019
Negative ExperienceNo Offer

Process

The feedback I received from the interview doesn't align with my performance. Regarding the laptop coding test, I was told I didn't add any comments or explanations for optimization, which is false. I attempted to explain this to the interviewer, but they weren't very interested and asked me to add it as a comment, which I did. In my opinion, the Javadoc comment for optimization was clear, and the algorithm's complexity was sufficient to solve the problem's constraints (n log n for 10^5 data points).

The initial debriefing took 25-30 minutes instead of the allocated 15. This was because the interviewers struggled to resolve my confusion regarding a test case. Consequently, there wasn't enough time at the end, and we finished in a hurry.

In the CS fundamentals interview, it was stated that my solution had a memory leak. However, we were dealing with approximately 40 data points, making a memory leak practically difficult to observe. A more helpful hint from the interviewer might have been to ask if such a solution could lead to potential problems at a larger scale. Aside from this, the interviewer informed me that the solution had this problem rather than asking if it had any potential issues.

Was this helpful?

Interview Statistics

The following metrics were computed from 35 interview experiences for the Lyft Software Engineer role in San Francisco, California.

Success Rate

26%
Pass Rate

Lyft's interview process for their Software Engineer roles in San Francisco, California is very selective, failing most engineers who go through it.

Experience Rating

Positive63%
Neutral9%
Negative29%

Candidates reported having very good feelings for Lyft's Software Engineer interview process in San Francisco, California.

Lyft Work Experiences