Sane working hours, partly due to SCRUM and "sustainable pace".
A good work environment.
Really sharp people.
A good ratio of product managers and QA to developers.
Great market placement.
Good work/life balance.
Guidewire has a substantial proprietary technology stack. Some of what you learn won't transfer out. Low turnover means the injection of new ideas is slower than at some places.
Don't let one team get too far ahead of others. Maybe rotate people between teams more often. Don't screw up a good thing.
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