Chubb AI Engineer interview typically runs 2 rounds: recruiter screen and a technical round. The process spans several weeks with notably slow communication and last-minute confirmations.
$130K
Avg. Base Comp
$185K
Avg. Total Comp
3
Typical Rounds
3-6 weeks
Process Length
With only one candidate experience on record, we're working with a limited sample — but what that experience reveals is striking enough to be worth taking seriously. The process at Chubb was notably unstructured from start to finish, and our candidate's account suggests that navigating ambiguity without losing your footing may be the real evaluation happening beneath the surface. The technical content itself was light — a foundational statistics question like covariance vs. correlation — which implies the bar isn't set at a high technical ceiling, at least for this role.
What's more telling is the shape of the friction. The recruiter appeared under-briefed on the actual role, questions surfaced in the final round that had no connection to anything previewed earlier, and the screensharing setup was awkward enough to disrupt the candidate's flow mid-interview. Multiple small signals point to a team that hasn't fully standardized its hiring process yet. That's not necessarily disqualifying, but it does mean candidates should treat every verbal commitment as unconfirmed until it's documented — start dates, timelines, flexibility on logistics. Our candidate learned this the hard way when an assumed accommodation on the start date turned into a rescinded offer.
The non-obvious risk here isn't the technical round. It's the coordination layer. Candidates who come in expecting a tight, well-communicated process will be caught off guard. Those who ask clarifying questions early, confirm details proactively, and don't read silence as progress tend to fare better in environments like this one.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Chubb process.
This was easily the most disorganized interview process I’ve had. I first met them at Grace Hopper, and even that got off on the wrong foot because they had the time of my interview wrong and we had to reschedule. After that, the recruiter I spoke with seemed to know very little about the role, and communication was slow the whole way through. I’d finish a stage and then hear nothing for a while, even after following up. Eventually they reached out again for a final round, but they didn’t send the confirmation with the time and structure until the night before, which already made it feel pretty sloppy.
The final interview itself was a technical round, but it wasn’t very well thought out. One odd thing was that they had me stop screensharing with the interviewer so I could type code, which felt awkward and unnecessary. I also got asked about things that weren’t really mentioned in the job description or in the recruiter’s earlier messages, so I couldn’t really prepare for the exact content. After that, there was another long wait before I finally got an offer over the phone. Even then, the recruiter was hard to coordinate with, and they kept asking whether I was interviewing elsewhere or considering other offers, which felt unprofessional. I had a week to decide, and when I asked to push my start date back, I was told it should be fine, then told at the deadline that it wouldn’t be accommodated. They treated that as a decline and pulled the offer. My main takeaway is to get every detail in writing and not assume anything about timing, structure, or flexibility until it’s confirmed.
Prep tip from this candidate
Be ready for a technical round where you may be asked to stop screensharing and type code live, and don’t assume the interview content will match the job description closely. If you get to the offer stage, get any start-date flexibility confirmed in writing before you rely on it.
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 Chubb
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Get Top N Frequent Words | |
| Covariance vs Correlation | |
| Find Duplicate Numbers in a List | |
| Employee Salaries | |
| Hurdles In Data Projects | |
| Size of Joins | |
| Bagging vs Boosting | |
| Random SQL Sample | |
| P-value to a Layman | |
| Rectangle Overlap | |
| Booking Regression | |
| Always Excited Users | |
| Total Spent on Products | |
| Data Preparation for Imbalanced Data | |
| Fine-Tuning VS RAG | |
| Transformer Encoder Layer | |
| Distribution of 2X - Y | |
| RAG Strict Source Control | |
| Fair Coin | |
| Assumptions of Linear Regression | |
| Lasso vs Ridge | |
| Integer String Addition | |
| Precision and Recall | |
| Data Pipelines and Aggregation | |
| Boarding Times Bias | |
| RAG Hallucinations | |
| Target Indices | |
| Poker Pair |
Synthesized from candidate reports. Individual experiences may vary.
Initial contact was made at the Grace Hopper conference, where candidates could meet the team and schedule a follow-up. Scheduling issues were noted at this stage, requiring a reschedule of the initial meeting.
A phone or virtual conversation with a recruiter follows the initial contact. The recruiter had limited knowledge of the role, and communication between stages was slow, often requiring follow-up from the candidate.
A technical coding round where candidates are asked to write code and answer role-related questions. Notably, screen sharing was stopped during the coding portion, and some questions covered topics not mentioned in the job description or earlier recruiter communications.