Honeywell Software Engineer interviews reported by candidates combine resume and behavioral discussions with technical questioning that can cover coding, language fundamentals, system trade-offs, and project depth.
$121K
Avg. Base Comp
$144K
Avg. Total Comp
4 rounds
Typical Rounds
3-5 months
Process Length
Honeywell Software Engineer candidates report several interview paths rather than one uniform script, but the recurring theme is clear: be ready to explain work you have actually done. Reports describe resume-led conversations that probe a project’s architecture, the libraries or technologies used, your individual ownership, and the trade-offs behind technical choices. One recent candidate was asked to unpack an SMS-notification microservice, including scalability, idempotency, monitoring, database parallelization, batch processing, indexing, and optimization.
Technical content varies by team and language. Candidates have encountered coding exercises, simple array problems, debugging broken code, and questions on Java, C++, or JavaScript fundamentals. Clear reasoning about a real project and its design decisions is the most consistent preparation theme. Java-focused reports mention OOP, memory management, exceptions, collections, and concurrency; other reports include C++ inheritance or direct JavaScript questions. Prepare the fundamentals relevant to the role you are pursuing, rather than assuming one language is universal.
Behavioral and hiring-manager conversations also recur. Candidates describe discussions of teamwork, difficult coworkers, values, career goals, failures, and team fit. Have concise examples that show how you work with others and can connect your experience to the position. The evidence is limited and team-dependent, so use these reports to prepare broadly rather than treat them as a fixed sequence.
Synthesized from 9 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.
Technical round: asked about projects, with follow-ups. The candidate reported that two rounds remained. There was no DSA in this first round; the main emphasis was work completed at the previous company, technologies used, and their trade-offs.
Questions asked: A specific question about an SMS-notification microservice and a full explanation of its architecture. Follow-ups covered scalability, idempotency, and monitoring. The interviewer also asked about database parallelization and batch processing, with follow-ups on indexing trade-offs and optimization.
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 | |
| The Brackets Problem | |
| Size of Joins | |
| Level Of Rain Water In 2D Terrain | |
| Triplet Counting | |
| Longest Increasing Subsequence | |
| Find Duplicate Numbers in a List | |
| Merge N Sorted Lists | |
| Worker Distribution Dilemma | |
| User Event Data Pipeline | |
| Offer Matching API Design | |
| Seller Type Modeling | |
| Fixed-Length Arrays: Deletion | |
| Gas Station Counting | |
| The Pirate’s Hunt | |
| Data Stream Median |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial phone, HR, or hiring-manager conversation in some paths. These discussions may cover required skills, software background, projects, and basic behavioral fit; one candidate reported a brief resume-and-project phone screen.
Some candidates report an online assessment, a small app or homework task, debugging code, or simple DSA-style questions. Reported examples include finding the second-largest array value and writing a linked-list cycle check; other candidates reported no live coding.
Technical interviews may explore the language used by the team, OOP, programming concepts, or project implementation. Candidates report Java, C++, and JavaScript questions, plus follow-ups on architecture, scalability, idempotency, monitoring, database work, indexing, and optimization.
Candidates report resume-driven behavioral interviews and, in one case, a multi-person final panel. Prepare examples involving teamwork, difficult situations, failures, values, career goals, and the decisions you personally made on past projects.
