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
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".
I applied online and the process took 2 months - interviewed at Guidewire in November 2013.
Interview Details – Had a series of conversations with a recruiter, first they steered me toward a role I didn't apply to I agreed to talk to the HM about it even though it wasn't what I was looking for. The recruiter then failed to follow up in the timeframe they said they would (thus I moved on assuming I wasn't a fit). After four weeks, they reached out again trying to set up interview for different role (which they did not clarify, I had to ask what role they were trying to set up an interview for), after having the role clarified, I again agreed to chat with the HM, but again, there was no follow up.
I'm really surprised and turned off by the flaky communication, especially for a highly lauded company such as Guidewire. Why are you reaching out to candidates, initiating conversations, just to disappear - even if a candidate is not a fit, the role got filled, etc, simply communicate that, especially when you initiated contact.
Interview Question – Would you be interested in a phone screen with "so and so"? Answer Question
I applied online and interviewed at Guidewire.
Interview Details – HR interview > hiring manager interview > technical interview/activity > in-person presentation/interview. must be good at OO programming. this is the most "technical" sales consultant job ever, it is almost a programming job more than a sales job
Interview Question – write a GoSu program Answer Question
Very Difficult Interview
I applied through a recruiter and the process took 1 week - interviewed at Guidewire.
Interview Details – Applied via LinkedIn, was contacted went through 1 week of interview via phone with recruitment. Then was coordinating to schedule an on-site with the hiring manager. Recruitment calls back 3 days later to tell me not interested, no reason why the change and get an email rejection. Avoid if in Finance or Accounting
Interview Question – Trying to arrange on-site interview Answer Question
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.
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.
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.
I applied through a recruiter and the process took 5 days - interviewed at Guidewire in January 2009.
Interview Details – Poor planning and communication. I pre-interviewed for a QA lead role in Java and SQL. I don't really do database in much depth, so they gave me a change to review my SQL syntax before the real interview. Unfortunately the real interview had nothing to do with Java or SQL!!! Program manager had a huge ego and ended the interview early after a series of questions about GUI applications, which I know nothing about, unfortunately. Guidewire really embarrassed themselves on this one, and perhaps they mixed up the role I was supposed to interview for. A year later I got a job at a company in the next building and saw the Guidewire guys at the gym all the time. Massive, massive egos nonstop. I read their eyes and they remembered me, but none of them even said hello. A friend of mine is there now and doesn't like it - only for the paycheck until something better comes along. Their CEO is a brilliant guy, check him out, but Guidewire is not a recommended company as far as I'm concerned.
Interview Question – "What would be the first priority to test in a GUI application?". There is not enough information in the question to answer that. Too vague. View Answer
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.
Join the Guidewire Team! Thanks for your interest! We're pleased that you're thinking of investing your time and energy with us. At Guidewire, a combination of humane working conditions, an excellent market opportunity… — Full Overview
Provided by employer [?]
This is the employer's chance to tell you why you should work for them. The information provided is from their perspective.
Your feedback has been sent to the team and we'll look into it.
The difficulty rating is the average interview difficulty rating across all interview candidates.
The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.
Your response will be removed from the review – this cannot be undone.
Simply post an anonymous review for a recent interview experience or current/former employer. Your post is anonymous – and if you're worried someone will be able to identify your review, you can even post without telling us your job title and location. Learn More.
No thanks –