Candidates describe Guardian Life software engineer interviews built around Java fundamentals. One offer recipient reported an aptitude test, a technical round on Spring Boot, SQL and string problems, a panel conversation and a final expectations discussion.
$130K
Avg. Base Comp
$153K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Guardian Life's software engineer interviews, as candidates describe them, center on Java fundamentals. The most detailed report comes from an engineer who received an offer. It began with a lengthy Mettl aptitude test with a fairly low cutoff, roughly 50 to 60 percent. The first technical round then covered core Java, Spring Boot annotations and SQL. It continued with string and array problems such as GCD of strings and longest substring, plus Java 8 Streams questions on filtering, mapping and counting occurrences. A panel conversation about experience came next, and the final round turned to compensation, role clarity and growth opportunities.
A Java intern candidate who did not get an offer saw a different format: a recruiter phone call, recorded video answers, and a live round of 20 to 30 quick questions on object-oriented programming, access modifiers, inheritance, polymorphism, collections and strings. That candidate had expected live coding and did not get it, so ask your recruiter what to expect.
A third candidate was asked to submit a CV through the company's system before meeting the hiring manager, then never heard back. If you apply through a recruiter, follow up on timing.
To prepare, practice explaining how Java and Spring Boot work under the hood rather than reciting definitions. Rehearse Streams and string problems, and be ready to walk through your past projects and the approach you take to problems.
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 Guardian Life process.
A recruiter reached out to me on LinkedIn with a link to schedule a screening interview. They mentioned I'd need to formally submit my CV through their system before moving forward to meet with the hiring manager, which struck me as an unusual requirement. I went ahead and submitted everything as requested, but after that I didn't hear back. It was frustrating because I'd been interested in the role, and the sudden silence made the whole process feel disorganized. I never advanced past that initial submission stage, so I can't speak to what the technical rounds, manager discussions, or HR conversations would have looked like — for me the process simply stalled after the CV submission, with no follow-up from the recruiter.
Prep tip from this candidate
Be prepared for a multi-round process including a written exam, two technical rounds, and manager discussion — but prioritize getting clarity from the recruiter on timeline and next steps after your initial submission, since ghosting after CV submission appears to be a real risk in this pipeline.
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 Guardian Life
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Employee Salaries | |
| Random SQL Sample | |
| Bagging vs Boosting | |
| P-value to a Layman | |
| Size of Joins | |
| Hurdles In Data Projects | |
| Type-ahead Search | |
| Cyclic Detection | |
| Three Zebras | |
| Precision and Recall | |
| Success Measurement | |
| Target Indices | |
| RAG Strict Source Control | |
| Transformer Encoder Layer | |
| Duplicate Rows | |
| Modifying a Billion Rows | |
| Type I and II Errors | |
| Same Characters | |
| Swap Variables | |
| Integer String Addition | |
| The Longest Journey | |
| Employee Benefits Outreach | |
| Triangle as Binary Array | |
| Drink Production Allocation | |
| International e-Commerce Warehouse | |
| Shortest Path Algorithms | |
| Why Do You Want to Work With Us | |
| Decision Tree Evaluation | |
| Stakeholder Communication |
Synthesized from candidate reports. Individual experiences may vary.
One candidate was contacted on LinkedIn with a link to schedule a screening and was asked to submit a CV through the company's system before meeting the hiring manager; no follow-up came afterward. A Java intern candidate instead had a friendly recruiter phone call, then recorded video answers with no interviewer present. Confirm the format and next steps with your recruiter.
A candidate who received an offer describes a fairly lengthy Mettl aptitude test before any technical conversation. The pass bar seemed low, around 50 to 60 percent. Other candidates did not mention this step, so ask whether it applies to your team and how long to set aside.
The engineer candidate reports core Java, Spring Boot annotations and SQL, with interviewers probing how things work under the hood. Coding covered GCD of strings, longest substring, merging two strings in parallel and Java 8 Streams. The Java intern candidate reports 20 to 30 rapid fundamentals questions on OOP, access modifiers, inheritance, collections and strings.
The engineer candidate describes a panel round that felt like a conversation about experience, background and approach to problems. The final round shifted to expectations, including compensation, role clarity and growth opportunities. The tone was described as professional and fair.
