The top two reasons for working at Intel are the people and the opportunities. Intel still houses some of the industry's best engineers, and its open-door policy allows one to really grow. Secondly, Intel, with its size, offers many opportunities. It's not difficult to move from one group to another. The caveat is that you have to pick the right group.
The main downside to working for Intel is the amount of bureaucracy that is needed to get things done, and even worse, to get changes implemented.
It is such a challenge to inject new ideas that one is often resigned to accepting what management wants. At times, it's even easier and rewarded to just 'go along' with management.
Further, Intel's total compensation package is no longer on par with other companies in Silicon Valley. RSUs and stock options are a significant part of the compensation package, but if the stock is not performing to expectations, Intel must revise its compensation and reward system in order to retain its talent as well as reward employees for sticking with Intel.
At top universities and colleges around the US, Intel used to be known for two things: cutting-edge technology and a rock-stable company.
You applied to work for Intel to be part of the world's leading technology in semiconductors, whether it's in chip design, process integration, or manufacturing. You also joined for its stability; given its size and large engineering profile, you knew Intel wasn't going anywhere.
These days, things have changed. Intel is not viewed as the company that produces 'cool and innovative' products anymore, and its stability is equal to that of a typical mid-size company in Silicon Valley. With this negative view, many top recruits are not applying to Intel.
In order to continue and maintain its success, Intel needs to change its image to attract the nation's top talent. This change starts internally:
I had about three rounds of interviews. The first was behavioral, and the other two were technical. I did not have to do much active coding, but it was a lot of Java and OOP-specific questions, as that was what I had experience with. All of the inter
The interview included straightforward questions about Linux and JavaScript. It progressed to web development stacks, with inquiries about React.js. Questions also covered my resume and experience. Simple JavaScript questions and Linux command-lin
Submitted resume on Intel Jobs site. Received prescreening phone call from Engineering Manager. Phone interviews, one hour each: * Project Manager * Software Director One hour in-person interview with the Project Manager. In-person interview with S
I had about three rounds of interviews. The first was behavioral, and the other two were technical. I did not have to do much active coding, but it was a lot of Java and OOP-specific questions, as that was what I had experience with. All of the inter
The interview included straightforward questions about Linux and JavaScript. It progressed to web development stacks, with inquiries about React.js. Questions also covered my resume and experience. Simple JavaScript questions and Linux command-lin
Submitted resume on Intel Jobs site. Received prescreening phone call from Engineering Manager. Phone interviews, one hour each: * Project Manager * Software Director One hour in-person interview with the Project Manager. In-person interview with S