The interview process included:
There was also another live coding round and 3-4 more rounds with the rest of the team and executives.
The recruiter reached out to me, asking if I was interested in applying to Guidewire. To ensure I was, they went into great detail about how Guidewire is a great employer.
I was trying to understand more about the role, and at one point, they mentioned it's a DevOps/automation role. However, in their words, "We changed the title to SE (Cloud) because we weren't getting candidates who can code properly with DevOps titles." Red flag #1.
The recruiter mentioned that the Codility test is the first step and the second one would be a live coding round, as they want to see how "fast I code." This was red flag #2, but I went ahead with the Codility test because I wanted some practice for other interviews, as I wasn't particularly interested in Guidewire.
Before I took the test, they mentioned it's very easy, with one task that usually takes 20 minutes to solve. The Codility test turned out to be a hard LeetCode problem usually asked by Microsoft. Red flag #3.
The following metrics were computed from 1 interview experience for the Guidewire Senrio Software Engineer role in Toronto, Ontario.
Guidewire's interview process for their Senrio Software Engineer roles in Toronto, Ontario is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Guidewire's Senrio Software Engineer interview process in Toronto, Ontario.