Software Development Engineer Interview Experience - Portland, Oregon
Process
A phone screening preceded the onsite interview. The onsite interview process lasted a full day. The interview schedule and slots were sent to me in advance. It included 1:1 and group panel interviews. I was asked to write C/C++ programs on a whiteboard, and answer linked list coding questions, as well as computer architecture and OS-related questions. Overall, it was a systematic process with an average difficulty level.
Questions
C/C++ programming
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Intel Software Development Engineer role in Portland, Oregon.
Success Rate
Intel's interview process for their Software Development Engineer roles in Portland, Oregon is incredibly easy as the vast majority of engineers get an offer after going through it.
Experience Rating
Candidates reported having very good feelings for Intel's Software Development Engineer interview process in Portland, Oregon.
Intel Work Experiences
- 5.0Good company, good paySoftware Development Engineer • Current EmployeePortland, Oregon, United StatesOctober 22, 2022Pros: Opportunities for growth. Good pay.Cons: Recent layoff rumors. Slow to make progress due to excessive bureaucracy.
- 4.0Great company to work forSoftware Development Engineer • Current EmployeePortland, Oregon, United StatesJune 19, 2018Pros: Great employee benefits. Projects are available in all fields, from hardware to software and from research to product development. You get to work with cutting-edge technology. Transferring inside the company is easy.Cons: Salary range not as high as Google or eBay.
- 4.0Freedom But Hazy ResponsibilitiesSoftware Development Engineer • Current EmployeeSanta Clara, California, United StatesDecember 20, 2019Pros: - Fast-paced development. - Freedom over how you develop and what to develop. - Flexible time off and work from home. - Small, close-circle team working over many different technologies. *Reviews are specific to the team I was working on. Other teams may vary.Cons: - Unspecified agenda and responsibilities make everything hazy. - Development is sometimes not completed. Rather than focusing on solid development, it's mostly focused on "just works" type completion. - Wrong scrumming and so-called agile processes, demos, and weekend/night work make it difficult.
Intel Interview Questions
