Guidewire Interview Questions
& Process

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.

At Guidewire, there are five interview rounds. The first three are hour-long technical interviews that also include some behavioural questions. These focus on your recent work and how it fits the role. Having similar hands-on experience and being able to explain it with real examples helps a lot. The fourth round is with the Hiring Manager, going deeper into role expectations, team fit, and your potential contributions. The last round is with HR, covering culture fit, communication, and company policies. The Guidewire interviewers are really friendly and make you feel comfortable. They don't push you if you're unsure but encourage honest answers and good discussion.

First, there was a call with HR, a really nice person. Initially, there was an issue with my work hours because I'm a foreigner and can only work 35 hours a week, but a few days later they confirmed it was okay. Then, I had an hour-long interview with the Hiring Manager, which was mostly situational and cultural questions, followed by some technical ones. On the same day, I also had a technical interview that lasted a bit over an hour. A couple of days to a week later, they gave me the green light.

The role was advertised as junior-level with corresponding salary expectations, but the interview felt like it was for a senior role. This felt misleading, like a bait-and-switch. The job description mentioned AWS, Terraform, Kubernetes, and Git. I was rejected for not having deep expertise, showing a clear mismatch between what they asked for and what they evaluated. HR said the interview would cover basic technical concepts, but the questions were advanced/senior level. This process felt like a waste of time because the expectations were set incorrectly from the start. It seems Guidewire isn't internally aligned on what they're looking for, which made the candidate experience frustrating and unfair.