Fragen im Vorstellungsgespräch für Software Engineer bei Qualcomm

Multiple rounds, very well structured, DSA, OS-level programming, C/C++, concurrency, Android NDK (Native Development Kit), JNI, extra - Compilers. Overall by far the best and most comprehensive interview process I had in years!

only one interview, ask about how to write c++ also ask about how to write about the other stuff would ask some os problem, very hard and very detail. They would continue to ask for the c++

3 Rounds: All technical rounds Data Structures, C programming, Analytical abilities. Tough questions. Intelligently prepared. Pointers, Linked lists are their favs, may be ! Good preparation Efforts needed to do well.

The interview process is good but i felt it was little bit tough but overall it was a nice experience. Hope this is help full. Wish you all the best.

The interviewer asked questions on Python concepts, OOP basics. There was a coding question in Python which was a menu-driven prog that should perform mathematical operations on 2 user inputs.

they told me it would be an off camera quick interview call. Then they told me during the interview to turn my camera on, and answer a bunch of technical questions. F- for communication

1 phone screen followed by a super day(4 interviews). Phone screen and 2 super day interviews were focused on LeetCode. 1 round with hiring manager and 1 round focused on OOP design. Whole process took over 2 months and should have been quicker.

Interview process was smooth and the interviewers were helpful. Two rounds of 1 hr each back to back. I was able to answer almost all the questions and wherever I got stuck the interviewers helped me.

2 Technical Rounds - based on DSA, C,C++,OS, Pointers etc. -> 2 back to back rounds of 1 Hr Each 1 Managerial Round - related to my prev work and technical question about kernel and user space communication

Pretty straightforward, lots of basic C++ questions. Was surprised I got a second interview bc I was fumbling not expecting super technical questions. But it was mostly gauging if you were able to code, rather than testing logic.