I had a phone interview with a Software Engineer. After one and a half months, I received an email from HR to schedule an onsite interview. I was really surprised, as I had no hope.
• Round 0: HR asked a few generic questions about my interests and explained the interview process.
• Round 1: Intersection of two sorted arrays.
• Round 2: * Count the number of 1s in an unsigned integer. * In-place matrix transpose.
• Round 3: * How are main() and functions stored in memory? * Identifying successful copying from a source to a target array when the target may have overlapping elements. * What happens when a packet is lost in TCP?
• Round 4:
* Diversity techniques: Why are they needed? What happens in multi-path?
* Inter-Symbol Interference analysis in the frequency domain.
* C Questions:
* static int a = 5;
* int a = 5; What is the difference between these two? Where are they stored?
• Round 5: * What happens when a low-priority task holding a lock is preempted by a high-priority task? * Some more questions, which I don't remember now!
Some of the questions were unclear, which showed me that they were not at all interested in conducting a proper interview.
The following metrics were computed from 8 interview experiences for the Qualcomm Software Developer role in United States.
Qualcomm's interview process for their Software Developer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Qualcomm's Software Developer interview process in United States.