Guidewire Software software engineer candidates report a Java-centered process that can combine an assessment, pair programming, practical coding, design or architecture discussion, and behavioral conversation.
$127K
Avg. Base Comp
$167K
Avg. Total Comp
2-5 rounds
Typical Rounds
6-8 weeks
Process Length
Guidewire Software software engineer interviews reported here lean toward practical Java work and discussion of the systems you have actually built. Prepare to write and explain Java code live. One candidate completed a pair-programming exercise involving dollar-to-penny conversions and wallet balances, while another implemented a card game with a senior developer. Other reports describe LeetCode-style coding, Java fundamentals such as static versus abstract, and reviewing a snippet to identify problems and propose fixes.
The technical emphasis is not limited to algorithms. Candidates also describe an iterator-design problem, explaining application architecture and an automation framework, and a system-design discussion. Practice narrating your choices as you work: clarify assumptions, make trade-offs visible, and connect object-oriented decisions to correctness and maintainability. Bring a project you can explain in depth; one reported exercise asked the candidate to clone their own project and add a feature live.
Expect communication to matter alongside the technical work. Reported later conversations included project and resume discussion, collaboration scenarios, and a question about learning a new skill. The available reports vary in location and seniority, so the exact sequence may differ.
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 Guidewire Software process.
I completed three rounds of the interview process. The first round was an online assessment. The second round was a pair-programming session where I was asked to implement dollar-to-penny conversions and wallet balance calculations. This was followed by an in-depth discussion on Java core concepts, which I found particularly engaging and interesting. The questions covered both practical problem-solving and a strong understanding of Java fundamentals.
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 | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Retailer Data Warehouse | |
| Download Facts | |
| P-value to a Layman | |
| Prime to N | |
| Bagging vs Boosting | |
| Google Maps Improvement | |
| Upsell Transactions | |
| Daily Retention Summary | |
| Find Bigrams | |
| First Touch Attribution | |
| Job Recommendation |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a Codility test or online assessment before later conversations. One assessment report described an implementation-style prompt; prepare for a concise coding exercise, but the available reports do not establish one standard assessment format.
Candidates report pair-programming sessions and live Java implementation, including a card game and wallet-balance calculations. Another report describes LeetCode-style coding. Expect to explain your approach while coding and adapt when an interviewer offers guidance.
Reported technical discussions covered Java core concepts, static versus abstract, OOP, API familiarity, custom iterator design, and reviewing a code snippet for problems and fixes. Candidates should be ready to justify design choices rather than only produce an answer.
Some candidates report explaining their current application architecture and automation framework; another reported a high-level messaging-system design discussion. The focus may be on how you structure and communicate real software decisions.
Candidates report resume and project deep-dives alongside situational questions about collaboration and learning a new skill. Prepare specific examples that show how you work with teammates and how you developed technical judgment.
