Honeywell Interview Experience for Internship | On-campus 2020 drive
Interview Experience
Round 1:This round consisted MCQs and two coding questions. MCQs were asked from CS fundamentals - I got questions regarding programming concepts like - fprinf(), fscanf()...
Full Details
Round 1 This round consisted MCQs and two coding questions. MCQs were asked from CS fundamentals - I got questions regarding programming concepts like - fprinf(), fscanf() and their properties and so on. The coding questions were very basic but one needs to be quick to solve both the questions in given time frame.
coding question 1 - Print all the prime numbers from 0 to 1000. Question 2 was regarding a standard arithmetic progression problem one which we see in CBSE class X math books. It was easy unless you know the concepts ;) One needs to clear both the coding questions and solve maximum MCQs correct to qualify for further rounds.
Round 2 This was regarding technical knowledge mainly focused on projects in the resume. I had shown my projects live (hosted). One can even provide link to the GitHub repo of the project to the interviewer. He then asked few basic questions from computer networks. Then he gave me to code a problem - Find the longest palindrome substring in a given string. { https://www.geeksforgeeks.org/dsa/longest-palindromic-substring/ }. He was satisfied with my answer. At last he asked me "What happens if you hit a link in your browser ? ". I explained him the process chain that happens along with DNS lookup ;)
Round 3 I got a mail saying that I had qualified for the HR round on the same day. Just 2 hours after my technical round got over. During the start of my HR interview, the interviewer made me feel comfortable. She then began my interview after a casual talk ;). She asked me - "Tell me about yourself ." "What is the probelm that you have solved in a very unusual way ?" "How do you manage to resolve conflict of ideas within your team ?" "What have you learnt during this COVID lockdown ?" For all the questions I answered honestly, as luckily there were instances in my life for the above questions. Finally, she asked if I have any questions for her - I asked few questions, for which she answered patiently. I thanked her and cut my call. It was indeed a great experience from Honeywell team. Finally I got selected for the internship. Hope this helps and all the best ;)
About This Question
This is a candidate experience report from a honeywell interview for a swe role (intern level) during the recruiter round reported in 2025.
It covers the following topics: Strings, Math .
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.