Happy to share a recent interview journey that pushed me to reflect on my strengths, sharpen my technical thinking, and revisit my architectural decisions.

Round 1 – Codility (DSA) Started with an online coding round. I solved a data structures and algorithms problem — it was time-bound and tested logical thinking under pressure.

Round 2 – CodeLive (DSA + Communication) Faced a similar DSA problem, but this time with an interviewer watching me code live. The key here was not just solving it, but explaining my approach, trade-offs, and edge case handling clearly and confidently.

Rounds 3 & 4 – Onsite (System Design) This was the most exciting part — I was given a system failure scenario and asked to identify weak points and propose improvements. Another discussion focused on how to add intelligence to a service — an interesting blend of system thinking and creativity.

Round 5 – Onsite – Managerial Round A reflective round — I spoke about my strengths, areas I'm actively working on, and walked through the architecture of my current project. I also answered, “Why Guidewire?” — and got a chance to align my goals with the company’s mission.

Round 6 – Final Round with Director Focused more on my CI/CD practices, understanding of deployment pipelines, and where I see myself contributing. I also discussed my tech interests and how they can shape impact.

Every round was thoughtfully structured — not just to test technical depth, but to understand how I solve, communicate, and grow.

DSA problem - Given a list of maintenance times scheduled regularly for every week, identify if a slot availability of x minutes can be fit in.