Taro Logo

Data Engineer Interview Experience - San Francisco, California

February 26, 2020
Neutral ExperienceNo Offer

Process

A recruiter reached out to me on LinkedIn. After discussions, I was set up for a phone interview using Coderpad. The phone interview included one SQL and one Python question, which I managed to solve with a few hiccups. I was then set up for an onsite interview that had five rounds and lunch with a team member.

Onsite

  • 1st round: General discussion about my profile and a LeetCode problem. I partially finished but couldn't complete it due to running out of time.
  • Lunch time: I waited for the team member who was supposed to take me to lunch, but they never showed up, and I missed the meal.
  • 2nd round: SQL coding on a MacBook with a MySQL session. The interviewer was busy with Facebook and didn't know or answer any of my clarifications. All three queries went unanswered because I didn't get the clarifications and wasn't sure what to expect.
  • 3rd round: The interviewer introduced himself and started with a behavioral round, asking about previous work experience.
  • 4th round: System design round. I was asked to design a distributed system with failover considered.
  • 5th round: Lyft use case for designing a dimension model.

Overall, it was a less-than-average onsite interview, and as expected, I didn't get the offer.

Questions

LeetCode questions

Was this helpful?

Interview Statistics

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

Success Rate

0%
Pass Rate

Lyft's interview process for their Data Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive33%
Neutral33%
Negative33%

Candidates reported having mixed feelings for Lyft's Data Engineer interview process in San Francisco, California.

Lyft Work Experiences