QA Automation Engineer applicants have rated the interview process at Lyft with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 63% positive. This is according to Glassdoor user ratings.
Candidates applying for QA Automation Engineer roles take an average of 7 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at Lyft overall takes an average of 20 days.
Common stages of the interview process at Lyft as a QA Automation Engineer according to 2 Glassdoor interviews include:
Phone interview: 100%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 1 week. I interviewed at Lyft in Apr 2016
Interview
I applied online through their website and got a call from their recruiter. She was prompt and quickly scheduled for a technical phone screen. I spoke to the manager of the team for about about 45 minutes. The first 20 minutes was about the team and what they do ; and the expectation from this job role. And then we delved into the coding problem. I eventually didn't make the cut, but they were courteous to call me back and let me know the results and feedback . The whole process was very professional - both while interacting with the recruiter and the manager.
I applied through an employee referral. The process took 1 week. I interviewed at Lyft (San Francisco, CA) in Jun 2015
Interview
I had my friend at Lyft submit my resume. I heard back from them within 15 minutes to schedule a phone interview for the week after.
I didn't talk to the person I was expecting to speak to, and it wasn't as casual as the recruiter made it out to be when I asked, which was fine.
The interview experience was quite unpleasant. It was obvious that he didn't want to be on the phone and listened to maybe 25% of the answers coming out of my mouth. He asked me a question, I answered, he prompted for a more correct answer and then gave me the exact same answer that I had answered. Then he asked me various forms of the exact same question multiple times in a row. I wasn't really sure what he was looking for, since it had to do with how testing is divided up on my current team. Maybe the way we do it at my company is wrong?
Either way, wasn't expecting to hear back, nor did I really want to. The interview proved that my time and effort was not valued.