Guidewire is full of talented people. Engineering, Sales, and Services all excel at creating great products and delivering to customers. Best of all, it feels like everybody here is working together toward a common goal.
We have a flat corporate hierarchy and little or no office politics. Your bosses always know what's going on. Unlike most companies, they can know more than many of the workers. There is a culture of openness from the executive level down, so we always have a good idea of the company's current situation, challenges, and strategies.
The company is very engineering-oriented. The engineering team is sharp, and they've got some really cool stuff. There is a heavy focus on quality, but the company also knows that it requires a lot of work and investment. Quality doesn't happen just because people talk a lot about it.
The company knows that faster development will lead to more sales today, but better development will lead to more sales tomorrow. And we want to be here tomorrow. So, the work-life balance is good, and we're proud of what we're building.
Guidewire is a startup but the benefits could be a little better. The company is big enough that individuals work on narrow areas. This can limit your impact and make it hard to learn new things.
Keep visible, come to Thirsty Thursdays, and don't lose touch with the company.
Interview Structure: * Codility test (2 rounds) * Pair programming (2 rounds) * System design (1 round) * Managerial (1 round) The interviewers were comforting and did not focus heavily on LeetCode problems. They also included me in daily meetings
A quick 30-minute HR call was scheduled to go through backgrounds. Following that, I was invited to an on-site interview. The interview process included: * One round of technical interview with an Engineer. * Immediately after, one round of be
The initial interview was with HR, where they asked a set of questions on programming, databases, and other CS theory topics. The next round was a coding interview with a staff member. The question was a medium-level one on LeetCode, but I missed e
Interview Structure: * Codility test (2 rounds) * Pair programming (2 rounds) * System design (1 round) * Managerial (1 round) The interviewers were comforting and did not focus heavily on LeetCode problems. They also included me in daily meetings
A quick 30-minute HR call was scheduled to go through backgrounds. Following that, I was invited to an on-site interview. The interview process included: * One round of technical interview with an Engineer. * Immediately after, one round of be
The initial interview was with HR, where they asked a set of questions on programming, databases, and other CS theory topics. The next round was a coding interview with a staff member. The question was a medium-level one on LeetCode, but I missed e