Honeywell software engineer candidates report a recruiter call or coding screen, technical questions on language fundamentals, resume project discussions, and behavioral or managerial conversations. The mix varies by team.
$103K
Avg. Base Comp
$127K
Avg. Total Comp
4 rounds
Typical Rounds
Not reported
Process Length
Candidates describe the Honeywell software engineer interview as fundamentals-first and conversation-heavy rather than a pure algorithm grind. The technical content depends on the team. One candidate reported a Java-centered process covering OOP, memory management, exceptions, collections and concurrency. That process also included a small app, a homework-style task and a code file full of errors to fix. Another described C++ questions on diamond inheritance and access specifiers, along with a simple array problem: finding the second largest number. A third was asked to explain, at a high level, how they would approach time series forecasting on a CSV dataset.
Resume discussion comes up repeatedly. Candidates describe being asked to explain their projects and name the libraries or technologies they used. Behavioral questions covered teamwork, difficult coworkers, failure or regret, and Honeywell's values. One candidate said the first conversation, after meeting a manager at a career fair, was entirely behavioral.
Outcomes are mixed and the shape of the process varies. Two candidates describe four rounds, one of them a coding round, two technical rounds and a managerial round. Another describes a short phone call followed by a single behavioral and technical conversation with no live coding. One candidate reported waiting a few months for a response after the assessment. Practice explaining core language concepts with examples, prepare a clear walkthrough of your projects, and have specific stories ready for teamwork and conflict.
Synthesized from 28 candidate 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.
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
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Merge Sorted Lists | |
| Bagging vs Boosting | |
| Cyclic Detection | |
| Term Frequency | |
| Hurdles In Data Projects | |
| Loan Model | |
| Solo ML Deployment | |
| String Palindromes | |
| Testing Constraints | |
| Kalman Filter in GPS tracking | |
| Area Under the ROC Curve | |
| Your Strengths and Weaknesses | |
| Bootstrapping Samples | |
| Prime to N | |
| Size of Joins | |
| The Brackets Problem | |
| Real-Time Transaction Streaming | |
| Level Of Rain Water In 2D Terrain | |
| Triplet Counting | |
| Longest Increasing Subsequence | |
| Find Duplicate Numbers in a List | |
| Multi-Reaction | |
| RAG Strict Source Control | |
| Merge N Sorted Lists | |
| Worker Distribution Dilemma | |
| User Event Data Pipeline | |
| Offer Matching API Design | |
| Seller Type Modeling | |
| Fixed-Length Arrays: Deletion |
Synthesized from candidate reports. Individual experiences may vary.
Candidates describe different first steps. One reported a basic phone call about their skill set, and another an HR chat followed by a small app and a homework-style task. A third described a coding round before the technical rounds. One candidate met a manager at a career fair and interviewed the next day.
Technical questions depend on the team and language. Reports include Java topics such as == versus equals, memory management and collections, plus C++ diamond inheritance and access specifiers. One candidate had a simple array problem: finding the second largest number. Another said JavaScript currying can come up, but described that secondhand. Expect to explain concepts with examples.
Several candidates describe a conversation built around their resume. Interviewers asked them to describe projects and name the libraries or technologies they used. One candidate described a behavioral and technical interview about past experience with no live coding exercise.
Behavioral questions covered teamwork, difficult coworkers, and greatest failure or regret. One candidate described a five-person audio panel that asked for examples of Honeywell's values, and another listed a managerial round after two technical rounds. Prepare specific stories rather than general statements.
