Real, anonymous reports from people who interviewed for Customer Success Engineer at Guidewire Software, newest first and distilled into what to expect across the loop.
Get your personalized Guidewire Software Customer Success Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
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.
> 1 year
Average Negative United States
I went through a long process that felt like it stretched almost a full workday. Total time was around 7+ hours, moving from coding to multiple interview formats without much downtime. The first part was a coding assessment with several questions that combined Java and SQL, and then it quickly turned into a technical interview with a team member.
The live part I remember included one situational and one behavioral interview, and later there was a larger panel-style stretch that made the process feel heavy—multiple sessions back-to-back, with a mix of technical questions and more off-track topics thrown in, which was jarring. There was also a coding round that involved connecting to an interviewer’s remote machine, and the setup was slow enough to be distracting while I was trying to work through the problem. On top of that, the process included another scheduled coding/interview at an odd hour that ran longer than expected.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
