Real, anonymous reports from people who interviewed for Software Engineer at Honeywell, newest first and distilled into what to expect across the loop.
Get your personalized Honeywell Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
After a recruiter screen, my process moved fairly quickly and mostly stayed conversational. The recruiter call was about my background and how it fit the role, and then I had a short follow-up interview with a team or hiring manager. Across these rounds, the flow felt pretty relaxed: I walked through my experience, answered behavioral prompts, and also touched on technical basics tied to my resume.
In the manager conversation, it was common to get a mix of role understanding and resume-based questions. One interview focused on my projects and how they connected to what the team needed, while another had a more specific technical angle like CAD-related topics (including GD&T and related experience). Even when there were technical questions, they weren’t delivered like a high-pressure coding gauntlet. I also experienced versions where it stayed strictly behavioral with little to no coding, and the overall tone varied a bit depending on the interviewer.
2 months ago
Average Negative Bengaluru
My first-round screening went poorly mainly due to the interaction itself. It was a phone or video-style call where two interviewers joined, and I struggled to answer a few questions. The camera was off, and I could only hear laughter from the interviewer’s side—like they weren’t able to see me, but the tone clearly wasn’t respectful.
I tried to handle it calmly, even asking politely for clarification on what I needed to do. The overall feel of that round was stressful and demoralizing, and I didn’t make it to an offer. Looking back, what stands out isn’t the content of the questions—it’s that the environment turned negative very quickly, and it affected my confidence more than any single technical miss ever could.
3 months ago
Difficult Neutral Broomfield, CO
My process felt long and more structured than I expected. It started with a manager phone screening, and then I was pulled into a timed aptitude test.…
3 months ago
Difficult Positive Bengaluru
My interviews ended up feeling more like structured conversations around what I could explain than a grind of pure coding. I had a round where the int…
5 months ago
Average Positive Bengaluru
My interview journey leaned heavily on coding fundamentals and Java/OOP-style questions, with very little time spent on personality-only discussion. I…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Flow
The interview process typically starts with a recruiter screen followed by a mix of technical and behavioral interviews, often structured as panel discussions. Candidates noted varying levels of formality and pacing, with some experiences feeling rushed while others were more conversational.
Recruiter screenPanel interviewsStructured flow
Technical Focus & Topics
Candidates encountered a strong emphasis on core technical skills, particularly in Java, OOP, and data structures, with questions designed to assess depth of understanding rather than surface-level knowledge. Some interviews included practical assessments and scenario-based questions that required clear reasoning.
JavaData structuresOOP
Behavioral & Cultural Fit
Behavioral questions were common, focusing on past experiences, leadership, and collaboration, often framed to assess cultural fit within the team. The atmosphere varied significantly depending on the interviewer, affecting candidates' comfort and confidence levels.
Behavioral questionsCultural fitLeadership
Interview Difficulty & Pressure
The difficulty of interviews ranged from average to challenging, with some candidates feeling significant pressure during technical discussions, particularly in timed settings. Others noted a more relaxed approach that prioritized fit over technical prowess.
Interview difficultyPressureTechnical discussions
Feedback & Communication
Many candidates expressed frustration with the communication process, particularly regarding feedback and scheduling delays. Some experienced a lack of follow-through after interviews, which contributed to a sense of uncertainty about their application status.
FeedbackCommunicationScheduling delays
Diversity & Inclusion Concerns
A few candidates reported negative experiences related to bias and unprofessional behavior during interviews, highlighting the importance of a respectful and inclusive environment. These experiences impacted their overall perception of the company culture.