Good company, but not the best team
Good company, but not the best team
- Big company = fairly stable, benefits are decent, the usual stuff.
- Lots of opportunity to network internally.
- Interesting product(s) to work on.
- Pay was not great compared to other companies I was considering (I chose them due to interest in the product).
- For those interested in benefiting from an employee discount, good luck getting products in stock.
- Corporate culture seemed to favor the "it's not my domain, it's not my problem" mentality, and many felt happy putting up red tape as barriers to prevent people from asking things of them.
- Some team members on my specific team didn't show much investment in the product(s)' success and didn't make much effort to actually tackle issues and be proactive to improve the team's output. I do want to stress that this was my experience with my team specifically and does not reflect every individual on that team, or the company as a whole. There were great people I found as well.
- The real issue with the former is that, especially in newer departments/teams, the management isn't very "settled," and as a result, these sorts of issues just get ignored.
- People spend more time arguing about the format they're going to present the results of their engineering than arguing about the actual engineering issues they're facing.
-
Actually manage your teams. Don't just have a vague mandate, then hand everything off to a group of equals who have proven an inability to elect and follow a leader themselves. If there are no clear goals and management ensuring they are met, lethargy and disenchantment follow.
-
Take greater care when hiring to ensure employee skills and responsibilities match up.
-
High-level management/executives need to talk to both customers and engineers more often (as in, the engineers doing the work, not the management). Bad decisions and flip-flops could be avoided if this happened.
-
Management should take the burden of packaging engineering information and delivering it to upper management away from individual engineers. There should be no need for them to debate the format of PowerPoints every week for an hour+.
Was this helpful?
Intel Interview Questions
Intel Interview Experiences
Software Engineer (Internship)
Totally technical. Almost no behavioral questions (which I liked). LeetCode Easy-Medium, so not very hard. Three interviewers, and two were very nice. Each of the interviewers took 30 minutes.
Software Engineer Intern
3 x 30-minute technical interviews. They seem to keep asking questions until the 30 minutes end. I was able to answer around 3-4 questions per round. The interviewers help you if you get stuck, so it's good.
FPGA Intern
The interviews were conducted online for both. They consisted of one LeetCode-style software interview and one Verilog hardware interview. There were no conceptual or behavioral questions. The process involved only one round, not a multi-round inter
Software Engineer (Internship)
Toronto, Ontario, CanadaSeptember 1, 2020Totally technical. Almost no behavioral questions (which I liked). LeetCode Easy-Medium, so not very hard. Three interviewers, and two were very nice. Each of the interviewers took 30 minutes.
Software Engineer Intern
Toronto, Ontario, CanadaOctober 1, 20223 x 30-minute technical interviews. They seem to keep asking questions until the 30 minutes end. I was able to answer around 3-4 questions per round. The interviewers help you if you get stuck, so it's good.
FPGA Intern
Toronto, Ontario, CanadaOctober 3, 2025The interviews were conducted online for both. They consisted of one LeetCode-style software interview and one Verilog hardware interview. There were no conceptual or behavioral questions. The process involved only one round, not a multi-round inter
