Guidewire interview questions

I got referred through a recruitment agency. Initially I had little interest in the job as it was in a different city and I had never heard of the company before but the recruiter was quite adamant that I look into it. After a little research and looking at reviews here it was clear this company was above average and had a good work culture so I went for it. The interview process is long but thorough. It was almost 4 weeks from the initial code test to offer. Technical exam: Coding exam for 4 hours with 3 coding problems to solve. One on JDBC, another on improving functional but poorly written code and an optional question on either JMS or iterators. Face-to-face interview: I had 3 individual interviews up to an hour long each. None were particularly technical, focusing mainly on my college projects, communication and people skills. One had some emphasis on problem solving and included a few brain-teasers. During the face-to-face interviews it was immediately apparent that the interviewers were genuinely happy to work for Guidewire and were all highly intelligent, rational people. Despite getting an offer in my home city for a higher base salary I chose Guidewire, they made it an easy choice.

I met this recruiter through LinkedIn when I inquired about a different job and she thought this one would be more of a fit than the one I inquired about. They were very nice and the company is growing fast so I was very intrigued. I interviewed first with the hiring manager and then with her boss. Both were very friendly and seemed like they would be good to work with, but the job seemed to be very poorly defined. Clearly this is a company with a very buzzword-friendly culture because by the end of the second interview, I was totally confused about what the job actually entails. In the end, it was not only a vaguely defined role with a strange title, also significantly more travel than the recruiter had said, so I opted out and did not continue with the interview process.