I was called by the recruiter and scheduled a technical phone interview soon after. The process was quick and smooth.

The interview focused mainly on mobile architecture. While I have past experience in mobile development, I wasn't too familiar with architecture details and consequently faltered a bit while answering.

This was followed by a question on a design pattern. I had never heard of this pattern before. I took my time to understand the question with some help from the interviewer.

Within 3-4 minutes, he became frustrated and told me he was looking for developers with better coding skills. I disagree that I have bad coding skills solely because I couldn't answer a question without frustrating him. He should have understood that it is difficult to implement a design pattern when one has never heard of it before.

I would have expected him to move on to another question. Instead, he gave up and ended the interview.

I found it unfair to gauge someone's knowledge by asking a single question when there are numerous other equally relevant CS topics to discuss. All in all, an opportunity was lost due to the interviewer's mood and impatience.

1. Say there are a bunch of records (either photos, news feed, or videos) to be displayed as a feed on a mobile app. How would you improve the performance of such an interface?

2. Implement the bus event design pattern.