Honeywell Software Engineer interview typically runs 4 rounds: HR, technical, coding, and managerial. Timeline varies from next-day to a few months, and the process is notably fit- and values-focused.
$108K
Avg. Base Comp
$157K
Avg. Total Comp
4-5
Typical Rounds
3-5 months
Process Length
We’ve seen Honeywell lean less on flashy algorithm puzzles and more on whether candidates can explain the language they claim to know in a way that feels usable on the job. Multiple candidates reported questions on core Java and C++ fundamentals — things like memory management, collections, access specifiers, inheritance, and exception handling — but the follow-up was often about applying the concept, not reciting a definition. One candidate was even asked to fix a file full of errors, which tells us they value clean, readable code and the ability to debug under pressure.
A recurring theme is that Honeywell also cares a lot about whether you can connect technical knowledge to real-world systems. Our candidates were asked to give real-life examples for OOP, explain how they’d solve diamond inheritance, and even talk through a machine-learning approach to time series forecasting on CSV data. That mix suggests they’re looking for engineers who can bridge textbook knowledge and practical implementation, especially in environments where software touches industrial or aerospace systems.
The other signal we keep seeing is that fit is not an afterthought here. Several experiences mention conversational interviews centered on background, personality, and values, with one panel explicitly asking for examples of handling difficult coworkers and living Honeywell’s values. In other words, clear technical depth matters, but so does being easy to work with and grounded in your own experience. Candidates who did well sounded specific, calm, and concrete rather than overly polished or theoretical.
Synthetized from 4 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Honeywell process.
Really straightforward. There was a phone call at first asking if you have a certain skill set. It was very basic. After, there is a behavioral/technical interview regarding your past experiences. No live coding exercise was required.
Questions asked: Just standard behavioral questions and a lot about your resume. For example, describe this project? what libraries did you use?, what is your greatest failure/regret?
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 Honeywell
In which case would you use a bagging algorithm versus a boosting algorithm
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Loan Model | |
| String Palindromes | |
| Testing Constraints | |
| Kalman Filter in GPS tracking | |
| Your Strengths and Weaknesses | |
| Bootstrapping Samples | |
| Prime to N | |
| The Brackets Problem | |
| Longest Increasing Subsequence | |
| Find Duplicate Numbers in a List | |
| Merge N Sorted Lists | |
| Worker Distribution Dilemma | |
| User Event Data Pipeline | |
| Fixed-Length Arrays: Deletion | |
| Seller Type Modeling | |
| Shortest Transformation | |
| Data Stream Median | |
| Hidden Substring Segment | |
| International e-Commerce Warehouse | |
| Safe Deployments | |
| Triplet Counting | |
| Deciding Between Solutions | |
| Text Editor With OOP | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us | |
| LRU Cache 1 | |
| Processing Large CSV | |
| Reverse List Starting at Index K |
Synthesized from candidate reports. Individual experiences may vary.
The process often starts with an HR or recruiter conversation to confirm background, interest, and basic fit. In some cases this can happen after an initial informal contact, such as meeting a hiring manager at a career fair or through Honeywell’s talent community portal.
Candidates are then asked technical questions focused on core language fundamentals and practical problem solving. Depending on the interviewer, this can range from JavaScript trivia like currying to Java or C++ basics such as OOP, memory management, exception handling, diamond inheritance, and simple DSA-style coding problems.
Some candidates are given a small app-building task or homework-style assignment. This stage emphasizes code quality and practical implementation, and may include debugging a file with errors rather than a traditional whiteboard algorithm.
A hiring manager round may be more behavioral and conversational, with a strong focus on personality, communication, and how you describe your background and projects. This stage can also include discussion of past experience and how it connects to the role.
The final round can be a panel with multiple interviewers from different teams. It is often resume-driven and values-focused, with questions about Honeywell’s values, teamwork, and examples of handling difficult coworkers or bridging academic knowledge to industry needs.