Honeywell Company Interview Experience | Dot net developer | Pune
Interview Experience
I got call from Honeywell hr because I applied for dot net developer job through company websiteHr told me it's 3 round of interview technical,hr,manager roundI only give...
Full Details
I got call from Honeywell hr because I applied for dot net developer job through company website Hr told me it's 3 round of interview technical,hr,manager round I only give first round because I got
rejected after first round Round - 1 Below are some questions that interviewer ask me It's a virtual interview round interviewer ask questions related mostly oops c#,.net core,sql He started questioning What is oops concepts give examples of each Explain serialisation and deserialisation in c#. What is difference between read-only and constant. What is static class Static constructor. What is critical features of .net core. What is filter and it's type explain in detail What is assembly , namespace,CLR. What is garbage collection and type of it explain it. What is middleware in .net core. What is status code and type of it explain it. What is action result. What is run and use method in .net core. What is web api Purpose of appseting and launch setting file in .net core. What is auto mapper. What is entity framework .what is managed unmanaged code in .net. What is store procedure. Explain join and it's type in SQL. What is union and union all. What is difference between select and select many in linq. What is abstraction and encapsulation and interface . Difference between overloadig and overriding Linq aggregate function explain. What is sealed class and delegate it's type What is transient singleton and scoped. How to handle exception in c#.
Result Unfortunately I was not selected at that round One thing need to mention here be confident and prepare as much all above concept you will clear interview Best of luck to all
About This Question
This is a candidate experience report from a honeywell interview for a swe role during the manager round reported in 2024.
It covers the following topics: Sql .
Topics
More Honeywell Interview Questions
About Honeywell Interview Reports
This question was reported by a candidate who interviewed at Honeywell. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Honeywell are the higher-signal extractions to take from this report.
For broader preparation context, the Honeywell interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Honeywell reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Honeywell Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Honeywell reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.