Agoda Software Engineer interview typically runs 3 rounds: HR call, coding round, platform interview. The process usually takes around 2 months, with long gaps between rounds and some scheduling delays.
$61K
Avg. Base Comp
$70K
Avg. Total Comp
3-4
Typical Rounds
2 months
Process Length
Our candidates report that Agoda is less about a single polished interview style and more about whether you can stay aligned with a process that can feel surprisingly inconsistent. The strongest signal from this experience is that the company does care about solid algorithmic thinking under pressure, but the bar is not just solving the first problem — it’s whether you can keep moving when the clock gets tight and the prompt is unusually specific. The examples shared here, from plane-shot-down counting to pivot elements in an unsorted array, suggest they favor practical problem decomposition over flashy theory.
What makes Agoda tricky is the mismatch risk. A recurring theme is that the expected stack or depth of discussion may not match what the interviewer actually explores, especially when the candidate assumes a backend conversation and gets pulled into frontend-flavored JavaScript topics instead. We’ve seen that this can become the make-or-break factor: not because the questions are impossibly hard, but because clarifying scope early matters more here than at many companies. The long gaps between rounds also seem to amplify frustration, so candidates who stay flexible and keep checking assumptions tend to navigate the process better than those who rely on a clean, linear experience.
Synthetized from 1 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Agoda process.
I got pulled into Agoda through a recruiter on LinkedIn, and the process dragged on much longer than I expected. The first step was an HR call, then a coding round on HackerRank that felt like easy-to-medium DSA. I cleared the first problem, but I couldn’t finish the second one in time. The questions were pretty specific: one was about how many airplanes can be shot down before any plane lands, and the other was to find all pivot elements in an unsorted array, where the pivot has everything smaller on the left and everything larger on the right. That round was fair, but the time pressure was real.
What surprised me more was how slow everything became after that. They had a scheduling website where I had to submit availability, and there were usually 15–20 days between rounds because they often didn’t have an interviewer ready. The whole process stretched to around two months, and for some people it went even longer. In my case, the next round was supposed to be a platform interview, but there was a mismatch between what HR said and what the interviewer actually wanted. I was expecting a backend-oriented discussion, but the senior engineer mostly asked about frontend-style JavaScript topics like templates and things he knew from his own 4–5 years of experience. I raised the mismatch with HR, waited about 20 days, and then they asked me to apply again and rejected me. The process felt disorganized, and the long gaps made it frustrating. My takeaway is to be ready for medium DSA under time pressure, but also to clarify the exact stack and round focus before you invest too much time.
Prep tip from this candidate
Practice medium DSA problems with a timer, especially array/pivot-style questions and counting paths in a matrix with obstacles. Also confirm the exact stack and round focus early, because the platform round may lean heavily into the interviewer’s own JavaScript background rather than the role you expected.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Agoda
Explain what a p-value is to someone who is not technical
| Question | |
|---|---|
| Cross-Region Inventory Sync | |
| Buy or Sell | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Customer Orders | |
| Random SQL Sample | |
| Rolling Bank Transactions | |
| Merge Sorted Lists | |
| Prime to N | |
| Upsell Transactions | |
| Comments Histogram | |
| Closest SAT Scores | |
| Monthly Customer Report | |
| Raining in Seattle | |
| Permutation Palindrome | |
| Find the Missing Number | |
| Delivery Estimate Model | |
| Over 100 Dollars | |
| Find the First Non-Repeating Character in a String | |
| Scrambled Tickets | |
| Minimum Change | |
| Google Maps Improvement | |
| Rectangle Overlap | |
| Nearest Common Ancestor | |
| Address Schema | |
| Download Facts | |
| Paired Products |
Synthesized from candidate reports. Individual experiences may vary.
The process started after a recruiter reached out on LinkedIn, followed by an initial HR call. This stage was used to introduce the role and begin coordinating the rest of the interview loop.
Candidates completed a HackerRank coding round with easy-to-medium DSA questions under time pressure. In the reported experience, the problems included counting how many airplanes could be shot down before any plane lands and finding all pivot elements in an unsorted array.
The next round was described as a platform interview with a senior engineer, but the focus did not fully match what HR had set expectations for. The discussion leaned toward frontend-style JavaScript topics such as templates rather than the expected backend-oriented stack.
After the mismatch was raised with HR, there was a long delay before the candidate was asked to apply again and then rejected. The overall process was slow, with gaps of roughly 15–20 days between stages and a total timeline of around two months.