
Agoda Product Analyst interview typically runs 4 rounds: SHL reasoning and logic test, recruiter screen, team manager interview, and an eng-thai writing test. It usually spans several rounds and emphasizes structured screening before team conversations.
$107K
Avg. Base Comp
$134K
Avg. Total Comp
4
Typical Rounds
2-4 weeks
Process Length
Our candidates report that Agoda cares less about flashy frameworks and more about whether you can make disciplined decisions under ambiguity. A recurring theme is the emphasis on structured reasoning: one candidate was screened with an SHL logic test, then pressed on hypothetical situations and a product-development analytics use case. That combination tells us they want people who can move from raw information to a defensible recommendation, not just recite metrics or buzzwords.
We also see a strong signal that communication is part of the job, not an afterthought. One experience included an eng-thai email-writing exercise to customer scenarios, which suggests Agoda is looking for analysts who can translate analysis into clear, usable language for both internal partners and customers. In the team conversation, the questions felt more like judgment checks than technical traps, so what tends to matter is whether your examples sound practical, specific, and grounded in real tradeoffs.
The non-obvious make-or-break factor here is how concrete your answers are. Multiple candidates noted that vague opinions didn’t land well, while data-backed responses did. We’ve seen the strongest candidates frame their thinking with a crisp situation, a clear decision path, and an outcome that shows they understand product impact. In other words, Agoda seems to reward analysts who can think like operators and communicate like business partners.
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.
Agoda uses a 50:50 interview structure where the first half focuses on your career history and the second half is a case study, but my experience was frustrating despite the questions themselves being straightforward. The interviewer asked me how I'd run an A/B test on a data aggregation system I'd managed. I explained that A/B testing didn't make sense for that particular system since there was no customer behavior or unknown variable to experiment on. He didn't understand my point and instead made assumptions about my own work that weren't accurate—claiming two metrics had to be a trade-off when they didn't—then gave me feedback that I was a poor performer for not knowing his false assumption about my experience.
The bigger issue was his communication style. He kept interrupting me mid-sentence, latching onto the first word I said without letting me finish my thoughts. When I started answering a question about what KPIs to track for commission income, I wanted to discuss both total commission volume and commission per booking, but he cut me off right after I mentioned the first metric and told me that was wrong. On the case study, he presented an incomplete metric funnel and said 'the top is same' without context. Only after the fact did I realize he meant the starting point was identical across both scenarios, but he never actually showed that top row in the funnel. The vagueness combined with his unwillingness to listen made an otherwise manageable technical discussion feel adversarial.
Prep tip from this candidate
The 50:50 career and case study format is standard at Agoda, but be cautious if your interviewer doesn't seem engaged in understanding your actual context—push back politely and ask clarifying questions if they make assumptions about your experience. For case studies, if the framing seems incomplete or unclear, ask explicitly for the full picture before diving in, rather than trying to infer what they mean.
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.
| Question | |
|---|---|
| Decreasing Comments | |
| Experiment Validity | |
| P-value to a Layman | |
| Google Maps Improvement | |
| Hurdles In Data Projects | |
| Random Seed Function | |
| Causal Email Journey | |
| Flipping 576 Times | |
| Xgboost vs Random Forest | |
| Lasso vs Ridge | |
| Free Cancellation Incentives | |
| Booking Value Tradeoff | |
| Count Transactions | |
| Video Game Respawn Model | |
| Upsell Carousel | |
| Client Solution Pushback | |
| Reward Experiment | |
| Marketing Dollar Efficiency | |
| Approximate Ad Views | |
| Regularization and Validation | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Comments Histogram | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Subscription Overlap | |
| Top Three Salaries | |
| Upsell Transactions | |
| Closest SAT Scores |
Synthesized from candidate reports. Individual experiences may vary.
The process starts with a structured aptitude screen focused on reasoning and logic. This appears to be a gatekeeper before candidates move on to conversations with the team.
A recruiter call covers the basics: your background, why you are interested in the Product Analyst role, why Agoda, and why you want to change careers. The conversation is introductory and helps assess motivation and fit.
Some candidates also complete a written communication exercise where they draft customer emails in English and Thai. This round emphasizes clear, professional communication in a customer-facing context.
The next round is with the team manager and focuses on fit, judgment, and how you approach product and analytics scenarios. Questions are often hypothetical and require data-backed, concrete answers, including how you would handle product development use cases.