Something changed in 2014
Something changed in 2014
Still attract enough smart people who don't know what's going on inside the company.
After several years of PC revenue decline, the company has drifted into a toxic mode. Layoffs unfairly target overrepresented groups of White or Asian males who are over 40. But if you are in the clique, you should be able to get by by making a few slides, checking some emails, and attending several meetings every day to claim you've driven a program, managed a project, led a team, influenced a decision, or refined a process. There are lots of people with fancy titles that don't know much beneath the colorful boxes in PowerPoint. In the meantime, managers are asked to fill the quota for Underrepresented Minorities in order to match college graduation demographic data. The CEO is mindlessly pursuing what's on the cover of magazines like IoT, drones, and wearables through acquisitions instead of making real engineering efforts.
Cannibalize your own products with cheaper alternatives. Don't slap people in their faces when they are told to leave after 20 years' hard work.
Was this helpful?
Intel Interview Questions
Intel Interview Experiences
Software Engineer
I had one-on-one or two-on-one interviews with 5-6 team members. 40% of the questions were behavioral, and 60% were technical, with some brain teasers and questions pertaining to my prior internship at Intel. Intel heavily favors recent college gra
Software Engineer
The interview process began with a phone interview with the hiring manager, who would be my direct supervisor. This was followed by a phone interview with a team member. Subsequently, I was flown out for a full day of interviews. Unlike interviews
Software Engineer
Very smooth. Interviewer was helpful. HR process was smooth. Questions were technically strong. Asked many questions on data structures, pointers, and linked lists. Covered modern C++, design patterns, UML, etc. I was half prepared but enjoyed
Software Engineer
Portland, Oregon, United StatesJuly 30, 2016I had one-on-one or two-on-one interviews with 5-6 team members. 40% of the questions were behavioral, and 60% were technical, with some brain teasers and questions pertaining to my prior internship at Intel. Intel heavily favors recent college gra
Software Engineer
Portland, Oregon, United StatesApril 1, 2011The interview process began with a phone interview with the hiring manager, who would be my direct supervisor. This was followed by a phone interview with a team member. Subsequently, I was flown out for a full day of interviews. Unlike interviews
Software Engineer
Portland, Oregon, United StatesFebruary 1, 2020Very smooth. Interviewer was helpful. HR process was smooth. Questions were technically strong. Asked many questions on data structures, pointers, and linked lists. Covered modern C++, design patterns, UML, etc. I was half prepared but enjoyed
