Someone at Uber reached out to me about a role there.
First step of the interview was a phone screen. It was high-level and conceptual, and given by an early tech employee who wasn't HR but, at this point, wasn't entirely a hands-on tech person either. They had moved into more of a director/operations role.
It asked some basic tech questions, but I don't think the person was expert enough in iOS itself to ask difficult questions.
Next was an at-home coding challenge. Take as much time as you want, but the expectation was within a few days to a long weekend. I completed it over an entire weekend and put substantial work into it. It was a straightforward iOS question with an API and UI elements. I put a lot of work into it.
After reviewing the submitted challenge for a few hours, I received word back that there was a flaw in a UI element, and we would not be moving forward. But they thanked me for spending my entire weekend on it. There was no discussion, no further communication.
After further investigation, I confirmed my flaw. A little frustrated because it clearly showed I was adept and could do the work with overall nice features, but also not happy with myself for my mistake that I didn't initially see in the UI.
Common iOS questions
The following metrics were computed from 7 interview experiences for the Uber iOS Engineer role in United States.
Uber's interview process for their iOS Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having mixed feelings for Uber's iOS Engineer interview process in United States.