The interview process began with a phone interview, followed by an invitation for an on-site interview. I had to fly from California and take two days off from work for this.
The interview consisted of a surprise panel. I was not informed of the details beforehand, so I was surprised by a panel of five people upon arrival. I performed well despite being blindsided.
Everyone was nice, and I answered all the questions while conducting myself well, as I am comfortable speaking to groups. Next, another panel was brought in to assess my coding, problem-solving, OVM, and other technical validation/verification skills. I answered all their questions.
After the technical sessions, the hiring manager asked to speak with me privately. I expected a discussion about salary requirements, but instead, he inquired about my RTL debug experience. I openly stated that I debug at the interface level, such as where components connect to a fabric.
Later that day, I received an email stating they were seeking a candidate with more design and RTL debug experience. I was confused because I had never claimed to possess that specific expertise and had been very clear about my experience. They could have clarified this over the phone, saving considerable time.
How do you verify the connectivity of an interface to memory with 6 bits of address and 6 bits of data?
Show me a program that will write, read, and verify the connectivity.
The following metrics were computed from 4 interview experiences for the Qualcomm Verification Engineer role in Raleigh, North Carolina.
Qualcomm's interview process for their Verification Engineer roles in Raleigh, North Carolina is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Qualcomm's Verification Engineer interview process in Raleigh, North Carolina.