My Agoda Interview Journey: A Candid Reflection
Not every journey ends with an offer. Some lead to clarity, growth, and a renewed sense of direction.
While I didn’t receive an offer, the decision came down to headcount constraints, the process turned out to be one of the most technically enriching and introspective experiences of my career.
Over the past few weeks, I had the opportunity to interview for a Senior Software Engineer — Front End (Bangkok) role at Agoda. It was a well structured, multi-stage process that pushed me to reflect deeply on how I approach frontend architecture, collaboration, scalability, and system design.
In this post, I’ll walk through how I prepared, what the experience looked like, and what I took away especially for anyone navigating similar interviews that blend frontend depth with engineering leadership.
Why Agoda?
As someone who thrives in fast paced, product driven environments, Agoda stood out for several reasons:
- A strong engineering culture with high ownership
- Focus on performance, scalability, and experimentation
- Opportunities to build systems used globally
- Emphasis on technical leadership and cross-functional collaboration
The role itself wasn’t just about building UIs it involved architectural thinking, mentorship, and platform-level ownership. It aligned naturally with the direction I’ve taken in my recent work, especially leading efforts like Staff Connect, a modular real-time hotel management platform.
How I Prepared
I treated this process as more than just a hiring evaluation it was a chance to challenge myself and sharpen how I think about building at scale. My preparation focused on:
- Deepening architectural thinking: Exploring frontend architecture as part of larger distributed systems not just isolated React components.
- Strengthening fundamentals: React concurrency (
useTransition,useDeferredValue), testing strategies, performance profiling, and system trade-offs. - Sharpening problem-solving: Revisiting DSA topics with an eye for clarity, structure, and real world applications especially arrays, strings, recursion, dynamic programming and graphs.
- Revisiting past work: Drawing insights from leading Staff Connect where we focused on scalable configs, shared utilities, developer experience, and live data sync using Firebase and GraphQL.
Most importantly, I approached each round as a conversation, not a checkpoint. That mindset helped me stay curious and present throughout the process.
The Interview Process
The process was thorough and thoughtfully paced:
- Online Assessment : Emphasized structured problem solving.
- Recruiter Call : Covered expectations, motivations, and fit.
- Coding Interview : Tested clarity of thought and algorithmic strength.
- Platform Interview : Dived into architectural decision making, tradeoffs, and system performance.
- Preliminary Call : Discussed relocation, timelines, and compensation alignment.
- Architecture + Culture Fit : Explored HLD, LLD, team collaboration, and technical leadership.
Each conversation was engaging, with room to discuss my experiences and ask questions about Agoda’s engineering direction.
Why It Didn’t Work Out
The team ultimately couldn’t move forward due to current headcount constraints.
Get Ram Krishnan’s stories in your inbox
Join Medium for free to get updates from this writer.
And while that was disappointing, it reaffirmed something important:
Not all rejections are reflections of capability. Sometimes, they come down to timing and business constraints.
I walked away knowing I gave it everything and that matters more than anything.
What I Took Away
Growth : I became sharper in how I approach architecture, performance, and frontend thinking at scale.
Validation : I received strong feedback across several rounds and held my own in deeply technical conversations.
Gratitude : To everyone I met from recruiters to engineering managers thank you for the transparency and respect throughout.
To Future Teams
If you’re looking for someone who brings:
- Deep frontend architecture and system level thinking
- Proven leadership in complex product environments
- A commitment to mentorship, collaboration, and technical ownership
Final Thought
This experience reaffirmed that growth happens through the process, not just the outcome. To the Agoda team thank you for the opportunity. It was an incredibly thoughtful journey, and I’m grateful to have been a part of it.
***************************************************************************
👋
Hey, I’m Ram krishnan, I love breaking down complex engineering concepts into clear, visual stories. From frontend systems to developer tooling, I write about what makes engineering efficient, elegant, and enjoyable.
