The benefits at Qualcomm are very good -- free medical, dental, and vision.
There's a decent 401K match.
The ESPP is good too (the stock is doing very well).
They offer a free gym membership.
There's a good work/life balance here.
Compensation is also pretty good (but I can't comment on the bonus plan).
This was one of the most boring jobs I ever had. It turned out to be more of a sustaining/maintenance role. Bug fixing occupied about 80% of my time. There's very little feature development going on in San Jose. Most of the significant work is happening in India.
Put more effort into assigning work and projects to San Jose-based engineers so that they will feel as if they have a stake in the success of QCA.
The phone interview was quite detailed, with numerous questions about C and networking. The level of detail required me to draw diagrams on paper to fully comprehend the questions. The in-person interviews were thorough and included: * C coding *
I applied through their website and received an email from the recruiter a couple of days later. She arranged a phone interview with the group leader and two engineers simultaneously. They asked a bit about my experience, a few C++ questions, and som
Interviews were conducted with HR and five technology team leads. Questions covered experience and skills, including algorithm development. Discussions also addressed best practices, development infrastructure, and tool chains. Questions were aske
The phone interview was quite detailed, with numerous questions about C and networking. The level of detail required me to draw diagrams on paper to fully comprehend the questions. The in-person interviews were thorough and included: * C coding *
I applied through their website and received an email from the recruiter a couple of days later. She arranged a phone interview with the group leader and two engineers simultaneously. They asked a bit about my experience, a few C++ questions, and som
Interviews were conducted with HR and five technology team leads. Questions covered experience and skills, including algorithm development. Discussions also addressed best practices, development infrastructure, and tool chains. Questions were aske