Honeywell Product Manager interview typically runs 3 rounds: online technical and aptitude test, technical interview, HR interview. It usually takes about a month end to end and is notably slow and drawn out.
$115K
Avg. Base Comp
$192K
Avg. Total Comp
3-4
Typical Rounds
3-5 weeks
Process Length
Our candidates report that Honeywell is less interested in polished product jargon and more interested in whether you can translate your background into a manufacturing context. A recurring theme is the heavy focus on college work, projects, and internships: one candidate said they had to walk through their academic path in detail, explain projects end to end, and connect internship experience directly to product development and management. That tells us the bar is not abstract PM fluency; it’s credible, specific evidence that you understand how products get built in an industrial environment.
We’ve also seen that Honeywell leans hard into practical, supplier-facing thinking. The candidate experience called out questions about manufacturing suppliers, why they left a previous company, and a request to prepare a presentation and business case. Those signals suggest they care about commercial judgment and operational realism as much as product sense. In our view, the non-obvious make-or-break factor here is whether your examples sound like they came from real work with constraints, stakeholders, and tradeoffs—not just classroom or internship summaries. Candidates who can show that their past work maps cleanly to a supplier-heavy, manufacturing-driven product role tend to come across as much stronger.
Synthetized from 1 candidates 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.
I applied through university, and the whole process was very slow, almost a month end to end. It started with an online technical and aptitude test that was easy to moderate, then there was a technical interview on Teams about a month later, and an HR interview two days after that. Most of the questions were centered on my background, so I had to walk through what I studied in college, explain my projects in detail, and talk through my internship experience. I also got a lot of specific experience-based questions around product development and management, which made it feel less like a generic PM screen and more like they were checking whether I could connect my past work to the role.
The process itself felt a bit drawn out and not very responsive. I also had to prepare a presentation and build a business case, which felt like a lot of work for an interview process. One question that stood out was why I had left my previous company, and another was about my experience with manufacturing suppliers, so they clearly cared about practical, industry-related exposure. After all of that, I did not get an offer, and there was no real feedback afterward. My main takeaway is to be very thorough on your own projects and internships, and be ready to explain how your experience fits product work in a manufacturing or supplier-heavy environment.
Prep tip from this candidate
Be ready to defend a presentation/business case as part of the process, and practice explaining your projects, internships, and college work in a way that connects directly to product development and manufacturing suppliers. Also prepare a clear answer for why you left your last company, since that came up explicitly.
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
How would we build a model to detect fraud and text customers to approve or deny fraudulent transactions
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Bagging vs Boosting | |
| Covariance vs Correlation | |
| Random Forest Explanation | |
| Loan Model | |
| String Palindromes | |
| Bias vs. Variance Tradeoff | |
| Data Preparation for Imbalanced Data | |
| Pizza No Show | |
| Testing Constraints | |
| Minimize Wrong Orders | |
| Expected Churn | |
| Merchant Acquisition | |
| Your Strengths and Weaknesses | |
| Analyzing Churn Behavior | |
| Rebalance Probabilities | |
| Retention Rate Disparity | |
| Late Orders | |
| Bootstrapping Samples | |
| Bias Variance Tradeoff | |
| Risk Model for a Mortgage Bank | |
| Booking Regression | |
| Lasso vs Ridge | |
| Merge N Sorted Lists | |
| Missing Housing Data | |
| Training Instability in Neural Networks | |
| User Event Data Pipeline | |
| Classification and Regression | |
| Offer Matching API Design |
Synthesized from candidate reports. Individual experiences may vary.
The process begins with an online test that covers technical and aptitude questions. In this case, it was described as easy to moderate and served as the first screening step for university applicants.
A technical interview was conducted over Teams about a month after the test. The discussion focused heavily on the candidate’s background, including college coursework, projects, internship experience, and how that experience connected to product development and management.
The candidate was asked to prepare a presentation and build a business case as part of the interview process. This step appeared to assess practical product thinking and the ability to apply experience to a manufacturing or supplier-heavy environment.
An HR interview followed two days after the technical round. Questions were still experience-based, including why the candidate left a previous company and details about manufacturing supplier exposure, along with broader fit and background questions.