Guidewire Software Engineer interviews typically combine a Codility coding screen, live Java/OOP pair-programming rounds, and a resume or behavioral discussion, with a design round appearing in some loops; reported round counts and timelines vary by candidate.
$110K
Avg. Base Comp
$142K
Avg. Total Comp
2-5 rounds
Typical Rounds
2 months
Process Length
Guidewire's software engineer interviews typically start with an online coding assessment, often administered through Codility, before moving into one or more live technical rounds. Across candidate reports, the technical bar centers on core Java and object-oriented fundamentals — think static versus abstract, OOP design choices, and practical Java questions — rather than obscure algorithms. A recurring format is pair programming: candidates describe implementing a card game or a wallet and currency-conversion feature live with an interviewer. One candidate was even asked to clone and extend their own past project on the spot, which rewards being able to narrate your thought process clearly and knowing your own code well.
Some loops also include a design component. One candidate was asked to design WhatsApp, and another faced a custom Iterator design problem with hasNext() and next(). Most loops also include a resume-driven or behavioral round covering past projects and collaboration style. Rounds generally run from two to five, and one candidate described the process taking almost two months, with long waits between steps.
Communication between stages can be slow. Candidates mention waiting weeks between steps and, in one case, an automated rejection with no feedback, so it's worth asking recruiters directly about expected timelines and next steps. Preparation should prioritize Java/OOP fluency, comfort narrating code live, code-review style questions on existing snippets, and a couple of well-rehearsed project stories you can explain in depth. Those elements show up most consistently in reported interviews.
Synthesized from 18 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 Guidewire Software process.
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 Guidewire Software
Minimum Change
| Question | |
|---|---|
| Messenger Service Design | |
| Minimum Days for Scheduling All Meetings | |
| Client Solution Pushback | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Random SQL Sample | |
| Top 3 Users | |
| Raining in Seattle | |
| Find the First Non-Repeating Character in a String | |
| Rolling Bank Transactions | |
| String Shift | |
| Customer Orders | |
| Comments Histogram | |
| Retailer Data Warehouse | |
| Download Facts | |
| P-value to a Layman | |
| Flight Records | |
| Bagging vs Boosting | |
| Prime to N | |
| Daily Retention Summary | |
| Google Maps Improvement | |
| Upsell Transactions | |
| Find Bigrams | |
| First Touch Attribution |
Synthesized from candidate reports. Individual experiences may vary.
Several candidates report an initial online assessment, often on Codility; one internship candidate described two data-structure and algorithm problems. Reported problems include interval and meeting-time logic, such as working out how long an employee could sleep between meetings. Treat this stage with real coding rigor and test edge cases before submitting.
A recurring format is a live, collaborative coding session instead of a solo whiteboard test. Candidates describe implementing a card game in Java, dollar-to-penny conversions and wallet balance calculations, or a plane seat reservation problem, with an interviewer who may offer guidance along the way. One candidate was asked to clone one of their own past projects and add a new feature live. Interviewers seem to weigh how clearly you narrate your approach.
Candidates describe Java and object-oriented theory questions, such as static versus abstract, along with practical questions about working with web APIs and core Java concepts. One candidate was handed a code snippet and asked to spot the problems and suggest fixes rather than write from scratch, suggesting conceptual clarity matters as much as working code.
Some candidates faced a design round. One was asked to design WhatsApp, and another tackled a custom Iterator with hasNext() and next() in a director round. Another candidate was asked to walk through their current application architecture and the automation framework they had worked on, so being able to explain systems you've actually built appears to matter.
A behavioral or resume-driven conversation typically appears toward the end of the process. It covers past projects and situational prompts, such as how you'd communicate with a busy coworker or a time you learned a new skill. For some candidates this is folded into a manager or director conversation.
