Honeywell Technology Interview Experience | On-Campus 2021
Discussion
Year - 2022Profile - Software EngineerProcessRound 1(Online Coding Round) - This was the preliminary round held on Hackerrank. There were two coding questions and one impl...
Full Details
Year - 2022 Profile - Software Engineer Process Round 1(Online Coding Round) - This was the preliminary round held on Hackerrank. There were two coding questions and one implementation-based question. One of the coding quests was to search for the element in a circular array and print the minimum number of comparisons you made. Another question was also a kind of easy-moderate. There is also an implementation-based question; the task is to request the JSON from an API request and print a particular field. I will rate this round as easy-moderate. Also, there was ample time to solve all these three questions. Round 2(Technical Round) - The interviewer asked various basic concepts related to the data types in C++, their range, types of storage class specifier, the difference between global and static keywords. The idea behind recursion. Questions were also from the real-time OS, like what condition do we need to implement the. Question-related to Round-robin scheduling wrt to real-time OS. Finally, he asked me to find out the midpoint of a linked list(using a single traversal of it). My advice is to keep your basics strong, and most important, if you have previously seen the question, don't get too excited, be calm, and tell the approach. Round 3(HR) - HR asked me for details of my projects. Details of the work done, the technology used. Then HR asked me, "What you know about the Honeywell?", "Why do you want to join us?". And other related questions. For preparing the HR round, at least get an overview of some of the products and the company's technology stack. Also, to answer frequently asked HR questions, please follow the template format available online. https://www.interviewbit.com/hr-interview-questions/ https://resources.workable.com/tutorial/hr-interview-questions
Verdict Selected My advice to all the students sitting for the placement season will be to keep yourself motivated, surround yourself with a good peer group. Do practice for the HR round. And last but not least, don't lose hope in midway. For me, it got 5+ companies interview to finally gets selected in Honeywell. So prepare well, sooner or later you will surely get your dream company. Also, check out my interview experience for PayU
About This Question
This is an interview discussion from a honeywell interview for a swe role during the oa round reported in 2025.
It covers the following topics: Linked List, Sql, Stack Queue, Recursion, Arrays, Stack .
Difficulty rating: Easy
Topics
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.