Real, anonymous reports from people who interviewed for Software Engineer at Chubb, newest first and distilled into what to expect across the loop.
I went through a short two-round process that was fairly average in difficulty, usually completed in about two weeks, and still ended in a late-stage rejection.
I experienced a mostly straightforward, recruiter-to-technical flow that centered on Java/SQL and my projects, with generally fair difficulty and mixed outcomes across rounds.
The interview process typically involves an HR screen followed by an online assessment, and then 2-3 technical interviews, often spanning 1-2 weeks. Candidates should be prepared for a structured flow that may include both technical and managerial discussions.
Candidates can expect a mix of coding questions, often based on data structures and algorithms (DSA), along with core computer science topics like OOP and SQL. The difficulty can vary, but many report that strong performance in the online assessment is crucial for advancing.
Behavioral interviews focus on background, role fit, and interpersonal skills, often assessing how candidates communicate and collaborate. Candidates should prepare to discuss their projects and how they align with the company's values.
Technical interviews may involve deep dives into resume details and project experiences, with varying levels of difficulty. Candidates should be ready to explain their past work thoroughly and demonstrate a solid understanding of technical concepts.
Candidates noted that the tone and professionalism of interviewers can significantly impact the experience, with some reporting unprofessional interactions. It's important to remain composed and articulate, even in challenging dynamics.
Many candidates reported not receiving feedback after rejections, leading to a sense of opacity in the decision-making process. It's advisable to follow up for feedback, but candidates should be prepared for the possibility of no response.