The products/solutions that Qcom develops are very impactful to the world in a good way. Big organizations and broad expertise offer a chance to develop tech skills breadth-wise and depth-wise, if you are willing to put in extra effort to follow up with fellow engineers. (BTW, documentation sucks.) San Diego is an awesome place to live.
As mentioned earlier, documentation at Qcom sucks. You need to approach the right people with the right leverage and be very persistent, or else you can't get things done on time.
Qcom internal tools suck.
If you have counterparts at different geo locations, work-life could be difficult sometimes. While it's advantageous to have a team spread out across multiple locations, it's very important to have proper etiquette here.
The annual review process sucks. I hate matrix organizations. There's a line manager whom you don't work with, but he/she is responsible for the annual review, and there is a functional manager whom you work with on a daily basis. This structure is stupid, primarily used for shifting blame.
Upper management (VP and above) is very bloated; we need to cut some fat here.
Freshers are taken advantage of in terms of compensation. There's not much competition for core technology jobs in SD by other companies (this is gonna change soon).
Invest into more infrastructure and develop better internal tools.
Many managers lack team etiquette. Teach them how to invest in team success. Examples:
I had three interviews. They basically asked everything on my resume. The first one was with the manager, and we had a chat about my projects. The second was with a testing engineer. It was like a rapid-fire round where they kept throwing keywords
Applied online. Coding test preceded the phone interview. The interview proceeded for 1 hour. Simple, formal questions related to the resume. Technical issues occurred for 40 minutes of the hour. Asked about the main programming language and its pr
The interview process involved telephonic screening followed by an onsite component. Five engineers were interviewed one by one, with each interview lasting 45 minutes. All interviews consisted of technical questions. There was also a lunch interv
I had three interviews. They basically asked everything on my resume. The first one was with the manager, and we had a chat about my projects. The second was with a testing engineer. It was like a rapid-fire round where they kept throwing keywords
Applied online. Coding test preceded the phone interview. The interview proceeded for 1 hour. Simple, formal questions related to the resume. Technical issues occurred for 40 minutes of the hour. Asked about the main programming language and its pr
The interview process involved telephonic screening followed by an onsite component. Five engineers were interviewed one by one, with each interview lasting 45 minutes. All interviews consisted of technical questions. There was also a lunch interv