Many opportunities for career growth if you can handle the bureaucracy
Many opportunities for career growth if you can handle the bureaucracy
One of the best reasons to work at Intel is that there are many different opportunities within the company, and it is easy to explore different career paths. Just because you have a particular specialty does not mean you will be pigeonholed into that area. If you express an interest in a different field at Intel to your manager, your manager will help you get where you want to go.
In addition to many career options, Intel has sites around the world, providing opportunities to move cities and still work at the same company.
Flexibility will vary from group to group and manager to manager, but in general, flexibility is a huge plus. If you need to be absent during normal working hours or work from home, it is never a problem as long as the job gets done and quality is not impacted.
Intel is a meritocracy and is data-driven; if you bring tangible results to the table, you will be recognized (and vice versa).
Bureaucracy and resistance to change. Management knows this is a problem and has attempted to resolve it, but there is still a long way to go.
Health benefits are okay, but not as good as compared to other tech companies.
The work pace is fast here, and it can be quite stressful at times trying to meet unreasonable deadlines. Although management understands the need for 'work/life balance', you really need to be able to set your own limits and say 'no', or else the workload will never stop growing.
There are some problems in the company which need to have resolutions pushed from the top down. Unfortunately, senior management is out of touch with individual contributors and is unaware of many such problems. As an IC, I have found it to be very difficult to bring problems to the attention of senior management and impossible to hold them accountable for finding solutions.
Was this helpful?
Intel Interview Questions
Intel Interview Experiences
Validation Engineer
Four parts: 1. One about Verilog coding: reading and telling what the code is about, and fixing code. 2. One about computer architecture: the traditional pipeline processor. 3. One about algorithms: how would you speed up file I/O and processing?
Validation Engineer
My interview process for a validation engineer started with a 30-minute phone interview with the hiring manager. We discussed my background and current role. He also briefly went into what the posted job entailed and the type of expertise he was look
Validation Engineer
They asked personal questions, requested a translation of an article from English to Hebrew, and kept making the questions increasingly difficult each time. Two easy-level LeetCode questions and one medium-level question were presented.
Validation Engineer
Hillsboro, Oregon, United StatesMarch 1, 2015Four parts: 1. One about Verilog coding: reading and telling what the code is about, and fixing code. 2. One about computer architecture: the traditional pipeline processor. 3. One about algorithms: how would you speed up file I/O and processing?
Validation Engineer
Hillsboro, Oregon, United StatesAugust 8, 2013My interview process for a validation engineer started with a 30-minute phone interview with the hiring manager. We discussed my background and current role. He also briefly went into what the posted job entailed and the type of expertise he was look
Validation Engineer
IsraelMay 20, 2025They asked personal questions, requested a translation of an article from English to Hebrew, and kept making the questions increasingly difficult each time. Two easy-level LeetCode questions and one medium-level question were presented.
