Philips Intern Interview Experience 2019
Question Details
Initially 15 students were shortlisted out of 83 students on the basis of online coding round. codes were very basic like GCD of an array.
Round 1 first round was tec...
Full Details
Initially 15 students were shortlisted out of 83 students on the basis of online coding round. codes were very basic like GCD of an array.
Round 1 first round was technical and HR combine. They ask me briefly about the project which i mentioned in my resume. interviewer ask me to write a query to select the list of student whose vouchers lie between 21 april 2017 to 21 may 2017. difference between singly linked list and doubly linked list tell me one formal and one informal risk you face in your life what are the problem you face as a project leader explain Software Development Life Cycle explain Layers of OSI model and HTTP difference between c++ and java difference between abstract class and interface
Round 2 It was an HR round. the question that were asked are Tell me about yourself why Philips where do you see yourself in 5 years
About This Question
This is a reported interview question from a philips interview for a swe role (intern level) during the recruiter round reported in 2019.
It covers the following topics: Arrays, Linked List, Sql, Networking, Math .
Difficulty rating: Easy
Topics
More Philips Interview Questions
About Philips Interview Reports
This question was reported by a candidate who interviewed at Philips. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Philips are the higher-signal extractions to take from this report.
For broader preparation context, the Philips interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Philips reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Philips Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Philips reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.