Real, anonymous reports from people who interviewed for Software Engineer at Philips, newest first and distilled into what to expect across the loop.
I got through an intro step and then it quickly turned into a skills-focused interview. The main thing I remember was being asked to rate my own abilities for data structures, followed by a series of programming questions—arrays, and then prompts that drifted into classic string/number checks like reversing strings and checking for palindromes. There were also questions about what I was interested in and discussions tied back to projects I’d done.
I went through a format that felt like a progression from coding to discussion. First came an online assessment round where dynamic programming was a big theme, and then I moved into a technical interview centered on my projects. Along the way, I also got asked about Java OOP concepts—enough to connect my background to how I’d build software rather than just recall buzzwords.
The interview process typically consists of multiple rounds, often starting with a phone screen, followed by technical interviews and an HR round. Candidates noted variations in the number of rounds, with some experiencing three to five distinct interviews, emphasizing both technical and behavioral aspects.
Candidates faced a range of technical questions primarily centered on data structures, algorithms, and programming fundamentals, with specific emphasis on languages like Java and C#. Many reported coding challenges that included array manipulation, string processing, and object-oriented programming concepts.
Behavioral interviews were common, often focusing on situational responses and alignment with company values. Candidates were asked to explain their past experiences and how they would handle various workplace scenarios, indicating a strong emphasis on cultural fit.
The overall tone of interviews varied, with many candidates describing a friendly and professional atmosphere. However, some reported logistical issues that affected the flow of interviews, leading to a rushed or disorganized experience.
Candidates encountered various assessment formats, including online coding tests and video interviews. The expectations were generally clear, focusing on both technical skills and the ability to articulate problem-solving processes, though some found the pace challenging.
Many candidates did not receive offers, often citing a lack of follow-up or clarity on the decision-making process. While the interviews were generally perceived as fair, the communication about outcomes left some feeling uncertain about their performance.