Poor planning and communication.
I pre-interviewed for a QA lead role in Java and SQL. I don't really do database work in much depth, so they gave me a chance to review my SQL syntax before the real interview. Unfortunately, the real interview had nothing to do with Java or SQL!
The program manager had a huge ego and ended the interview early after a series of questions about GUI applications, which I know nothing about. 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.
What would be the first priority to test in a GUI application? There is not enough information in the question to answer that. It is too vague.
The following metrics were computed from 1 interview experience for the Guidewire QA Lead role in San Mateo, California.
Guidewire's interview process for their QA Lead roles in San Mateo, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Guidewire's QA Lead interview process in San Mateo, California.