Stuff you work on will generally be interesting.
Coworkers are pretty good.
Solid process for programmers (versioning systems, code review, etc.).
Large enough teams so work is evenly distributed.
Good opportunity to be exposed to new things.
Best pro is that I'm usually into my work enough that time passes by quickly, and I'm generally excited for Mondays.
No commitment to the flow of knowledge. You can often be assigned to an unfamiliar project with very little idea of what you're supposed to do. The project lead will have the high-level overview, but good luck getting them to explain it to you. More often than not, it's baptism by fire. To be fair, they're getting better about documentation now.
Code quality varies across teams, drastically. A lot of legacy code needs to be maintained.
Workload is very unpredictable. There are weeks when you have nothing to do and weeks where 24 hours isn't enough in a day.
Some of the higher-level managers have overly aggressive deadlines, and no one bothers reigning them in.
Too much administrative crud (I assume it's everywhere).
Pay comparatively sucks.
Quit touting San Diego as the place to be and hence offering a lower salary. Salary hikes during promotion are nothing to speak of. In short, Qualcomm needs to be far more competitive with its peers in the industry as far as compensation is concerned.
I'll admit the benefits are very good.
This interview was for a computer vision engineer. I worked with the HR department to schedule a phone interview. The phone interviewer asked me about the LoG function, corner detection, and their time complexities. He seemed very capable and accomp
Telephonic round: - A few bit manipulation questions - One or two coding questions - A few standard OS concept questions - A few questions based on your resume Onsite: - Four rounds of interviews, each spanning 45 minutes (one interviewer may exte
I applied online for a software engineer position at QCT. After four days, I received an email inviting me to a phone interview. The phone interview took place three days later. A senior software engineer called and asked questions based on my resume
This interview was for a computer vision engineer. I worked with the HR department to schedule a phone interview. The phone interviewer asked me about the LoG function, corner detection, and their time complexities. He seemed very capable and accomp
Telephonic round: - A few bit manipulation questions - One or two coding questions - A few standard OS concept questions - A few questions based on your resume Onsite: - Four rounds of interviews, each spanning 45 minutes (one interviewer may exte
I applied online for a software engineer position at QCT. After four days, I received an email inviting me to a phone interview. The phone interview took place three days later. A senior software engineer called and asked questions based on my resume