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.
Synthesized from 1 candidate report 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.
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
Find the maximum profit from at most two stock buy/sell transactions
| Question | |
|---|---|
| P-value to a Layman | |
| Google Maps Improvement | |
| Hurdles In Data Projects | |
| Target Indices | |
| Cross-Region Inventory Sync | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Employee Benefits Outreach | |
| Video Game Respawn Model | |
| Three Indexes Adding Zero | |
| Upsell Carousel | |
| Buy or Sell | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Monthly Customer Report | |
| Random SQL Sample | |
| Prime to N | |
| Top 3 Users | |
| Bagging vs Boosting | |
| Upsell Transactions | |
| Comments Histogram | |
| Find the First Non-Repeating Character in a String | |
| Retailer Data Warehouse | |
| Raining in Seattle |
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.