What to expect interviewing for software roles at Carrier Corporation: recruiter and manager conversations, practical technical questions on OOP, SQL and Java or WPF stacks, and reported scheduling and communication friction.
$97K
Avg. Base Comp
$130K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates who interviewed for software-related roles at Carrier describe a mix of behavioral and practical technical conversations rather than puzzle-style screens. One candidate reported OOP concepts, data structures and algorithms fundamentals, and SQL queries, with a conflict-with-a-coworker question in the behavioral mix. A senior candidate reported a roughly thirty-minute virtual technical round where they refactored or debugged supplied code in a notepad-style editor within about five minutes, with questions on interfaces and WPF binding. A second technical round reportedly covered Core Java, Spring and React, followed by a manager round about a difficult project. So match your preparation to the specific stack in the posting.
An intern candidate described a different style: a manager conversation walking through resume projects in detail, plus a design question about structuring code across multiple databases with overlapping and distinct data. That candidate described it as conversational and not an algorithm grind, so be ready to explain what you built and why.
Several candidates also reported process friction. A UI/UX engineer described two recruiter calls, three virtual interviews and an onsite with a six-person panel that was rescheduled several times, then about three weeks of silence before a rejection. An embedded candidate on an L2 visa reported being screened out over work authorization after a recruiter's unverified guess, so confirm eligibility details early and in writing. Reported outcomes in this set were mostly rejections, with one internship offer. Confirm interview times ahead of each round and keep your own notes on timelines.
Synthesized from 5 candidate 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 Carrier Corporation process.
The interview process at Carrier was straightforward but ultimately didn't work out. I went through three rounds total — two technical interviews plus one with a manager. The first technical round was virtual and lasted about thirty minutes. The interviewer had their camera off, which felt a bit impersonal, but they asked me to share my screen and code on a notepad. They provided some existing code and asked me to refactor or debug it within five minutes. The questions covered object-oriented programming concepts like interfaces and different types of binding in WPF. It was fairly manageable, nothing that felt overly tricky. The second technical round dug deeper into my full stack skills, focusing on Core Java and Spring on the backend, then React for the frontend. The interviewers were decent and professional, and the overall vibe was positive — they seemed genuinely interested in my experience. The final round with the manager felt like a standard behavioral interview where they asked me to walk through a time I handled a difficult project. The workplace itself seemed nice based on what I could see, and the interviewers weren't unfriendly. Despite the good experience during the process, I was rejected after the final round. Looking back, I wish I'd had more time to prepare for the specific stack they were using, especially the WPF questions, which caught me a bit off guard.
Prep tip from this candidate
For Carrier's interview, be ready for WPF binding questions alongside your Core Java and Spring knowledge — they seem to value Windows desktop development alongside web stack. Practice refactoring code quickly under time pressure, especially in a notepad-style environment without an IDE.
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 Carrier Corporation
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Merge Sorted Lists | |
| Prime to N | |
| Bagging vs Boosting | |
| Hurdles In Data Projects | |
| Size of Joins | |
| The Brackets Problem | |
| Real-Time Transaction Streaming | |
| Level Of Rain Water In 2D Terrain | |
| Cyclic Detection | |
| Longest Increasing Subsequence | |
| Term Frequency | |
| Find Duplicate Numbers in a List | |
| Multi-Reaction | |
| RAG Strict Source Control | |
| Merge N Sorted Lists | |
| Worker Distribution Dilemma | |
| Offer Matching API Design | |
| Loan Model | |
| Seller Type Modeling | |
| Solo ML Deployment | |
| The Pirate’s Hunt | |
| String Palindromes | |
| Data Stream Median | |
| Gas Station Counting | |
| Shortest Transformation | |
| Hidden Substring Segment | |
| International e-Commerce Warehouse | |
| Safe Deployments | |
| Fixed-Length Arrays: Deletion |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with a recruiter or HR call. Topics reported include background and aspirations, logistics and personal information, and in one case work authorization. Candidates may want to confirm visa and eligibility details early and in writing, since one reported being screened out on a recruiter's guess.
Candidates report practical technical questions rather than puzzles. Reported topics include OOP, data structures and algorithms basics, SQL queries, interfaces, WPF binding, and a timed refactor or debug exercise in a notepad-style editor. A second technical round reportedly covered Core Java, Spring and React. Exact content likely depends on the team and stack.
Candidates report a manager conversation covering past projects, a difficult project or conflict with a coworker, handling pressure, and day-to-day collaboration. An intern candidate also described a database design question about structuring code across multiple datasets. Be prepared to explain your own work in detail.
Some candidates report an onsite with a facility tour or a panel of several interviewers. One candidate reported repeated rescheduling and about three weeks waiting for a decision after the onsite. Communication may be slow, so confirm timing before each round and ask about next steps.
