
One candidate who interviewed for Philips Engineering Manager roles reports a basic introductory interview, slow HR replies of 3 to 6 days and rejections with conflicting leadership feedback. Here is how to prepare.
$140K
Avg. Base Comp
$165K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The one candidate report we have for the Philips Engineering Manager interview describes a process that was light on technical depth and heavy on logistics. The candidate applied to two different positions about two months apart and interviewed for both. They remember the interview as very basic, built around a "tell me about yourself" opener, with nothing especially deep or challenging.
The harder part was the process around the conversation. This candidate says HR replies often took 3 to 6 days and that interview times were not flexible. They were rejected from both roles. For one they were told they lacked leadership skills, and for the other they were told they had too much leadership experience for an engineering role. Role-level fit is therefore the thing to settle before you interview.
If you apply, prepare a concise, honest account of your background and the scope of team you have led. Tie it to the specific posting rather than to engineering management in general. Be ready to say where you sit between hands-on engineering and people leadership, and why that matches the role. Allow for slow scheduling and keep your availability open.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Philips process.
I would not recommend applying for internal or direct positions at Philips right now if you do not want to waste your time. Based on my experience, I was not convinced they were actively hiring for these roles, and the whole process felt more frustrating than substantive.
I applied for two different positions about two months apart, and in both cases I went through interviews only to be rejected. The interview itself was very basic, which was part of why the outcome felt so confusing. The main question I remember being asked was a simple “tell me about yourself” style opener, and there was nothing especially deep or challenging beyond that. What stood out more than the questions was the process around them: HR communication was slow, with responses often taking 3 to 6 days, and scheduling was difficult because they were not able to offer flexible interview times. For one role I was told I did not have enough leadership skills for a leadership position, and for the other I was told I had too much leadership experience for an engineering role. That contradiction made it hard to understand what they were actually looking for. I also noticed the same roles were open for contractors, which made me wonder whether the direct hire postings were serious.
Overall, I came away feeling that the process was poorly organized and not worth the time unless you are very patient and comfortable with slow back-and-forth.
Prep tip from this candidate
Be ready for a very basic introductory conversation, but don’t expect a deep technical screen. The bigger risk here seems to be unclear role fit and slow scheduling, so make sure you can clearly frame your leadership level and why it matches the specific posting.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Philips
Describing a data project and its challenges
| Question | |
|---|---|
| Text Editor With OOP | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Prime to N | |
| Find the Missing Number | |
| Equivalent Index | |
| Group Success | |
| Recurring Character | |
| Google Maps Improvement | |
| Customer Analysis | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Instagram TV Success | |
| The Brackets Problem | |
| LRU Cache 1 | |
| Valid Anagram | |
| Promoting Instagram | |
| Groups of Anagrams | |
| String Mapping | |
| Sort Strings | |
| Targeted sum | |
| Digit Accumulator | |
| Inactive Users | |
| Cyclic Detection | |
| Shortest Path Algorithms | |
| First Names Only | |
| Stop Words Filter | |
| Greatest Common Denominator | |
| Nearest Common Ancestor |
Synthesized from candidate reports. Individual experiences may vary.
The candidate applied to two separate Philips engineering roles about two months apart. They suspected the same roles were also open to contractors. Applicants may want to read each posting closely, because the reported feedback centered on how their leadership level matched the role.
This candidate reports that HR replies often took 3 to 6 days and that the company could not offer flexible interview times. Candidates may want to offer several availability windows early and follow up politely, since scheduling was described as the most frustrating part.
The candidate describes the interview as very basic. The one question they remember was a "tell me about yourself" style opener, with nothing especially deep or challenging. Typically this suggests preparing a clear, role-specific career narrative, though other candidates may be asked more.
The candidate was rejected for both roles. For one they were told they lacked leadership skills for a leadership position, and for the other that they had too much leadership experience for an engineering role. Readers may want to frame their leadership level explicitly so a mismatch is less likely.