Agoda Software Engineer candidates commonly report a timed HackerRank coding screen, followed by technical and design rounds. Some describe not finishing the second coding problem as the sticking point, and several describe slow scheduling.
$63K
Avg. Base Comp
$80K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Across the Agoda Software Engineer experiences, the most repeated hurdle is the timed coding round on HackerRank. Candidates describe two or three problems at easy-to-medium difficulty, and one called the online assessment harder than most, with three questions in 90 minutes. Two candidates solved only one of two problems, and one of them was not shortlisted afterward. Reported problems include how many airplanes can be shot down before any lands, pivot elements in an unsorted array, a two-sum style target problem, Meeting Rooms II, minimum sum pairs and a grid path problem with obstacles. Aim to finish every problem cleanly under a timer, and practice arrays, strings, hash maps, intervals and dynamic programming.
Later rounds vary by team and level. One candidate was asked to improve a high-level booking system design and was rejected largely for not covering testing and QA. Another was asked to design a hotel inventory availability system on a virtual whiteboard. An internship candidate's manager round turned to system scalability and security. A round on JavaScript event loops and browser APIs, a platform round that drifted into frontend topics, and OOP multiple-choice questions also appear in individual reports, so confirm the stack and round focus with your recruiter.
Process logistics are mixed. One candidate praised a professional, responsive recruiting team, while others describe gaps of 15-20 days between rounds and waits of around two months for a decision. One candidate also reports surprise business-math questions in an HR screen. Be ready to discuss past projects in depth.
Synthesized from 32 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 in expecting the problems to be the hard part, but they were mostly easy to medium. The process was three rounds of live coding, and what surprised me was that finishing the code wasn't the real bar. The interviewers wanted me to explain how I arrived at each solution, and they kept asking about my thinking as I went. Memorized answers wouldn't have carried me through.
The first problem I got was a two sum. Once I had a working version, they added complexity and asked me to extend it to a three sum. That follow-up was where the interview really tested whether I understood the approach or had just seen the pattern before. It forced me to rethink my solution instead of tweaking it.
My main advice is to narrate your reasoning from the start. Say what you're trying to do before you write it, explain your tradeoffs, and stay calm when the problem changes under you. I did not receive an offer, so treat this as a sign of how much weight the explanation carries here.
Prep tip from this candidate
Practice explaining your reasoning out loud while you code, since this process weighed the explanation as heavily as the final solution. Be ready for a two sum problem to be extended to three sum within the same round.
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 | |
|---|---|
| Google Maps Improvement | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| Target Indices | |
| Cross-Region Inventory Sync | |
| Count Transactions | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Client Solution Pushback | |
| Employee Benefits Outreach | |
| Video Game Respawn Model | |
| Three Indexes Adding Zero | |
| Upsell Carousel | |
| Buy or Sell | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Random SQL Sample | |
| Top 3 Users | |
| Rolling Bank Transactions | |
| Monthly Customer Report | |
| Upsell Transactions | |
| Longest Streak Users | |
| Customer Orders | |
| Scrambled Tickets | |
| Prime to N | |
| Bagging vs Boosting |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter or HR conversation, often after a LinkedIn approach. It typically covers background and role fit. One candidate reports unexpected business-math questions, so it may help to ask the recruiter which topics the call and later rounds will cover.
Candidates commonly report a HackerRank coding step with two or three LeetCode-style problems at easy-to-medium difficulty. One described three questions in 90 minutes. Another assessment also included OOP multiple-choice questions. Two candidates did not finish the second of two problems.
Reported follow-up rounds include more data structures and algorithms, discussion of past projects, and stack-specific questions such as JavaScript event loops and browser APIs. One candidate's platform round focused on frontend topics rather than the expected backend discussion, so it is worth confirming the focus in advance.
Some candidates report design prompts tied to Agoda's domain, including a hotel inventory availability system and improving a high-level booking system design. One report says missing testing and QA coverage led to rejection. An internship candidate faced scalability and security questions from a manager. Prepare trade-offs and validation strategy.
Candidates who progress report a technical discussion with an engineering manager or a hiring manager conversation. Timing varies, with reports of 15-20 days between rounds and around two months before a decision.
