The good and bad of working for Intel
The good and bad of working for Intel
Very interesting work.
Opportunity to learn and contribute to leading-edge technologies.
Top pay and benefits. Compensation is merit-based.
Stock options too.
Super competitive work culture. Long, hard days. Intense pressure to produce results. Little appreciation unless you're one of the fast-track, superstar performers. Steady performers who meet their deliverables without fanfare will not succeed.
Was this helpful?
Intel Interview Questions
Intel Interview Experiences
Software Development Engineer
Take-home assignment of a Web API CRUD application. Explain on TypeScript code, SQL syntax questions, some architecture and design questions. Overall, a great and transparent process with a few rounds before being selected.
Software Development Engineer
Applied online. Reached out by a recruiter within two weeks. It seems all applicants can receive at least one round of technical interview. The first round of interview had two LeetCode Easy questions. There were no behavioral questions, and no ques
Software Development Engineer
The first hour was an overview of the team and an "introduce yourself" question, followed by some technical questions. There were multiple programming quizzes focusing on algorithms and efficiency. There were three interviewers, one-on-one.
Software Development Engineer
Bayan Lepas, Penang, MalaysiaNovember 25, 2025Take-home assignment of a Web API CRUD application. Explain on TypeScript code, SQL syntax questions, some architecture and design questions. Overall, a great and transparent process with a few rounds before being selected.
Software Development Engineer
CanadaNovember 9, 2022Applied online. Reached out by a recruiter within two weeks. It seems all applicants can receive at least one round of technical interview. The first round of interview had two LeetCode Easy questions. There were no behavioral questions, and no ques
Software Development Engineer
United StatesApril 13, 2022The first hour was an overview of the team and an "introduce yourself" question, followed by some technical questions. There were multiple programming quizzes focusing on algorithms and efficiency. There were three interviewers, one-on-one.
