Qualcomm Product Test Engineer Interview Questions & Reviews
Getting an Interview
- Popular Job Titles:
- Software Engineer (128)
- Intern (52)
- Senior Software Engineer (31)
- Engineer (31)
- Embedded Software Engineer (30)
- Engineering (25)
- Software Engineer Intern (18)
- Systems Engineer (16)
- Hardware Engineer (15)
- Senior Engineer (14)
- Verification Engineer (14)
- Test Engineer (13)
- Systems Test Engineer (12)
- Associate Engineer (11)
- Internship (11)
- Interim Engineering (11)
- Interim Engineering Intern (10)
- ASIC Design Engineer (9)
- Senior Systems Engineer (8)
- Staff Engineer (8)
- Digital Design Engineer (8)
- Staff Software Engineer (7)
- Modem Systems Test Engineer (7)
- Modem Test Engineer (6)
- Design Engineer (6)
- Program Manager (6)
- Hardware Test Engineer (5)
- Senior Staff Engineer (5)
- Embedded Software Developer (5)
- Design Verification Engineer (4)
Product Test Engineer Interview (Negative Experience; Difficult Interview)
I applied through a recruiter and the process took 3 months - interviewed at Qualcomm.
Interview Details – This was one of the strangest (and worst) interviews I have ever had. I was initially contacted by a recruiter in Feb., and told they would contact me the next week. I didn't hear from them until late April, when I was contacted again by recruiting. I proceeded to do a phone interview with a hiring manager (who was apparently not the hiring manager for the actual position). That interview was composed of a few technical questions, and wasn't too difficult. All the questions were related to the job and my background. The job had been posted as being available in Austin or San Diego, and I inquired about the location. The hiring manager responded that he wasn't sure where the job would be located. The location was important to me because I live in Austin and am not willing to move to San Diego.
After that, I was invited to their Austin office for in-person interviews. I was told that there would be 4 hours of interviews, consisting of 4 people for 45 minutes each, and 1 HR person. I ended up interviewing with only 2 people and the HR person. The two people that I interviewed with apparently were not hiring managers (they really didn't take the time to explain who they were). Both of their interviews were 100% technical. The questions ranged from easy to difficult, although the difficulty would be relative depending on your experience and background. It seems they actually were not looking for a product/test engineer, but an analog test engineer. I don't have a lot of analog background, so those questions were difficult for me. Both interviewers acknowledged they realized it was not a big part of my background. Both also asked me if I was willing to move to San Diego, and I said I was not. The location of the position, it seems, was still up in the air. I was really surprised that neither of these people asked any behavioral questions at all, or even "Why do you want to work here?". One guy didn't even tell me his title until I managed to squeeze in a question about it. Speaking of which, they left no time at the end of the interview for me to ask any questions of my own. Not impressive.
After these two folks, I met with the HR person. After her, I was supposed to meet with the hiring manager. However, during my talk with her, the hiring manager notified her that he already thought that I wasn't a good fit, that I did not have the skill(s) they were looking for. All that without ever meeting me. At that point, I told her that was fine and we could end the process right then. To her credit, she felt bad and said that she felt it reflected badly on them (which it does).
What this tells me: 1) They hire for skills alone, not personality or character, or other traits. They don't care about one's ability to learn. They couldn't have cared less about me as a human being. I've always been of the opinion that skills can be taught, but character can't. 2) They were not very organized - they couldn't even decide where this position would be located, but were interviewing anyways. 3) By not giving me any time to ask my own questions, they let me know that they were not interested in finding a mutual fit - just in finding a body that had the skills they apparently needed.
Interview Question – Given an array of 10 numbers, all 0 or 1, write code to turn the 0's to -600 and the 1's to 600 without using any if/then or switch statements. View Answers (3)
Product Test Engineer Interview (Positive Experience; Average Interview)
I applied online and the process took 4 weeks - interviewed at Qualcomm in May 2013.
Interview Details – Destination Q program for the PTE. No phone 1 on-site.
Met 3 people, 45 min each
All the questions are about the resume. People are very nice
Interview Question – The most difficult part of one project and the solution to that problem.
CMOS related questions. Answer Question
Product Test Engineer Interview (Negative Experience; Average Interview)
I applied online and the process took 4+ weeks - interviewed at Qualcomm in January 2013.
Interview Details – Received a phone call for Destination Qualcomm Event and went for onsite interview in January , 2013.
Interview Question – Three rounds of interview.Basic questions on op-amps, RF, filters and projects mentioned in resume. Answer Question
Interviews for Top Jobs at Qualcomm