Real, anonymous reports from people who interviewed for Software Engineer at Guidewire Software, newest first and distilled into what to expect across the loop.
After a recruiter call, I was asked to complete an online assessment that had two LeetCode-style questions—one easy and one medium. They felt fairly straightforward, and nothing in the problems seemed unusually difficult. A short while later I had a call with an engineering manager where we talked about the role, and near the end I solved a simple coding problem and wrote tests for it. The feedback was immediately positive, and the manager said they wanted me to move forward to an onsite interview.
The process started with a recruiter outreach and then moved into a structured set of rounds. I went through an online screening stage, followed by three more in-person rounds: one centered on problem solving, one focused on system design, and a final round with the hiring manager.
The interview process typically begins with a recruiter call followed by an online coding assessment that includes LeetCode-style questions, often one easy and one medium difficulty. Candidates should prepare for both coding challenges and multiple-choice questions covering computer science fundamentals.
Candidates can expect one or more technical interviews that focus on coding, Java fundamentals, and problem-solving skills, often requiring live coding or debugging. Interviewers may ask candidates to explain their thought processes and trade-offs during problem-solving.
A significant portion of the interview process includes a system design round where candidates may be asked to design a system relevant to the company's work or troubleshoot a system failure scenario. This round is often collaborative and may involve multiple interviewers.
Candidates will likely face behavioral interviews that assess cultural fit and situational responses, focusing on teamwork and conflict resolution. These discussions may occur alongside technical evaluations and require candidates to articulate their experiences clearly.
Some candidates reported issues with scheduling, including missed calls and poor communication from recruiters, which can lead to confusion and frustration. It's important to follow up proactively and maintain clear communication throughout the process.
Candidates expressed mixed feelings about the overall interview experience, with some finding it well-structured while others felt it was poorly managed or lacking in feedback. It's advisable to seek clarity on next steps and feedback after each round to avoid uncertainty.