Envié una solicitud electrónica. El proceso duró 5 semanas. Acudí a una entrevista en Qualcomm (Boulder, CO) en feb 2017
Entrevista
2 weeks after applying online I was contacted by the hiring manager for a technical phone screen. We went over pointers and simple function design/testing on a shared word document. 2 weeks later I went in for a full day interview at the Boulder campus. There were 13 other candidates there doing the same thing. I had (4) hour long technical interviews with different members of various teams and (1) half-hour long interview with HR. They fed us lunch and did a brief recruiting presentation. 2 weeks later they sent a generic email stating "Although we were very impressed with your background and qualifications, we are unable to offer you a position with Qualcomm at this time."
Overall it seemed like they were more interested in finding book worms fresh out of school with no practical working experience than someone with actual embedded engineering experience.
Make sure to study linked lists, linked lists, binary trees, and more linked lists because that is all they seem to care about!
Preguntas de entrevista [7]
Pregunta 1
white board: find the first non-recurring character in a string. i.e. input "abbcdcaea" would return "d"
they call you and ask you the your availability and typical interview goes for 3 hours if they are interested. They ask C questions and your project related questions. At last a manager comes and takes your interview.
I had 1 screening round with 4 onsite rounds . All the rounds focuses on basic C concepts and additional concepts specific to role. Prepare behavioural questions related to your past work experience
Acudí a una entrevista en Qualcomm (San Diego, CA)
Entrevista
Applied online. Recruiter reached out to schedule 2 technical interviews , 1 was about C/C++ coding , as well as fundamental coding / memory concepts. And another was a deep dive about items on my resume focusing on both technical and other aspects. Thought they went good but didn’t get the offer
Preguntas de entrevista [1]
Pregunta 1
Going through code snippets and finding issues/ changing code