I applied online and was contacted by the recruiter. The first task was a take-home project over the weekend. The preferred language of choice was Swift. Although my current job is in Objective-C, I was trying to make a switch to Swift, so I decided to do the project in Swift anyway.

The second round was a phone screen with one of the iOS engineers. The recruiter had mentioned that it would be a discussion on the take-home project. Unfortunately, it was not just a simple going over the project. In fact, we didn't go over the project at all! It was a deep dive into iOS with a good amount of focus on Swift! I tried to convey that my experience was mostly in Obj-C and that the purpose of doing it in Swift was to show that I could learn something quickly and still come up with a good project. I guess it became a chicken-and-egg problem.

Honestly, I blame the recruiter here. He didn't convey properly what to expect in the phone screen, otherwise I would have been definitely well-prepared, even with Swift questions. But the devs had something else in mind. It would have saved time for all of us.

Drawbacks of using storyboards

Difference between protocols and inheritance Difference between structs and classes Mutating structs and mutating classes Difference between unowned and weak Explain retain cycle with example Drawbacks of using singleton Difference between MVC and MVVM What is MVVM bindings Escaping vs non-escaping closures What is the responder chain Difference between GCD and Operation Queues Frames vs Bounds