Still pockets of technical excellence and brilliance.
Still has a lot of money-making products.
Teams are working on every stack, from virtual reality and machine learning to physics and manufacturing.
A mini industry in itself.
Benefits are pretty good.
Current bad management will run it to the ground. Bad or no strategy is killing the company fast.
Every group has its own hiring policy, so many bad engineers tend to get hired due to sloppy interviews (bad hires hire other bad hires).
Due to good benefits, bad people don't leave, while good people get frustrated and leave.
Messed up diversity hiring, messed up layoffs, messed up closing of sites, projects, and messed up reorgs, etc.
The reason Intel is not competitive in mobile and other products is due to bad management strategies.
Products get delayed due to frequent reorgs that take 6 months to settle.
Delayed products are not competitive and so they get cancelled. Then management again does roadmap changes and reorgs, which ironically delays the next generation of products by 6 months to a year.
Have a stable management structure so that teams get 3-5 years of stability to gradually meet and beat the competition.
Stop expecting to compete against well-entrenched players by entering the markets and expecting to beat them in 2 years.
Have a real strategy (not some fancy virtuous cycle) instead of charging customers more just because you have a monopoly.
That differential will disappear soon, and then the company's profit will collapse.
More of a conversation than a technical interview. They asked simple questions to see if you had basic knowledge. The manager was not very engaged or knowledgeable. Very easy process, but very long. No sense of urgency.
Phone screen, followed by five rounds of interview. 1 behavior, 1 coding, and 3 architecture rounds. Questions covered basic hardware architecture, debug flows, and workload profiling. Most of the questions were about memory latency optimization te
A 3-hour loop interview, with each interviewer conducting their portion for 30 minutes. You remain on the call for the entire 3 hours. Every 30 minutes, the current interviewer drops out, and a new one joins the call. This results in a total of 6 int
More of a conversation than a technical interview. They asked simple questions to see if you had basic knowledge. The manager was not very engaged or knowledgeable. Very easy process, but very long. No sense of urgency.
Phone screen, followed by five rounds of interview. 1 behavior, 1 coding, and 3 architecture rounds. Questions covered basic hardware architecture, debug flows, and workload profiling. Most of the questions were about memory latency optimization te
A 3-hour loop interview, with each interviewer conducting their portion for 30 minutes. You remain on the call for the entire 3 hours. Every 30 minutes, the current interviewer drops out, and a new one joins the call. This results in a total of 6 int