Qualcomm Interview Questions & Reviews

Interview Details – I initially had a group phone interview that lasted about 10 minutes until I was passed on to next stage. At my in-person interview, I first met with an HR person and went over some basic info. I then met with a panel of four supervisors. Lots of questions about my resume, but the interview felt unstructured and ad-hoc with lots of silences. One of the interviewers seemed like he was upset - he barely made eye contact with me. Odd experience.

Once the interview concluded, one of the managers walked me out and said that I would be brought back in for another panel interview, but I never heard from them again. Surprisingly unprofessional from a company this large.

Interview Details – Phone Interview : Pretty much standard questions about static keyword, Linked Lists and then finally the interviewer showed me few pieces of code on google docs and asked to find problems in them if any like Memory leaks. Segfaults etc. Later, I found out that the questions were picked up from some website word-to-word. I gave answers to almost all the questions but failed to notice problems well in the last two pieces of code. It's ridiculous, that it was the basis of rejection.

Also, the interviewer kept boasting about how he has worked in almost all the areas that I can possibly name. I am not saying mine was a stellar performance, but overall negative attitude by interviewer and Negative interview.

Interview Details – Applied online. Some questions asked:
Write code to:
1. convert from big endian to small endian.
2. convert decimal to binary.
3. Return the n element from end of a linked list.
4. Count the occurrence of every word

Interview Details – Appied online. Met 5 interviewers. Kind. Got offer and completed whole process in 3 weeks.

Negotiation Details – not so much. a little bit trimming

Interview Details – 1. Had a phone screen where I was asked general system vulnerabilities, Buffer Overflow, Heap overflow. Also asked questions on my resume.
Gave a code, and told me to find the vulnerability in the code.

2. Was called onsite, where had 5 interviews. Again, was asked similar vulnerabilities questions. Each interviewer had a set of code where i had to find vulnerabilities.

Important to know about integer overflows, TCP/IP network vulnerabilities, buffer and heap overflows, format vulnerability, return to libc attack, overwtiting the frame pointer and security impact of that.

Interview Details – Campus interview.
Two Technical interviews 45 mins each

Interview Details – it's a long interview from 9:30 am to 4:50 pm.there are 6 interviewers.the first one just ask for you information. the other 5 interviewers asked technique question. they were asking me questions even when I was having lunch. It's a long day. So be prepared. Sleep well the night before.

Interview Details – 1 hour of phone interview and about 5 hours of onsite interview

Interview Details – The interview process started with a recruiter contacting me with the details of the position and a time slot for a phone interview.
The phone interview was pretty simple, asked a few questions about RTOS : mutex, semaphore, stacks and heaps. Also asked a C question: what will be the address of an integer pointer after increment of the pointer variable directly.

Once I cleared that, the recruiter confirmed a time slot for an onsite interview.
The onsite interview had 7 rounds including a HR round which usually lasts from 9-5pm.
The HR round just includes some basic questions about your current job and your salary expectations.
The next 6 rounds included interviews with director of engineering, senior staff engineers and staff engineers.
The questions were pretty basic. Mostly in C language such as strcpy, strlen,bit counting etc...