Chubb Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 83 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Chubb.
Chubb
Software Development Engineer
Entry Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding
The whole interview was a good experience, and I felt comfortable. The questions were clear, the interviewers were helpful, and the difficulty was just right. It was a structured process with good communication, and I felt I could show my skills well. However, they asked questions from so many areas, making it tough.
Confirmed questions4 questions
- Questions about FastAPI
- Questions about OOPs
- Questions about why Pydantic models are used
Chubb
Associate Software Engineer
Entry Difficult Positive experience Accept offer 2 rounds
Interview process
Technical screen Technical screen Onsite
Interview formats
Technical Coding Technical
The whole process consisted of 1 assessment with 5 leetcode questions of medium and hard difficulty, and 2 interview rounds. The first round was purely technical, where they asked me to live code a graph question, and also asked about my projects and some ML questions. Round 2 was much more difficult, they went very deep into my projects and asked me SDE2 level questions.
Confirmed questions4 questions
- Live code number of islands (graph question)
- ML and DL basics
- Project and DSA
Chubb
Software Engineer
Intern Average Positive experience No offer 2 rounds
Interview process
Take home Technical screen
Interview formats
Technical Coding
I had a great interview experience. The interviewers were super knowledgeable and prepared, they really looked at my resume and knew about the tech tests I did before. They were clearly experts and asked good questions showing they understood the field. They asked about Data Structures and Algorithms (DSA) and core computer science stuff. The technical part was hard but fair, felt like a real chat more than just being judged. Overall, it was a professional, fun process that tested my practical and theoretical knowledge.
Confirmed questions2 questions
- Could you answer some questions about Java basics?
- Can we discuss your projects? (This part was hard.)
Chubb Software Engineer Interview Questions
Quoted word for word from Chubb interview reports.
“What is the maximum number of indexes allowed in a table?”
Read reports →“What is the length of the longest subsequence where the XOR of adjacent elements equals K?”
Read reports →“What is the maximum occurrence of a character in a string?”
Read reports →“Suppose there are n stairs, can you provide a Python code to calculate the number of possible ways to reach the top? For 3 stairs, for instance, you can go 1,1,1, or 2 then 1, or jump directly to the 3rd stair.”
Read reports →“Is it possible to overload the main method in Java?”
Read report →“How would you sort a Hashmap based on its values in ascending order?”
Read report →“What's the difference between a Primary Key and a Foreign Key?”
Read report →“Given a room with 7 red socks and 7 blue socks, and it's completely dark, how many socks do you need to pull out to guarantee a matching pair?”
Read report →“How would you sort an array that contains only 0s, 1s, and 2s?”
Read report →Formats, difficulty and experience
Across all 83 Chubb interview reports.