Honeywell's loop splits cleanly by geography and function. In India, where the bulk of published accounts come from, it is a classic campus funnel: a timed online assessment (HackerRank or HackerEarth, sometimes a separate aptitude/MCQ paper), one or two technical interviews that lean on core CS fundamentals and heavy resume/project grilling, and a short HR or cultural-fit round; some cycles substitute a team hackathon or a group discussion for a second technical round. In the US, corporate and product roles run a lighter, behaviour-first sequence: recruiter or on-campus screen, then a hiring-manager conversation or a multi-person panel, with only one or two role-specific technical questions. Interviewers repeatedly steer toward what candidates actually built rather than abstract puzzles, and the non-software campus streams (instrumentation, process/chemical) get discipline-specific written tests instead of DSA.
These 19 writeups cover software engineering, product management, finance and other roles, India campus heavy, some US corporate. 14 of them were posted under a pseudonym (Reddit, GeeksforGeeks or forum handles), so we could not verify the authors’ identities.
Typical rounds
2.81-5 range
Outcomes shared
10/4offer / not
Most common round
Online assessment
Sources span
2017 - 2026
Most frequently reported · Behavioral(17), Data structures & algorithms(15), Past projects(14), Domain knowledge(10), Arrays & strings(8)
Honeywell International’s official process
Honeywell's own careers site framed hiring in three phases (Get to Know Us, Talk With Us, Join Us) laid out as seven steps: research the company, find a role, submit an application, speak with a Honeywell recruiter, speak with the hiring manager, take part in a panel interview, then get hired. The panel stage is called out explicitly as a standard part of the process. The current live URL 404s, so this is read from the Internet Archive capture; the FAQ block on that page was still unfilled placeholder text. Honeywell's careers blog separately publishes recruiter-written interview tips (research the businesses, prepare questions, send a thank-you note) but no round-by-round breakdown.
A single scheduled half-hour conversation with two experienced Honeywell engineers. Most of it was spent unpacking the candidate's full-stack web project and their prior internship stack, with extra attention on their ML/AI work, plus a short behavioural block on strengths, weaknesses and teamwork.
Covered · Past projects, Resume deep-dive, Behavioral, API design
A timed online test mixing aptitude questions with MCQs on OS, DBMS and OOP, plus two easy-to-medium coding problems drawn mostly from arrays and strings. Roughly 150 students sat it and about 40 advanced.
An hour of pure problem solving covering arrays, strings, linked-list basics and recursion, with the candidate asked to code a linked-list reversal both iteratively and recursively and then reason about time and space complexity. Around 18 of 40 went through.
Covered · Arrays & strings, Data structures & algorithms, Trees
3
Technical interview (core CS + projects)Technical
A deeper round on process versus thread, scheduling, normalisation, indexing and transactions, then an application-flavoured project discussion about handling concurrent user requests and improving performance. Memory-management basics came up because of Honeywell's systems-level work.
Covered · Operating systems, DBMS, OOP, Past projects, Scalability
4
HR interviewBehavioral
A short closing conversation on motivation for Honeywell, career goals, teamwork and adaptability, aimed mainly at communication and general fit.
One hour covering thirty OOP multiple-choice questions the candidate found genuinely tricky, alongside two straightforward number-crunching coding problems where the catch was picking a wide enough integer type.
Covered · OOP, Data structures & algorithms
2
Technical interviewTechnical
An online interview with two panellists who focused squarely on DSA rather than advanced engineering, working through two string-reversal variants and a binary-tree mirroring problem, with a dry run expected for each.
Covered · Arrays & strings, Trees, Data structures & algorithms
Multiple-choice questions in a programming language the candidate nominated in advance, weighted toward language basics, syntax and file handling.
Covered · Data structures & algorithms, OOP
2
Technical interviewTechnical
An in-person round built around pointers and memory: why pointers exist, how memory is allocated, allocation types, swapping with and without pointers, and scope rules, followed by classic logic puzzles.
Covered · Data structures & algorithms, Puzzles, Operating systems
3
HR interviewBehavioral
A relaxed closing conversation with standard introduction and motivation questions, including whether the candidate would relocate later in their career.
A ninety-minute HackerEarth test with three medium-to-hard problems spanning segment trees, graphs and dynamic programming. About 200 candidates were shortlisted a week later.
Covered · Dynamic programming, Graphs, Data structures & algorithms
2
Technical + HR interviewHiring manager
A twenty-minute conversation that turned out to be almost entirely non-technical: projects, certifications, why the candidate chose AI/ML, a definition of AI, and willingness to be placed into any department.
Covered · Past projects, Behavioral, Domain knowledge
A short twenty-to-twenty-five minute multiple-choice paper in a language of the candidate's choice from C, C++ or Java, where speed was the main constraint.
Covered · Aptitude, OOP
2
Online coding assessmentOnline assessment
Thirty minutes for two very basic programming exercises involving input handling and a simple summation loop.
Covered · Arrays & strings, Data structures & algorithms
3
Technical interviewTechnical
A wide-ranging round starting with language choices and web fundamentals, moving through OOP concepts with examples, a live coding exercise on conditionals and inheritance, and a detailed walk through the candidate's data-analytics internship project.
Covered · OOP, Past projects, Data structures & algorithms, Testing
4
HR interviewBehavioral
Ten minutes on background, motivation for Honeywell, and how this interview compared with other companies the candidate had faced.
A HackerRank screen with three DSA problems escalating from beginner level to a moderate dynamic-programming question and a moderate tree question.
Covered · Data structures & algorithms, Dynamic programming, Trees
2
Technical interviewTechnical
Two problems (a knapsack-style DP question and a complexity question), then a CV walkthrough that zeroed in on a C++ terminal simulation project and the maths behind it, closing with a question on the candidate's favourite algorithm and why.
Covered · Dynamic programming, Data structures & algorithms, Past projects
3
HR interviewBehavioral
Standard HR ground covering what the candidate knew about Honeywell's products and technology stack and why they wanted to join.
Forty-five multiple-choice questions spanning OOP, data structures, complexity analysis, databases and aptitude. A handful of candidates, including this one, were pushed straight to interview on resume strength.
Covered · OOP, Data structures & algorithms, DBMS, Aptitude
2
Technical interviewTechnical
A long seventy-five-minute session: implement big-number factorial with arrays, trace an unfamiliar snippet and explain what it computed, find the kth largest element in an unsorted array with more than one approach, then rapid-fire OOP theory before a discussion of prior internships.
Generic HR ground on background, strengths, weaknesses and the biggest challenge the candidate had overcome. Most other candidates had two technical rounds before this; this one had only one.
A general quantitative and reasoning paper the candidate rated as straightforward for any engineering or science graduate who had practised.
Covered · Aptitude
2
Technical testOnline assessment
A branch-specific paper that the candidate found considerably harder, drawing on heat and mass transfer, process design and process control rather than programming.
Covered · Domain knowledge
3
Group discussionGroup exercise
A general-interest group discussion where the candidate's advice was to stay on topic and prioritise quality of contribution over airtime, since aggressive participants hurt the group.
Covered · Behavioral
4
Technical interviewTechnical
A brisk twenty-minute conversation on programming fundamentals such as data structures and arrays; the candidate got some answers wrong and acknowledged it at the end.
Covered · Data structures & algorithms, Past projects
5
HR interviewBehavioral
Generic HR questions plus a stress-test element: a situational personality question and a lateral one about describing a colour to a blind person, alongside a core-engineering question on distillation column design.
A two-part paper: forty to fifty one-mark technical multiple-choice questions restricted entirely to industrial instrumentation, sensors and transducers, process control and microprocessors, plus five or six higher-weighted reasoning questions recycled from past papers. The candidate did not clear it.
Covered · Domain knowledge, Aptitude
2
Technical interviewTechnical
Reported second-hand as the stage that follows the written test; the candidate did not reach it.
Covered · Domain knowledge
3
HR interviewBehavioral
The closing stage of the drive, which the candidate did not reach.
Three problems over three hours, escalating from a simple GCD exercise through a dynamic-programming question to a harder string-manipulation problem. Around 35 students advanced.
Teams of five built a prototype in four hours, choosing between an IoT home-automation build, a ticket-booking application under given constraints, or a Battleship game. One or two people per team advanced, judged on coding, teamwork and how well they understood what they had built.
Covered · Past projects, API design, Low-level design
3
Personal interviewTechnical
Resume-driven questions plus a few programs to write on the spot around string manipulation and data structures. There was no separate HR round in this cycle.
Covered · Past projects, Arrays & strings, Data structures & algorithms
A HackerRank screen with two algorithmic problems (including a search in a circular array counting comparisons) plus an implementation task requiring the candidate to call a JSON API and extract a field. Generous time limit.
Covered · Arrays & strings, Data structures & algorithms, API design
2
Technical interviewTechnical
Systems-flavoured questioning on C++ data types and ranges, storage class specifiers, global versus static, and recursion, then real-time operating system concepts including round-robin scheduling, closing with finding a linked list's midpoint in one pass.
Covered · OOP, Operating systems, Concurrency, Data structures & algorithms
3
HR interviewBehavioral
HR walked through the candidate's projects and the technologies used, then covered knowledge of Honeywell and motivation for joining.
Covered · Past projects, Behavioral, Domain knowledge
Multiple-choice questions across OOP, data structures, aptitude and databases plus two very easy programming problems. More than a hundred students went through.
Covered · OOP, Data structures & algorithms, Aptitude, DBMS
2
Technical interviewTechnical
A twenty-five minute round built entirely on the candidate's resume: detailed project explanation, then hypothetical scenarios asking them to design an extension of their own system, plus database and SQL optimisation questions prompted by the resume.
Covered · Past projects, System design, SQL, DBMS
3
HR interviewBehavioral
A fifteen-minute closing chat on favourite projects, learning speed, self-assessment on picking up new technology, and motivation for Honeywell. Results came the next day; 24 interns were selected.
An in-person interview held at the candidate's university with two other candidates present, mixing values-oriented questions about innovation with a basic accounting question.
Covered · Behavioral, Domain knowledge
2
Super dayFinal
Candidates who cleared the campus round advanced to a super day. The overall process ran one to two months and ended without an offer.
A HackerRank paper of three DSA problems in one hour: one graph question and two logic or sorting problems written in a competitive-programming style.
Covered · Graphs, Data structures & algorithms, Arrays & strings
2
Technical interviewTechnical
An online round beginning with an overview of all projects then a deep dive into one development project, followed by tree questions covering how to declare and traverse the structure with code, a puzzle, and development-concept questions tied back to the project.
Covered · Past projects, Trees, Data structures & algorithms, Puzzles
3
HR interviewBehavioral
Behavioural questions on motivation for the company and the role, ending with the candidate asking for feedback on themselves and about the projects they would work on. The result came through about half an hour later.
Three medium-difficulty coding problems that the candidate felt were reachable after roughly two months of consistent DSA practice.
Covered · Data structures & algorithms, Dynamic programming
2
Technical interviewTechnical
Standard interview topics covering OOP, pseudo-code for common competitive-programming problems, probability and statistics and puzzles, though in this candidate's case the interviewer spent the whole round grilling the CV on past projects and experience.
Covered · OOP, Data structures & algorithms, Past projects, Puzzles
3
Cultural interviewBehavioral
An HR-run fit conversation the candidate described as largely a formality, but one where knowing Honeywell's domains, recent projects and leadership helps.
A HackerRank paper of three easy-to-medium DSA problems in one hour, testing sorting, logic and graph algorithms.
Covered · Graphs, Data structures & algorithms, Arrays & strings
2
Technical + HR interviewTechnical
Unlike previous years this cycle collapsed to a single round: five easy-to-medium DSA questions, a brain teaser, and a discussion of the candidate's development projects. The result arrived the next day.
Covered · Data structures & algorithms, Puzzles, Past projects, Behavioral
A 45-minute call with a senior product manager and a senior director of product covering background, knowledge of Honeywell and the role, then a detailed interrogation of resume projects (why it was built, how the need was identified, target customer and cost, what could be improved) plus product lifecycle fundamentals including the product owner versus product manager distinction.
Covered · Past projects, Domain knowledge, Behavioral
2
Video interview with the hiring teamHiring manager
A 45-minute conversation with the senior product manager of the team, covering prior work experience, technical tooling, what an API is and why it is used, data experience, and the candidate's own definition of the product manager role. The offer came about a week later.
Covered · Past projects, API design, SQL, Domain knowledge
A mixed paper of aptitude and technical multiple-choice questions followed by a coding section that rewarded clean logic and careful constraint handling rather than exotic techniques.
Covered · Aptitude, Data structures & algorithms
2
48-hour hackathonTake-home
A two-day hackathon run through Honeywell's campus-connect platform on real-world problem statements. The candidate picked a flight schedule optimisation problem, built a working model and presented both the approach and a set of future enhancements, which the panel responded well to.
Covered · Past projects, System design, Domain knowledge
3
Technical + HR interviewHiring manager
An unusually conversational round: introduction, software questions despite the candidate targeting ML, a live demo of their portfolio site, discussion of an ML summer school stint and of LangChain and automation work, then a question about which role families they would be comfortable in. The offer email arrived within hours.
Covered · Past projects, Behavioral, Domain knowledge
What is the interview process like at Honeywell International?
Honeywell's loop splits cleanly by geography and function. In India, where the bulk of published accounts come from, it is a classic campus funnel: a timed online assessment (HackerRank or HackerEarth, sometimes a separate aptitude/MCQ paper), one or two technical interviews that lean on core CS fundamentals and heavy resume/project grilling, and a short HR or cultural-fit round; some cycles substitute a team hackathon or a group discussion for a second technical round. In the US, corporate and product roles run a lighter, behaviour-first sequence: recruiter or on-campus screen, then a hiring-manager conversation or a multi-person panel, with only one or two role-specific technical questions. Interviewers repeatedly steer toward what candidates actually built rather than abstract puzzles, and the non-software campus streams (instrumentation, process/chemical) get discipline-specific written tests instead of DSA.
What topics does Honeywell International test in interviews?
Commonly reported topics include Data structures & algorithms, Dynamic programming, Graphs, Trees, Arrays & strings, OOP.
These guides summarize public, first-hand interview experiences shared by candidates. They describe the shape of each loop and the topics that came up, not a leaked question bank, and every experience links back to its original source. Processes change often; treat this as directional prep, not a script.
