Candidates describe a Liberty Mutual software engineer interview built around a recruiter screen, a technical round with debugging and hashmap-style problems, and behavioral conversations about projects and teamwork.
$117K
Avg. Base Comp
$139K
Avg. Total Comp
Not reported
Typical Rounds
4-8 weeks
Process Length
Candidates who describe the Liberty Mutual software engineer interview most often mention a debugging exercise in the technical round. Several report being handed existing code and asked to find and fix issues, followed by an easy-to-medium problem that leans on hashmaps. One candidate described the debugging piece as closer to a code review than an algorithm puzzle, so practice reading unfamiliar code and explaining your reasoning aloud.
Behavioral questions carry real weight. Reported topics include disagreements with a teammate, asking for help, receiving feedback, projects you are proud of, and your specific contribution to a project. One candidate said behavioral questions dominated every stage, and another received a question about approval for a decision. Having a few structured stories ready is worthwhile.
The format varies. Some candidates describe a recruiter phone screen followed by a 45- to 60-minute technical round with two engineers, which one candidate took on CodeSignal. Others describe a hiring manager conversation with peers, then a technical team round. One candidate reported a system design question on a tiny URL service, and another was asked about React and JavaScript fundamentals, so the experience is not uniform.
Communication was a recurring theme: candidates said interviewers were friendly, gave live feedback, and cared about thought process. One candidate missed the expected output format on a hashmap problem, so clarify requirements before coding. Reports of timing differ, with some candidates waiting about two weeks after the technical round and one describing weeks of silence.
Synthesized from 11 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 Liberty Mutual Insurance process.
The process kicked off with a 30-minute recruiter screen—mostly logistics and light behavioral questions to get a sense of how I work in teams and my background with programming languages. Nothing too intense, just confirming fit and running through my resume. They asked me to walk through a project I'd worked on and how I'd learned different languages, which gave them a baseline on my experience level.
After that came the technical round, a full hour with two engineers using CodeSignal. They had me tackle a debug problem first—finding and fixing bugs in existing code—which felt more like a code review than a typical interview question. Then came a leetcode-style problem on hashmaps, tagged as easy to medium difficulty. The problem itself wasn't the hard part; I got tripped up on the output format, which was a good reminder to clarify expected formats before diving in. The engineers were genuinely nice about it—they encouraged me to talk through my approach, step by step, which made the whole thing feel more collaborative than adversarial. The structure helped me think out loud rather than sit in silence.
One thing that caught me off guard was the timeline. It took about two weeks to hear back after the technical round, and if you advance, there's apparently a final round with the hiring manager and a couple other people where they dig deeper into your resume and behavioral fit. The company seems to value team dynamics and project experience over pure algorithm grinding, so being able to articulate your past work clearly matters a lot. If you get through the technical, be ready to defend your resume choices and explain your problem-solving process in detail.
Prep tip from this candidate
Focus on hashmap problems and output format edge cases—don't just solve the algorithm, double-check how results should be formatted. Also, practice articulating your resume projects clearly and be prepared to explain your debugging approach, since that seems to be a key part of their screen.
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 Liberty Mutual Insurance
Describing a data project and its challenges
| Question | |
|---|---|
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Random SQL Sample | |
| Bagging vs Boosting | |
| Size of Joins | |
| P-value to a Layman | |
| Duplicate Rows | |
| Type-ahead Search | |
| Type I and II Errors | |
| Justify a Neural Network | |
| International e-Commerce Warehouse | |
| Unified Inbox | |
| Decision Tree Evaluation | |
| Cyclic Detection | |
| Three Zebras | |
| Precision and Recall | |
| Swap Variables | |
| Success Measurement | |
| Target Indices | |
| RAG Strict Source Control | |
| Transformer Encoder Layer | |
| Client Solution Pushback | |
| Modifying a Billion Rows | |
| Same Characters | |
| Integer String Addition | |
| The Longest Journey | |
| Employee Benefits Outreach | |
| Triangle as Binary Array |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter call covering background, interest in Liberty Mutual, and light behavioral questions such as working through a disagreement or asking for help. One report mentions logistics like graduation date and citizenship, and another put the call at about 30 minutes. Candidates describe the tone as friendly.
Candidates typically describe a technical session of 45 to 60 minutes with two engineers, sometimes on CodeSignal. Reported content includes a debugging problem where you fix issues in existing code and an easy-to-medium hashmap problem. Some candidates also mention behavioral follow-ups about project contributions during this round.
Several candidates describe a hiring manager conversation, sometimes with peers, and a follow-up round with the technical team or adjacent teams. Reported questions cover conflicts, proud projects, group challenges, and end-to-end project ownership. One candidate said coding appeared again, while others described the later rounds as mostly behavioral.
Candidates report different decision timelines. One said they heard back about two weeks after the technical round, another received an offer a week after interviewing, and one described a stretch of weeks without feedback. One candidate said the recruiter called to walk through feedback after a rejection. Expect some variability in communication.
