The process is not yet complete. I'm just writing it down so that I don't forget. I have the onsite interview in one week, so I will edit it completely. Please do not reject it right now, and don't make it public either. Perhaps GD should consider adding a draft feature?

I had applied in October/November 2014 but received a call in late January. I showed interest and was quickly linked to a telephonic interview. Progress on that led to another telephonic interview with a senior developer. Success in that led to Yelp offering me boarding and lodging to fly to San Francisco for an onsite interview. The whole process went surprisingly smoothly.

Even before landing in San Francisco, I had communicated with a recruitment manager, interview coordinator, relocation officer, a developer, and a senior developer. The people were really nice and respectful, and I always felt that I was in good hands.

The telephonic interviews were smooth as well. They weren't very challenging if you are prepared. Surprisingly, they did not focus too much on iOS development.

An enumerator is a class with a getNextObject method. It encapsulates a container. First, write an enumerator. Next, write a new enumerator called chained-enumerator, which is initialized by two other enumerators. Finally, how would you make it work with N enumerators? I had to write the logic for getNextObject for the most part (and any other internal state I wanted to manage).

The second question was not really a question but a very healthy session of pair programming where I was speaking and a senior developer was coding. He chose Java, and we were creating a list data structure (with add, count, delete operations). The catch was that we were going to do it TDD style. So, I guided him on what kind of tests we could write and how to pass those tests, and so on. We continued doing this, and in 45 minutes, we had a very well-tested, working list data structure.