Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

7 stories

Likes earn the author +10 XP for the first 3 likes each day

Honeywell TechnologiesSoftware Engineer
Reported Aug 2026

Honeywell Technologies Software Engineer Interview Experience: recruiter discussion of pay and benefits

The selection process felt organized and fairly smooth. The recruiter conversation made the role and its expectations clear, and the questions were straightforward and easy to follow. Compensation and benefits also came up as part of discussing what the position would offer. It felt more like aligning expectations than a stressful grilling. I didn't receive an offer, but it was still a decent and…

HR Screen0
Honeywell TechnologiesSoftware Engineer
Reported Aug 2026

Honeywell Technologies Software Engineer Interview Experience: System design and AI themes

The process focused on explaining concepts and showing how well I understood the work behind them. Rather than going straight into coding, it centered on the systems side of software engineering, and I spent a lot of time talking through system design ideas. There was also a noticeable focus on newer AI themes. I tried to connect what I knew to the current "latest trends" type of questions. The b…

0
Honeywell TechnologiesSoftware Engineer
Reported Jul 2026

Software Engineer interview at Honeywell Technologies: low-level design

The first round began with a low-level-design prompt. I had to design a system, then the conversation moved into object-oriented programming and C++ questions. Nothing about the topics was wildly surprising, and the interview itself felt okay. I did not hear back afterward, though, and because the process did not continue, I assumed I had been rejected. Looking back, the expectations seemed clear…

0
Honeywell TechnologiesSoftware Engineer
Reported Jul 2026

Honeywell Technologies Software Engineer interview: role fit and communication

I was first contacted for an introductory conversation and then moved to a technical interview. The technical discussion centered on the role itself, what I would be doing, and how well I understood the requirements. They also asked about my English language skills and my studies. It felt more like a screen for fit and communication than a hard technical challenge. I did not receive an offer, but…

Technical Screen0
Honeywell TechnologiesSoftware Engineer
Reported Jul 2026

Honeywell Technologies Software Engineer interview: STAR answers and resume discussion

The recruiter call was mostly basic behavioral questions. About a week later, I spoke technically with a group of engineers. The pace was quick, and they explicitly wanted structured answers, so I used STAR throughout. The technical questions were manageable and tied mainly to my resume and background rather than deep, tricky problems. I did not get an offer, but the process was more manageable t…

HR Screen0
Honeywell TechnologiesSoftware Engineer
Reported Jul 2026

Honeywell Technologies Software Engineer interview: interruptions and laughter

The Honeywell Technologies process started with HR, with the recruiter calling candidates one by one. I then met two interviewers in the interview room. Their tone threw me off. They seemed mean, laughed while I answered, and repeatedly interrupted me before I could finish. The format itself was ordinary, but I experienced the interaction as disrespectful and unreceptive. I did not receive an off…

HR Screen0
Honeywell TechnologiesSoftware Engineer
Reported Jun 2026

Honeywell Technologies Software Engineer interview experience

I started with an online assessment, then had a technical interview that covered coding, my projects, and core subjects. After the technical part, I went through a managerial and HR round that focused more on how I work with people: teamwork, communication, and my career goals. What made the process feel different was the balance. It did not feel like a purely technical elimination round. It felt…

Online Assessment0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP