Candidates describe a Geico Software Engineer process built around an online or live coding screen, a behavioral conversation, and sometimes system design. Reported structures and outcomes vary, so prepare for each stage.
$140K
Avg. Base Comp
$160K
Avg. Total Comp
2-5 rounds
Typical Rounds
4 weeks
Process Length
Candidates who interviewed for Geico's Software Engineer role describe a coding-heavy process, but the exact loop varies. Some report two or three rounds, while others describe five that mix behavioral conversations, coding and system design. Several coding reports mention medium LeetCode-style problems on Codility or HackerRank. One candidate said they were not especially hard, and another found a Valid Sudoku problem harder than expected. A largest-palindromic-number problem appears in more than one account.
Understand the problem before you code. One candidate who passed all tests said the interviewer wanted a more deliberate restatement of the requirements and edge cases first. Others describe interviewers who gave hints, and one reports getting none, so practice working independently under time pressure.
Behavioral rounds are reported as detailed. Candidates mention STAR-style questions, probing for concrete project details, and one case of questions about technologies not listed in the job description. System design appears in some loops, with notification systems, a video application and a browser-URL walkthrough mentioned. Not every candidate saw a design round, so confirm the format with your recruiter.
Communication is the most inconsistent part. Some candidates praise clear recruiter updates, while others report late or missing interviewers and long silences. Ask for a round-by-round rundown early and follow up in writing.
Synthesized from 19 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 Geico process.
I went through Geico's interview process after getting a referral, which turned out to be a pretty structured affair — five rounds total. The first stage was a questionnaire followed by an online assessment with a single easy LeetCode problem, which I completed well ahead of the time limit. That got me to the main event: a 1.5-hour interview split into an hour of coding and 30 minutes of behavioral. The technical portion felt straightforward. I was given algorithmic problems to solve, and I worked through them efficiently without much friction. The interviewers were engaged and the technical bar seemed reasonable — nothing obscure or unreasonably hard, just solid fundamentals testing. After that came the behavioral round, which is where things got weird. The interviewer started asking extremely specific questions about technologies and methodologies that weren't even mentioned in the job description. They weren't particularly warm either — the whole vibe felt a bit combative. I answered as best I could, but it was clear we weren't clicking. A few days later I got a call saying they were moving on without me. The interviewer explained that if I'd passed that behavioral round, there would have been one more round and then an offer, so I was close to the finish line. Looking back, the technical interviews were genuinely easy and I felt confident in my performance, but that behavioral round caught me off guard with its focus on tangential technical specifics and the overall unfriendliness of the interaction. I did some digging afterward and found some harsh reviews from current and former employees about this particular role — apparently there's significant friction between the TDP program and the broader engineering teams, which made me wonder if that tension was showing up in how I was being evaluated.
Prep tip from this candidate
The behavioral round here goes beyond standard situational questions — prepare for deep technical dives on specific technologies and methodologies that may not be in the job posting. Research the team culture and TDP program dynamics beforehand, as the interviewer may probe areas that signal fit within a particular team structure.
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 Geico
In which case would you use a bagging algorithm versus a boosting algorithm
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Justify a Neural Network | |
| Your Strengths and Weaknesses | |
| Returning Last Element | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Top Three Salaries | |
| P-value to a Layman | |
| Random SQL Sample | |
| Rectangle Overlap | |
| Size of Joins | |
| Total Spent on Products | |
| Delivery Estimate Model | |
| Get Top N Frequent Words | |
| Type-ahead Search | |
| Always Excited Users | |
| Three Zebras | |
| Precision and Recall | |
| Find Duplicate Numbers in a List | |
| Duplicate Rows | |
| Type I and II Errors | |
| RAG Strict Source Control | |
| Success Measurement | |
| Target Indices | |
| Transformer Encoder Layer | |
| Digitizing Student Test Scores | |
| Swap Variables | |
| Common Prefix | |
| Integer String Addition |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report different starting points, including online applications, referrals and recruiter outreach. One candidate waited about six weeks for initial contact, while another received an assessment invite within about a week. Ask the recruiter for a written outline of the rounds, since candidates report the format differing from what they expected.
Several candidates describe an online assessment or a live coding screen on Codility or HackerRank, typically one or two medium-level problems. One intern says passing most or all test cases decided who advanced. Another candidate reports being judged on how thoroughly they understood the problem before coding, so restate requirements and test edge cases.
Later coding rounds are reported at roughly an hour, with medium LeetCode-style problems, sometimes with follow-ups on input validation or complexity. Candidates report mixed interviewer styles. Some received hints and guidance, while another received none. A largest-palindromic-number problem is mentioned in more than one account.
Some candidates report a system design round, with prompts including a notification system, a video application and what happens when you type a URL into a browser. Others, including one who prepared for it, say no design round took place. Prepare core design fundamentals, but confirm with your recruiter whether your loop includes one.
Candidates describe behavioral conversations of about 30 minutes in some loops, typically using STAR-style questions. Interviewers reportedly press for concrete details on decisions, leadership and technical problem solving, and may ask why you want to work at Geico. One candidate was asked about technologies not in the job description, so be ready to go deeper on your own projects.
