Software Engineering Intern applicants have rated the interview process at Intel Corporation with 2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 75% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineering Intern roles take an average of 1 day to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at Intel Corporation overall takes an average of 27 days.
Common stages of the interview process at Intel Corporation as a Software Engineering Intern according to 2 Glassdoor interviews include:
Skills test: 50%
Group panel interview: 50%
Here are the most commonly searched roles for interview reports -
I interviewed at Intel Corporation (Haifa) in Feb 2025
Interview
2 old-fashioned whiteboard onsite interviews. Nothing too bad, standard LC questions. Interviewers were really nice and the process was quick, respectful and accommodating of my time given I had exams at the time.
My one complaint is that each interview was 2 hours long which is exhausting (for the interviewers as well), but they pass in the end.
Interview questions [1]
Question 1
graph algorithms, data structures, algorithms in general
I applied online. The process took 3 days. I interviewed at Intel Corporation (Pulau Pinang) in Oct 2023
Interview
Straightforward and Helpful. 3 managers interviewed the candidate, with questions relating to behavioral, and thought process reasoning. Lasted for an hour, most questions can be handled by anyone, as long you have coded before.
Interview questions [1]
Question 1
- Live Hands On Coding (printing using array) - Tech stack - Experience
I applied through university. The process took 1 day. I interviewed at Intel Corporation (Limerick, Limerick) in Oct 2020
Interview
Very nice casual interview with a number of people. Not many technical questions. I was expecting to receive some sort of exercise in the form of a programming challenge but did not.
Interview questions [1]
Question 1
Why do you think C is useful for low-level programming?