Honeywell Connected Enterprise Interview Experience for Internship (On-Campus)
Question Details
I am a final-year undergraduate student majoring in Electrical Engineering. My academic journey has been focused on the Bachelor's Program in this department. My primary a...
Full Details
I am a final-year undergraduate student majoring in Electrical Engineering. My academic journey has been focused on the Bachelor's Program in this department. My primary areas of interest lie in programming and embedded systems. I initiated my coding journey in the 11th standard and delved into competitive programming during my first year of college. Overview The on-campus selection process for the Honeywell internship comprised three rounds, all of which I successfully cleared. The initial round involved coding with three moderate-level questions. The second round was a technical assessment covering programming and mathematical questions, coupled with a review of my CV. The concluding round was the HR interview, focusing on typical inquiries about my plans and aspirations. Role The company had come for an SDE-II role which was for 2 months and the internship was in Bengaluru. They expected a good grasp of DSA and mild developing experience. Process Round 1 (Online Coding Round): This was the preliminary round held on Hackerrank. There were three coding questions which were all DSA-based : The first question was on the easy level which could be solved by anyone who has started DSA. The second question was of moderate level and was based on Dynamic Programming. The third question was a moderate-level tree question which could be done if you have solved enough tree questions on leetcode and other coding platforms. Round 2 (Technical Round): The interviewer asked me two questions one of which was a DSA question which was a standard problem (knapsack, DP), and the other was based on time complexity. He started with my CV after the DSA questions, where he particularly focused on one project where I had made a simulation using ASCII characters in a C++ terminal. He asked how I implemented it and what was the maths involved. He then proceeded by asking me my favourite algorithm in DSA and why, and I responded by saying "Dijkstra's algorithm" explaining how it uses the greedy approach to find the shortest path along with priority queue to make it efficient in terms of time complexity. Round 3 (HR): The HR round went very smoothly with easy standard HR questions which you can practice from coding platforms. Be prepared with the standard HR questions which will come in handy and must not be overlooked. https://www.interviewbit.com/hr-interview-questions/ https://resources.workable.com/tutorial/hr-interview-questions During the HR interview, I responded to questions such as "What do you know about Honeywell?" and "Why do you want to join the company?" along with other relevant questions. To prepare yourself for the HR round, ensure you have a basic understanding of the company's products and technology stack. Familiarize yourself with the range of products the company offers and gain insights into the technologies they use.
Verdict Selected Familiarize yourself with your CV, as it serves as the primary determinant in the initial selection phase. Your CV is a reflection of your professional identity, so invest time in having it reviewed by different individuals. If time allows, consider acquiring additional, quick-to-learn skills that could be viewed as valuable by potential employers. Strategically choose projects that align with specific domains, showcasing a deliberate progression in your career direction rather than a random assortment of experiences.
About This Question
This is a reported interview question from a honeywell interview for a swe role (intern level) during the oa round reported in 2025.
It covers the following topics: Heap, Trees, Dynamic Programming, Sql, Graph, Stack Queue, Greedy, Graphs, Queue, Stack .
Difficulty rating: Easy
More Honeywell Interview Questions
About Honeywell Interview Reports
This question was reported by a candidate who interviewed at Honeywell. 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 Honeywell are the higher-signal extractions to take from this report.
For broader preparation context, the Honeywell 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 Honeywell reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Honeywell 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 Honeywell 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.