Taro Logo

Software Engineer - Android Interview Experience

October 1, 2020
Negative ExperienceNo Offer

Process

It was a phone interview with a recruiter. In most cases, I didn't have a problem with this phase of the interview, as it's not technical. However, this time, I didn't pass.

The recruiter was 10 minutes late (I didn't have this problem with most companies). Okay, let's say that can happen. The problem is that he cut the interview short to 20 minutes, which is a very short time to represent myself and learn about the company.

He was very quiet and didn't ask the right questions. He asked if I knew RXJava, Dagger, Retrofit, and Glide, and a little bit about my career. I was expecting questions that would allow him to learn about me and my career in detail.

When we finished the call, I was 100% sure I would receive a negative answer. It wasn't just a gut feeling; I sensed it from his behavior during the interview. So, I asked if he could share the information right away, but he insisted he needed to check with someone and then they would get back to me.

The biggest concern is whether I just had bad luck with this recruiter. Perhaps others are fine, but how can I re-run the interview process? I'm really disappointed that I didn't have a chance to showcase my Android skills.

Questions

Did you use RxJava, Dagger, Retrofit, or Glide?

What is your past experience?

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Lyft Software Engineer - Android role in United States.

Success Rate

0%
Pass Rate

Lyft's interview process for their Software Engineer - Android roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Lyft's Software Engineer - Android interview process in United States.

Lyft Work Experiences