Guidewire Interview Questions & Reviews
Getting an Interview
- Popular Job Titles:
- Senior Software Engineer (9)
- Software Engineer (9)
- Solutions Consultant (6)
- QA Engineer (5)
- Senior Functional Consultant (3)
- Integration Architect (3)
- Solution Developer (2)
- Senior Implementation Consultant (2)
- Senior Product Manager (2)
- Curriculum Developer (2)
- Engineering (2)
- Consultant (2)
- Product Manager (2)
- Java Solutions Consultant (2)
- Senior Implementation Architect (2)
- Implementation Architect (1)
- Sales Enablement (1)
- Technical Product Manager - Consultant (1)
- Technical Consultant - North America (1)
- Software Consultant - Entry Level (1)
- Solution Consultant (Dublin) (1)
- Sales Operatoins (1)
- Director-Finance_Accounting Role (1)
- Graduate Java Consultant (1)
- Product Evangelist (1)
- Support (1)
- Tax Intern (1)
- Software Engineer Internship (1)
- Technilcal Consultant (1)
- User Interface Architect (1)
Senior Product Manager Interview (Negative Experience; Average Interview)
I applied through an employee referral and the process took 1+ week - interviewed at Guidewire in October 2013.
Interview Details – I was an internal referral and was fast tracked. I spoke to 5 people, of whom there was one Platform Program Manager and others were Product Managers, including one Director.
I was quite surprised that barring one of the guys, none... yes, none of them had actually read my resume in any sort of detail. That was pretty off putting.
Interview Question – How do you incorporate time zones into a system that didn't have it in the past? View Answer
Reason for Declining – Although my internal contact spoke highly of GuideWire, I was less than impressed with my interviewers. However, I was given to understand that they had both a major release heading out of the door as well as some conference.
Very Easy Interview
Software Engineer Internship Interview (Neutral Experience; Very Easy Interview)
I applied through college or university and interviewed at Guidewire.
Interview Details – The interview consisted of a few very easy programming questions. More concretely one of them was, given a string count the frequency of characters in a string. Two, given a file directory list all the files in the directory, including those that are in folders inside the directory. The rest of the interview was just talking.
Interview Question – No difficult questions Answer Question
Reason for Declining – Wanted other company
Very Easy Interview
Software Engineering Intern Interview (Positive Experience; Very Easy Interview)
I applied through college or university and the process took a day - interviewed at Guidewire in February 2014.
Interview Details – Applied through a career fair and had a first round interview on-campus. The first round consisted of simple questions involving knowledge of hash functions, graph traversals, and classic java syntax. These guys were so friendly, I was interviewed with two engineers at the same time. Both of them were very nice interesting people.
Interview Question – Given a root directory, return all the sub files of this root directory. Note, a file can be a directory with more sub files or a data file which has no sub files. View Answer
Reason for Declining – I haven't declined yet, the offer is definitely much higher than the average intern position placed on glassdoor. Only reason I chose this option is because glassdoor doesn't have a "Received Offer, not sure yet".
Senior Curriculum Developer Interview (Positive Experience; Difficult Interview)
I applied through a recruiter and the process took 4+ weeks - interviewed at Guidewire in September 2009.
Interview Details – I was contacted by a recruiter, by phone, while I was unemployed. This gave me hope. The recruiter gauged my interest and skills then referred my resume to the hiring manager. The hiring manager was pessimistic but evaluated my skills and invited me in for a face to face interview.
The f2f was grueling: I spoke with six people over four hours, was asked to take a software test, and generally put through the wringer. The people were interesting and friendly though.
I didn't hear from them for several weeks. Then suddenly the recruiter called me with an offer, which I accepted without attempting to negotiate.
Interview Question – Why aren't you employed? View Answer
Negotiation Details – I didn't try.
Sales Operatoins Interview (Positive Experience; Average Interview)
I applied through a recruiter and the process took 5 weeks - interviewed at Guidewire.
Interview Details – Initially contacted by a recruiter. I had a "discussion" (phone interview) with her to begin with, then went into the office for my interview. I met with three people during the interview. The interview process was very straightforward.
Negotiation Details – The offer was extended via the recruiter. The recruiter explained everything to me very well. I was pleased with the offer.
Sales Enablement Interview (Positive Experience; Difficult Interview)
I applied through a recruiter and the process took 2 weeks - interviewed at Guidewire in July 2012.
Interview Details – Very detailed process. I live in a different state than where the company is headquartered, so I had 4-5 hour-long phone interviews with various team members and other people I would interact with frequently. I then traveled to headquarters for 3 hours of in-person interviews, a casual interview over lunch, and an hour-long, in-character presentation based on a case study I was given the week prior. Overall, talked to my manager, her manager, three team members, and four other coworkers who I engage with frequently.
Interview Question – The case study presentation was the most difficult/highest pressure part. Every employee is given a case study that is appropriate for their position (developers have to debug code, for example). They do this to see an example of your work, but also to see how you handle criticism and pressure. I received the case study on a Thursday evening, and presented the following Monday afternoon. Answer Question
Negotiation Details – Was done over the phone. Early in the process, I indicated what I was previously making. A few days after the in-person interview & case study presentation, the HR manager called with details of the offer. I was told that they try to make the best offer possible, and typically don't do a lot of negotiation. The offer was very good, and I accepted.
Software Engineer Interview (Positive Experience; Average Interview)
I applied through a recruiter and the process took 2 days - interviewed at Guidewire in August 2009.
Interview Details – 2 day interview
Interview Question – Design a poker game Answer Question
Negotiation Details – Just name a price and it was accepted.
Senior Implementation Consultant Interview (Positive Experience; Difficult Interview)
I applied online and the process took 4 weeks - interviewed at Guidewire in April 2013.
Interview Details – refered by friend, applied, contacted and set up phone interview 1 (passed), took 3 hour technical test (passed), trip to chicago for final interview (was 3 seperate 1 hour interviews) - passed. On the way home from chicago I got an email letting me know they were working on my offer. 3 days later I had my offer and accepted
Interview Question – I had background in there software, there for nothing was very difficult or surprising. In chicago I had to write some code for a recursive function to meet a specific need., View Answer
Negotiation Details – I gave them a range and they of coarse started at the lowest end even though I nailed the interview. Fortuently I made my lowest number the number I was really wanting and that anything more was a bonus in my mind. I did ask why they offered what they did in the range I provided and they were able to explain with decent logic. As well as the company stock helps you not worry about it.
Integration Architect Interview (Positive Experience; Difficult Interview)
I applied through a recruiter and the process took 4+ weeks - interviewed at Guidewire in March 2013.
Interview Details – Right from the beginning Guidewire made it clear about their interview process and was prompt in scheduling, giving feedback and going for the next round. It became very clear from the beginning that these guys were professional, intelligent and a fun set of people. The interviews were very open, enthusiastic and more like technical discussions. I have never given interviews like these - it was a pleasure and everyone was genuinely friendly. The face to face interview was with 3 people and each one of them made me feel comfortable and asked great questions. Clearly I had never had such fun in the interview process. Questions were on expected lines and it never felt that these guys were asking anything that would never be used on the job - very logical and practical questions around java and general language constructs. One of the most impressive things about Guidewire was that they are very thorough and detailed in scheduling, providing details and setting up everything along the process. Even after their offer, they went out of their way to set up all the required resources and sent emails with the details. The interview process is tough and lengthy, but once you get through you know that you will be working with brilliant people who themselves went through this process and this gives you that much more confidence.
Interview Question – None really Answer Question
Negotiation Details – The offer was above what I was making [and I work in a bank which is known for great pay] and very good. I asked for a small change in the numbers with supporting documentation for the request. It was granted the next day and I was very happy at the end.
Implementation Architect Interview (Positive Experience; Difficult Interview)
I applied through a recruiter and the process took 2+ weeks - interviewed at Guidewire in February 2013.
Interview Details – Guidewire is a class act organization, they move fast on the interview process and are very professional all around.
First phone screen with recruiter.
Second phone interview with peer/lead in position.
Third skills test and review, 2 hours to complete an implementation quiz with some programming concepts.
Fourth in person, met with 3 managers in person (Chicago) from various disciplines.
Received offer 3 days later.
Interview Question – Describe in detail object oriented programming concepts, review code, etc View Answer
Reason for Declining – Three full weeks of onsite training (including weekends) was hard to swallow.
Interviews for Top Jobs at Guidewire