Agoda's Software Engineer interviews typically combine a recruiter or HR screen, timed DSA coding on HackerRank, a system design discussion, and a manager conversation, with some candidates reporting the process stretching to around two months.
$130K
Avg. Base Comp
$185K
Avg. Total Comp
2-5 rounds
Typical Rounds
2 months
Process Length
Agoda's Software Engineer interviews center on fast, accurate DSA execution rather than trick questions. Candidates typically start with a recruiter or HR screen, then move to a timed HackerRank assessment or coding round. One candidate describes an online assessment of three questions in 90 minutes. Another describes easy-to-medium problems where time pressure was the main obstacle.
Candidates who advance describe live coding rounds built around arrays, strings, dynamic programming, and matrix path problems. Completing both problems in the allotted time matters as much as solving them correctly: several candidates who solved only one of two problems did not move forward.
Some candidates then have a system design or HLD round framed around Agoda-style scenarios, such as improving a booking system or designing hotel inventory availability. Interviewers have pushed into testing strategy and scalability beyond the initial design brief. A manager round focused on past projects, design decisions, scalability, or security can close the loop.
Process length and round count vary by candidate and role. Some candidates describe scheduling gaps of 15 to 20 days between rounds and a process stretching to around two months. One describes a mismatch between the round focus HR described and what the interviewer actually asked. Confirm the stack and focus of each round with your recruiter in advance.
Synthesized from 22 candidate 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 went through Agoda's interview process over a few months, and honestly, the recruitment team was impressively professional and responsive throughout. The process started with an online assessment that included multiple choice questions alongside DSA problems. The OOPs questions in the MCQ section caught me a bit off guard — they tested conceptual knowledge rather than just coding ability, so that's worth preparing for. The DSA portion of the assessment had moderate difficulty overall, and I was able to solve most of the problems, though I wasn't able to complete everything perfectly.
The first technical round focused on medium-level DSA problems, particularly around array and string manipulation. One specific question asked me to find the minimum sum pairs in an array and return all of them. The interviewer was genuinely supportive and collaborative, which made the process feel less adversarial than some other interviews I've done. The second round shifted gears entirely — it dove into core JavaScript execution details, event loops, and browser APIs. This was where things got trickier for me. The questions probed how asynchronous JavaScript actually works under the hood, not just syntax-level knowledge. They also asked me to discuss past projects and technical decisions I'd made. While I thought I'd done reasonably well on the DSA portions, I didn't ultimately receive an offer. In retrospect, I wish I'd spent more time on medium-to-hard DSA problems before going in, since those turned out to be genuinely tough to crack. The JS fundamentals round also underscored how important it is to really understand event loops and browser internals, not just be able to write async/await code.
Prep tip from this candidate
Focus heavily on medium-to-hard DSA problems involving arrays and strings before your interview, as those will likely appear in the first technical round. Additionally, prepare deeply on JavaScript execution internals — event loops, the call stack, and browser APIs — since the second round tests conceptual understanding of how JS actually works, not just practical coding ability. Don't overlook OOPs concepts in the online assessment either.
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 | |
| Count Transactions | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Employee Benefits Outreach | |
| Video Game Respawn Model | |
| Three Indexes Adding Zero | |
| Upsell Carousel | |
| Buy or Sell | |
| Client Solution Pushback | |
| 2nd Highest Salary | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Rolling Bank Transactions | |
| Monthly Customer Report | |
| Customer Orders | |
| Prime to N | |
| Random SQL Sample | |
| Top 3 Users | |
| Bagging vs Boosting | |
| Upsell Transactions | |
| Comments Histogram | |
| Scrambled Tickets |
Synthesized from candidate reports. Individual experiences may vary.
Most candidates start with a recruiter or HR screen covering background, motivation, and interest in the role, sometimes after LinkedIn outreach. This step is usually conversational. One candidate reported an unusually technical HR screen that included business-math questions like calculating growth percentages, so ask the recruiter what topics to expect before the call.
Some candidates report a timed online assessment on HackerRank. One describes three questions in 90 minutes and calls it harder than most. Accuracy and completion speed both appear to matter at this stage.
The core technical stage is typically a live HackerRank session with two problems drawn from arrays, strings, dynamic programming, or matrix path problems, sometimes run by two engineers. Several candidates report that solving one problem without completing the second was not enough to advance.
Candidates who advance may face a system design or HLD round built around Agoda-style problems, such as improving a booking system or designing hotel inventory availability. Interviewers reportedly probe beyond the initial architecture into testing and QA strategy, so be ready to defend a design from several angles.
Some candidates describe a closing manager round focused on past projects and design decisions rather than new coding problems. One candidate found this round shifted into theoretical questions on system scalability and security.
