Guidewire Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 172 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Guidewire.
Guidewire
Software Engineer
Entry Difficult Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Technical screen
Interview formats
Coding Technical Behavioral
I sent in my application in December via referral and then I got a call back in February. The whole process involved two technical rounds that were back-to-back on the same day at their Bengaluru office. The first round was with a Senior Developer, and the main task was to code a card game using Java. It felt more like a pair-programming session than a typical DSA or system design round, and the interviewer was pretty helpful, giving me pointers when I got stuck. I managed to get most of the game features working. The second round was all about my resume, digging into my past work and projects. There were two interviewers for this one. They asked me to get one of my projects up and running on their machine and then add a new feature to it right there. Plus, they threw in some technical questions about how I built my project and general core concepts. It was a very practical, hands-on process, really focused on actually building stuff. They expected a solid grasp of everything, even for a fresher. The rejection email took ages to arrive, about 15 days after the interview, and it was just a generic automated message with no specific feedback.
Confirmed questions1 question
- Could you clone one of your projects and implement a new feature live during the interview?
Guidewire
Senior Software Engineer
Senior Easy Negative experience No offer 4 rounds
Interview process
Take home Recruiter call Technical screen Technical screen Recruiter call Technical screen Technical screen Recruiter call
Interview formats
Coding Behavioral Technical Technical Behavioral
The technical interview process had many parts to check skills and how you fit in. First, there was an offline coding test to see your programming and problem-solving skills. Then, an HR interview to talk about salary, notice period, and why you want to change jobs, and also to see if you'd fit the company culture. After that, there were two technical interview rounds. Round 1 was an hour with Java/Spring Boot questions and a coding problem. Round 2 was also an hour, focusing on building an API from existing code and another coding problem. Finally, there was an interview with the Engineering Manager, likely behavioral, to check your soft skills and teamwork. It's a shame they gave unprofessional feedback after you passed everything.
Confirmed questions2 questions
- What is the approach to creating a Microservice?
- Could you describe the debugging process?
Guidewire
Software Engineer Intern
Intern Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Technical screen Onsite
Interview formats
Coding Technical Behavioral
The interview process involved three main rounds: first, a 1-hour online coding test with two problems that needed logical thinking. After passing this, there was a 20-minute HR screening call to discuss the company and benefits. Next, a 1-hour technical interview covered basic questions about my FYP, projects, and programming languages, along with a multiple-choice theory question on topics like inheritance, interfaces, and the difference between equals and ==, plus a live coding question. Finally, a 1-hour hiring manager interview focused on cultural fit, asking about my goals, personality, soft skills, and experiences. The interviewers were professional and friendly, making it a good experience overall, although the hiring process took longer than expected.
Confirmed questions1 question
- Can you explain the difference between default and protected access modifiers?
Guidewire Software Engineer Interview Questions
Quoted word for word from Guidewire interview reports.
“Write a Java method to check if any two contacts in a Contact array share the same phone number. The method should return true if a duplicate phone number is found. Aim for the most efficient solution for a large dataset.”
Read reports →“How would you remove duplicate elements from an array in Java, returning a new array containing only the unique elements?”
Read reports →“Implement the hasNext() and next() methods for a class designed to handle a Collection of Collections, ensuring the main collection is not null or empty and sub-collections are not null.”
Read reports →“Can you implement a sparse matrix in Java? It should have a constructor, a set method, and a get method. The matrix can have millions of rows and columns but will only be populated up to 15%.”
Read reports →“Given a plane with N rows and seats numbered 1 to N, with ten seats in a row labelled 1 to ten, process plane seat reservations.”
Read report →“Could you please code an iterator for a Collection of Collections in Java? Specifically, implement the next() and hasNext() methods, as well as the constructor, adhering to the constraint that only the iterator() method from the Collection interface is available for use.”
Read report →“Could you write a function to generate license plate numbers by converting specific numbers within given string formats into letters?”
Read report →“Given a list of meetings scheduled regularly for every week, identify if a slot availability of x mins that can be fit in.”
Read report →“Finally, could you develop a function to generate all possible license plates that follow the correct format?”
Read report →Formats, difficulty and experience
Across all 172 Guidewire interview reports.