INTERVIEW PROCESS:

The usual process involves three phone screens and one onsite interview with multiple people.

I was initially contacted by a technical recruiter for a pre-screening, leading to the next level of interviews. I was screened for the subsequent call, and the following questions were asked in the next rounds.

There were a few questions in the first round, and then a second round was scheduled.

One interview started with a simple "hi" and immediately jumped into highly technical questions in a rapid-fire manner:

• I am proficient in C, C++, and Objective-C. The interviewer asked about memory allocation in C and C++.
• Remove duplicates from a list with the best time complexity.
• Keywords: "@property", "synthesize", and the difference between "atomic" and "non-atomic".
• Virtual functions and overloading, overriding functions.
• Design Patterns.
• Difference between hash and array in Perl.

This interview process lasted 30 minutes.

While the experience was acceptable, it felt more like a timed question-and-answer session.

Finally, I was told they would get back to me after a discussion with senior management.

They simply said they would get back to me and there was no response, which I assumed meant I was declined.

It was a decent experience, but remember you need to be attentive and answer questions in depth.

Remove duplicates with best time complexity.

Inheritance, Polymorphism in C. Memory allocation in C, C++. What does the new keyword do?