Real, anonymous reports from people who interviewed for Software Engineer at Guidewire Software, newest first and distilled into what to expect across the loop.
Get your personalized Guidewire Software Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
After a recruiter call, I took an online assessment that had two LeetCode-style questions—one easy and one medium. They felt fairly straightforward and I didn’t notice anything unusual about the difficulty. Then I had a call with an engineering manager, and near the end I was asked to solve a simple coding problem and write tests for it. The feedback was immediately positive, and the manager said they wanted to see me at onsite.
Scheduling the onsite is where everything unraveled. I reached out to the recruiter to set it up, but the recruiter didn’t show up for the call. We rescheduled, and they missed it again. At that point I was honestly confused about what was happening, since the earlier round felt like it was moving forward.
2 months ago
Average Neutral Malaysia
I started with the usual application flow, then HR reached out and asked for my current and expected salary. After that, I was given Codility with Java and SQL components—3 Java tests and 1 SQL one. The next step was a live technical interview in Java that focused on OOP, running for about an hour.
Following the technical session, I had a manager interview that was behavioral in nature for another hour. The final step was a director interview on-site that also took about an hour, making the whole sequence feel fairly standard and paced across different interviewers and formats.
2 months ago
Difficult Positive Bengaluru
My process started with an initial screening that used an online assessment for about one stage, followed by four total rounds overall. After the scre…
2 months ago
Average Negative Bengaluru
I had a recruiter outreach early on that explained the hybrid work model—around 2 to 3 days in the office. After that, I went into a screening where I…
3 months ago
Average Positive Bengaluru
My interview journey felt pretty clean and well-organized from the start. The first technical round was rooted heavily in my resume and projects, but …
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Online Assessment
Candidates typically start with an online assessment that includes LeetCode-style coding questions, often focusing on Java and data structures. The difficulty is generally described as easy to medium, setting a foundational expectation for technical skills.
LeetCodeJavaDSA
Technical Interviews
The technical interview rounds often involve coding tasks that require candidates to demonstrate their understanding of Java fundamentals, object-oriented programming, and sometimes system design. Candidates should be prepared for both live coding and discussions about their thought processes.
OOPSystem DesignLive Coding
Behavioral and Managerial Rounds
Candidates will encounter behavioral interviews that assess cultural fit and communication skills, often with hiring managers or directors. These rounds tend to focus on past experiences and how candidates align with the company's values.
Cultural FitCommunicationBehavioral
Onsite Experience
Onsite interviews can involve multiple rounds, including hands-on pair programming and discussions about current projects. Candidates should expect a mix of technical and behavioral questions, with an emphasis on collaboration and real-world problem-solving.
Pair ProgrammingCollaborationOnsite
Communication and Coordination Issues
Several candidates reported issues with communication and scheduling, including missed calls and delays in feedback after interviews. This can lead to frustration and a feeling of unprofessionalism in the process.
CommunicationSchedulingFeedback
Overall Process and Timeline
The interview process can be lengthy, with some candidates experiencing extended timelines and unclear expectations. It's important to remain proactive in following up and to be prepared for potential delays.