Taro Logo

iOS Engineer Interview Experience

December 27, 2019
Negative ExperienceNo Offer

Process

The recruiter reached out and scheduled a phone interview. This interview had four parts, after which I was invited to the office for an in-person interview. There were four rounds at the office:

  1. System design
  2. Write an app you've designed
  3. Code review with a group of rude, arrogant, and unprofessional individuals
  4. Behavioral interview with the Engineering Manager

Apart from the phone interviewer and the behavioral interviewer with the EM, every other interviewer brought someone else to shadow the process.

The app had one main functionality and three bonus features. I completed the main functionality, exceeding expectations, and one bonus item.

Naturally, I approached it in a startup-like manner, not handling every single edge case within the 1.5-hour time limit.

The code review began. From the outset, they seemed to want to assert their superiority, perhaps because I was transitioning from a FAANG company. One question evoked a strong reaction from me.

They asked the cliché question about the difference between a class and a struct. As I listed the differences, I mentioned that one is passed by reference and the other by value. One of the interviewers sneered and asked, "Yeah, but what's the meaning of 'by reference'?" I received many similar negative signals throughout this session, which lasted about 1.5 hours – it was excessively long.

Questions

There are four squares at the bottom of the screen, each with one color. Once you select one square, the selected color will be that color. (This part was prebuilt.)

Now, you may select any of these colors and tap on the screen. You should create a square with that color and place it on the screen.

Next, add a number to each square you put on the screen. For example, if there are two green squares and one blue square already on the screen, the next green one should be number three. (Use a dictionary to track the latest number for each color: tracker = [UIColor: Int])

Next, implement undo functionality (use a stack).

Finally, introduce a redo functionality (use a second stack).

On-site Interview:

Hit an API that returns photos. Create a photo browsing app like Instagram.

Was this helpful?

Interview Statistics

The following metrics were computed from 4 interview experiences for the Lyft iOS Engineer role in United States.

Success Rate

25%
Pass Rate

Lyft's interview process for their iOS Engineer roles in the United States is very selective, failing most engineers who go through it.

Experience Rating

Positive25%
Neutral25%
Negative50%

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

Lyft Work Experiences