I had my first phone interview. It was scheduled one week after applying online, and I was very excited about it.
I got very disappointed very quickly, as the voice quality was poor and the interviewer spoke with a strong foreign dialect. It was very hard for me to make out acronyms like ARC, GCD, MVC, and MFC. I had to ask them to repeat questions multiple times and also had to rephrase/repeat my own answers in order to understand what was being asked of me. Other than that, the questions were only technical in nature.
The interview took exactly 45 minutes. I quickly figured out a pattern in the replies to my answers. If the interviewer replied "Excellent" or "Exactly," I obviously got a checkmark in the "correct answer" block. If I answered a question not exactly as it stands in the books (because of experience, you sometimes break the rules/patterns knowingly), I only got a "That's fine" or "It doesn't matter." (Really? One would think everything you say would matter...)
I initially thought I answered most questions correctly, but I think I plainly misunderstood one or two questions asked, just because of the difficulty in being able to hear and understand the person. It turns out I answered more questions wrong than I initially expected.
In the MVC pattern, where does communication with a server fit?
What is the difference between Objective-C's automatic reference counting and garbage collection?
The following metrics were computed from 1 interview experience for the Qualcomm Software Engineer - OS X & Linux Applications Development role in San Diego, California.
Qualcomm's interview process for their Software Engineer - OS X & Linux Applications Development roles in San Diego, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Qualcomm's Software Engineer - OS X & Linux Applications Development interview process in San Diego, California.