Qualcomm had the following four rounds of interview process
- Aptitude + Programming MCQs + Technical MCQs
- Tech Interview 1
- Tech Interview 2
- HR Round
It had 3 sections
- i) General aptitude (medium level)
- ii) Programming MCQs : Many output based questions, object oriented concepts(interfaces, classes), pointers, operator precedence, scope and lifetime of variables, storage classes related questions.
iii) Technical MCQs: Mainly operating system, computer architecture and data structures related questions were asked.
Note: Questions were easy and a few were tricky. The key to clear is to manage the time and mark only the questions you know (as each question had 0.25 negative marks).
Round 2: Technical Interview 1:
? He asked me to introduce myself and asked why did I leave job and took admission in M. Tech.
? He started asking the third project which I had mentioned in the resume which was related to GPU. He didn’t go in depth of the project and it looked like he just wanted to know if I recall the project :P.
? He then asked me, if I am comfortable with C++. I said yes, I’m pretty comfortable.
? He asked to explain the concept of VTable. He expected me to know where it is used and how is it implemented. I started explaining him the dynamic polymorphism through virtual function and explained how Vtable and the virtual functions are mapped and also I explained him about vptr concepts used.
? He then asked me to write a singleton class. I explained to him the concept but he insisted me to write a class for the same. I was able to answer it by using static bool variable. Although it was not perfect, he seemed okay with the implementation.
? What is volatile keyword?. Explain any other compiler optimization techniques.
? Questions related to fragmentation, paging, cache memory, threads, mutex, counting semaphore, binary semaphore were asked.
? What are the disadvantages of inline functions?. I explained to him what are inline functions and I was thinking about its disadvantages but he didn’t let me think and said, thanks for your time.
Interview went for around 25 mins. For others it went anywhere from 25-60mins.
Round 3: Technical Interview 2
? This round was very easy for me. As I had computer architecture in resume, he asked me to explain how CPUs work. I wrote the cpu architecture diagram and explained each component. He expected me to explain instruction execution cycle in detail(stages, addressing modes etc., ). He asked if ARM uses the same pipeline stages and difference between RISC and CISC.
? Explain the role of MMU.
? Page size in linux.
? 2D array dynamic memory allocation: https://www.geeksforgeeks.org/dynamically-allocate-2d-array-c/
? He asked two famous puzzles.
- i) http://www.mytechinterviews.com/apples-and-oranges
Interview ended in 20-25mins.
Round 4: HR
? Introduce yourself
? He did not ask me any further questions and started explaining about Qualcomm and its criteria. I asked questions in between to clarify many doubts I had(related to team allocation, kind of work, team preferences, location preferences, internship related etc., ).
HR was also a filtering round, a few students who gave HR were not in the final list (Not sure about the criteria used for the final list).
Feel free to ping me for any help at https://www.linkedin.com/in/sujay-raj-728376102/
- Qualcomm Interview Experience (Off Campus)
- Qualcomm Interview Experience (Off-Campus)
- Qualcomm Interview Experience | Set 17 (On-Campus)
- Qualcomm Interview Experience (On campus)
- Qualcomm Interview Experience | Set 19 (On-Campus)
- Qualcomm Interview Experience | Set 7 (On-Campus)
- Qualcomm Interview Experience | Set 10 (On-Campus)
- Qualcomm Interview Experience | Set 14 (On-Campus)
- Qualcomm Interview Experience | Set 11 (On-Campus)
- Qualcomm Interview Experience | Set 6 (On-Campus)
- Qualcomm Interview Experience | Set 15 (On-Campus)
- Qualcomm Interview Experience | Set 7 (Off-Campus)
- Qualcomm Interview Experience | Off Campus
- Qualcomm Interview Experience | Set 13 (On-Campus)
- Qualcomm Interview Experience | Set 12 (On-Campus)
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to email@example.com. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.