Intel is a great place to work and allows lateral movement within the company.
Risk-taking is very decently promoted and valued, allowing individuals to gain exposure and experience in multiple areas.
The company does a lot for the community; volunteer and fund-raiser works are well supported.
Flexible work hours, telecommuting, vacations, and leave of absence for personal reasons are all well supported.
Senior engineering staff is among the most talented bunch of folks in the industry.
Too large a company makes it bureaucratic. Promotions and performance appraisals get lost in the process. Being a large company, the decision-making process also slows down.
The bottom-up "bubble" of Intel employees, from lower to upper grade levels, should be encouraged.
Intel's HR contacted me for an initial phone screen. This initial screen was with two engineers who were on the team for which I would be interviewing. The questions were technical, but nothing too heavy. Shortly thereafter, I was contacted to come
It was a phone coding challenge—no IDE or development platform was available. It was an unscheduled interview where the interviewer called me out of the blue one day. I had to describe code to my interviewer because there was no online platform for
The interview process was very cut and dry. They presented you with many technical coding problems, one after another, and expected very fast responses. They did not allow the time to get relaxed or to ask general questions about their work environ
Intel's HR contacted me for an initial phone screen. This initial screen was with two engineers who were on the team for which I would be interviewing. The questions were technical, but nothing too heavy. Shortly thereafter, I was contacted to come
It was a phone coding challenge—no IDE or development platform was available. It was an unscheduled interview where the interviewer called me out of the blue one day. I had to describe code to my interviewer because there was no online platform for
The interview process was very cut and dry. They presented you with many technical coding problems, one after another, and expected very fast responses. They did not allow the time to get relaxed or to ask general questions about their work environ