Editorial practice groupings, not verified official interview questions or endorsements.
Public Agoda prep guide
Prepare with five practice prompts shaped by six public frontend accounts from 2025 and 2026, most of them Bangkok relocation loops interviewed from India, and by Agoda's own description of its four rounds: a hotel search page frontend designed from scratch for a million users and several teams, a scalable architecture for a travel booking site, a React and TypeScript take-home on stock data, a one-hour web-fundamentals round that runs from CDN caching to CSRF and Core Web Vitals, and a JavaScript implementation round beside a HackerRank coding hour.
This guide uses public, self-reported interview accounts and Agoda's published careers and engineering pages to create realistic constraints. It does not claim access to private interview material, a fixed interview format, or the stack of every Agoda team.
Study priorities
The public accounts converge on a loop run remotely on HackerRank with about a week between rounds: a coding hour with two easy-to-medium problems and verbal questions on test cases and pull requests, a Frontend Platform hour, a preliminary call in which the level is set, an architecture hour on a product such as a hotel search page, and a culture-fit conversation with an engineering manager. Agoda's own interview-process page lists the same four rounds, Coding, Platform, System Design and Agoda Culture Fit, and its interviewer's guide says the Platform round typically asks candidates to implement something related to Agoda and often includes reviewing, fixing and improving a given code snippet.
The round that sets the level is the Platform hour, and its content varies by interviewer: a 2026 Senior candidate got a web-fundamentals question-and-answer hour with no code, a 2025 Staff candidate got a JavaScript implementation grown out of a resume item, and a 2025 Senior candidate was told to expect component reusability, state management, handling API data and rendering performance. Each prompt below starts with the clarifying questions a strong candidate asks, then the behaviours a strong answer covers, then the miss that usually ends the round.
Reported interview process
Agoda's interview-process page describes a HackerRank online test as the coding assessment and four rounds: Coding, Platform, System Design and Agoda Culture Fit, with a decision typically within two weeks of the last round. Front-end accounts from Bangkok relocation loops in 2025 and 2026 describe a recruiter prep call, a 60-minute coding interview, a Frontend Platform interview and an architecture interview, all on HackerRank about a week apart, a preliminary call in which the level is set, a culture-fit conversation with an engineering manager, and the manager presenting the offer.
The careers pages could only be read from archive captures. The Platform round's content varies by interviewer: a pure question-and-answer hour, a JavaScript implementation or an architecture discussion. Rejections after clearing the technical rounds are reported, over headcount or without a managerial round. Gurgaon loops differ by team; Manila and Bangalore rest on too little to state a loop. On 2026-10-21 the front-end postings were Staff, Lead and Manager level, all Bangkok-based with relocation. Sources last checked Oct 2026.
| Stage | What happens | Who | Evidence |
|---|---|---|---|
| Recruiter prep call | 15 to 30 minutes on background, notice period, relocation and expectations. | Front-end engineers, Senior and Staff | Official page and 3 reports |
| HackerRank assessment | A HackerRank online test to complete within a timeframe, as the official page describes it; one 2025 Senior front-end account opened with an online assessment, while the other Senior and Staff accounts had none. | Some loops | Official page and one report |
| Coding interview | 60 minutes on HackerRank with an engineer: two easy-to-medium DSA problems in JavaScript, then verbal questions on test cases and the pull-request process. Practice: DSA for frontend loops | Front-end engineers, Senior and Staff | Official page and 4 reports |
| Frontend Platform interview | 60 minutes on HackerRank: a web-fundamentals question-and-answer hour, a JavaScript implementation grown from the resume, or a discussion of component reuse, state, API data and rendering performance; the prep guide promises a code snippet to improve. Practice: Cookie vs sessionStorage vs localStorage | Front-end engineers, Senior and Staff | Official page and 5 reports |
| Preliminary call | 30 minutes with the recruiter on compensation, relocation and feedback; the level is set here (a Staff applicant was moved to Senior, strong Senior candidates to the Staff track). | Front-end engineers, Senior and Staff | 6 public reports, 2025–2026 |
| Architecture interview | 60 minutes: a frontend-flavoured product design such as a hotel search page or a booking app, with no diagram expected; the Staff track adds a BE Platform hour on a hotel booking system. Practice: Frontend system design blueprint | All; the extra hour on the Staff track | Official page and 4 reports |
| Culture fit | 60 minutes with an engineering manager; behavioural questions, which the official interview guide frames with the CAR method (Context, Action, Results). Practice: Behavioral interview guide | Front-end engineers, Senior and Staff | Official page and 3 reports |
| Decision and offer | The hiring manager presents the offer; the official target is a decision within two weeks of the last round, or under 30 days overall. | Candidates who pass | Official page and one report |
Team-specific: three accounts with different stage orders. Interviewers may sit in Bangkok, and one 2026 account was rejected in Gurgaon's second round before an offer from a Bangkok loop after the six-month cooling period. On 2026-10-21 the board listed no Gurugram front-end-titled role.
| Stage | What happens | Who | Evidence |
|---|---|---|---|
| Online assessment or take-home | HTML/CSS and JavaScript questions in an online assessment, or a take-home such as a React and TypeScript stock dashboard listed as a 120-minute online coding interview. | Some loops | 2 public reports, 2025 |
| HR screen | A short call before the technical rounds. | Some loops | One public report, 2025 |
| Coding round | 60 minutes of JavaScript or DSA problems, on HackerRank in one account; another pairs a substring problem with a debounce utility. Practice: Debounce | Front-end and full-stack engineers | 3 public reports, 2024–2025 |
| Platform or architecture round | JavaScript depth (hoisting, class behaviour, SSR versus CSR, atomic design, testing), an hour of frontend architecture for a travel booking site, or a system architecture with a frontend that integrates backend API calls. Practice: SSR and hydration in React | Front-end and full-stack engineers | 3 public reports, 2024–2025 |
| HR salary and relocation call | Compensation and relocation before a decision. | Some loops | One public report, 2025 |
| Managerial or technical-strategy round | A managerial round in the 2024 offer account, a 60-minute technical-strategy round in the 2025 Code360 account, and a rejection without a managerial round in the 2025 Blind account. Practice: Behavioral interview guide | Some loops | 3 public reports, 2024–2025 |
Role lenses
These are preparation lenses based on Agoda's own description of its front-end work, not claimed team assignments. Choose the lens closest to the role and keep the reasoning framework-neutral.
Agoda's interview-process page describes TypeScript with React and Redux, Rspack and Vite for bundling, and micro-front-end and cross-platform solutions; the reported architecture rounds asked for a hotel search page and a travel booking site.
Practice focus: Search and filter state that survives reloads and shared links, rendering strategy per page type, CDN caching with explicit invalidation, and a funnel from search to payment that can be measured.
The interviewer's guide says front-end developers also contribute to front-facing API services, and the reported Platform and BE Platform rounds asked about API data handling, token storage, CSRF and XSS, performance bottlenecks and production debugging.
Practice focus: Typed data at the API boundary, session and token placement with its security trade-offs, request cancellation and retries, and the metrics you would watch after a deploy.
Representative practice prompts
For each prompt, clarify the contract, explain ownership and trade-offs, implement or diagram the smallest credible slice, and test the failure cases. Each prompt links to the public report it is modelled on and to a practice page.
Prompt 1
Given a wireframe with date, city and guest inputs on top, filters on the left and result cards on the right, design the frontend: scalable, maintainable and observable, with a real-time chat integration, able to support a million users, multiple teams and fast, independent deploys of features. No diagram is expected; talk through the decisions and the follow-ups: micro-frontends, monorepo versus multi-repo, framework and bundler choice, where the filter and input state lives and in which components, component breakdown, testing architecture and monitoring.
Practice version modelled on a reported round: Public report: LeetCode senior frontend engineer loop, Bangkok, July 2026
Decomposition of a product page into ownable units, state placement for inputs and filters, deploy boundaries between teams, and whether you can name what you would measure once it is in production.
Common miss: Drawing the three visual areas as components and stopping there, with no answer for who deploys what, where the filter state lives, or how a regression would be noticed.
Work through the real-time search with debounce and caching case (Premium)Prompt 2
Design the frontend architecture for a travel booking website similar to Agoda: it must handle high traffic, support micro-frontends, render SEO-friendly pages with SSR or SSG, and include performance optimisations. Say which pages are server-rendered, how the micro-frontends share a shell, and what you cache where.
Practice version modelled on a reported round: Public report: Code360 frontend engineer loop, Gurgaon, May 2025
Rendering-strategy judgment per page type, the real cost of micro-frontends, caching layers from the CDN to the browser, and performance reasoning tied to measurable metrics rather than to a list of features.
Common miss: Listing SSR, micro-frontends and a CDN as features without saying which page gets which, so the interviewer cannot tell whether you understand the cost of each.
Work through the car rental booking frontend case (Premium)Prompt 3
Build a React and TypeScript single-page application that fetches stock data from a given API and shows it in paginated tables with summary statistics (the lowest value, the average open price for one year, the longest streak where close is above open), with attention to performance, modular architecture and clean code. In the 60-minute follow-up the same account was asked for Longest Substring Without Repeating Characters and to 'Create a debounced utility function in JavaScript.'
Practice version modelled on a reported round: Public report: Code360 frontend engineer loop, Gurgaon, May 2025
Request-state handling, typed data at the API boundary, derived statistics computed once from the full dataset, pagination that stays correct when the data changes, and whether you can explain each module's job when asked.
Common miss: Computing the statistics inside the table's render from the current page, so the lowest value changes when the user pages, and a debounce that clears no timer and so still fires the stale call.
Practice the fetch-and-render exercise (free)Prompt 4
A one-hour question-and-answer round, as a 2026 account reported it: techniques to optimise page landing speed; SSG, SSR, CSR and ISR; the core entities of a hotel booking page; what to cache in a CDN and how updates reach it; the ways to store data on the client and where to store the authentication token with the security implications of each; what CSRF and XSS are and how to mitigate them; the ways to hold state in React; where to store the selected filters on a hotel booking page, in state or in query params; how to measure page performance with Core Web Vitals; how to track a funnel from search to view to book to pay; testing strategies with an example of each; and how to manage test failures that are not caused by your own code.
Practice version modelled on a reported round: Public report: LeetCode senior frontend engineer loop, Bangkok, July 2026
Breadth across the web platform with precise answers, trade-off reasoning for storage and rendering choices, security basics stated correctly, and whether you can tie performance and testing to how a product team works.
Common miss: Answering localStorage for the token without naming the XSS exposure, or describing CSRF as a variant of XSS; the round checks whether the trade-off is understood, not whether the term is recognised.
Review cookies versus sessionStorage versus localStorage (free)Prompt 5
Two rounds reported from Bangkok loops. First, a JavaScript implementation round grown from the resume: a 2025 Staff candidate was asked to implement a pipeline function and then extend it so asynchronous steps run under a concurrency limit, in 40 to 50 minutes, followed by 10 to 15 minutes of behavioural questions. Second, the coding hour on HackerRank: two easy-to-medium problems (a 2026 account names Rank Transform of an Array and Climbing Stairs with 1, 2 or 3 steps) with complexity analysis, then verbal questions on which test cases you would write and what to check before raising a pull request.
Practice version modelled on a reported round: Public report: LeetCode staff frontend engineer loop, Bangkok, February 2025
Function composition and closures, promise sequencing with a concurrency cap, clean JavaScript under pair programming, complexity analysis, and whether you can talk about testing and code review as everyday work.
Common miss: An async limit built from a counter and polling with setTimeout instead of promise settlement, and a resume that lists a utility you cannot write on request; the 2025 account's own advice was not to mention anything that can be turned into a JavaScript function you have not already prepared.
Practice the debounce utility (free)Public mini walkthrough
Treat this as a representative exercise, not a description of the reported one. Work from the requirements toward the deploy boundaries, and say each decision out loud; the reported round expected no diagram.
Name the three input groups, the filters, the result cards, the chat integration and the non-functional targets: a million users, several teams, fast independent deploys, observability.
Put the search inputs and the selected filters in the URL as the source of truth, derive component state from it, and name the single writer for each piece.
A shell that owns routing, layout, auth and the design system; search, filters and results as units with a typed contract between them; shared dependencies pinned once.
One unit per team, built with a bundler that supports runtime composition, released on its own cadence with a contract test the shell runs before it mounts the unit.
Core Web Vitals per route, error rates per unit, and a search-to-view-to-book funnel keyed by a search id, so a regression points to one deploy.
A shared link with stale filters, a slow results unit while the inputs render, a filter change during an in-flight request, and a unit that fails to load.
Actionable preparation
Every day ends with code, a test, a design artifact, or a question you can use in the real process.
Web fundamentals: client storage and token placement, CSRF versus XSS, HTTP and CDN caching, SSG, SSR, CSR and ISR per page type, Core Web Vitals.
Deliverable: A one-page answer sheet with a recommendation and a trade-off for each topic.
Utility functions: a debounce with cancel, a pipeline in synchronous and asynchronous forms, an async limit that preserves order.
Deliverable: Three implementations with tests you can retype from memory.
The coding hour: two easy-to-medium problems in JavaScript against a timer, then the test cases and the pull-request checklist said out loud.
Deliverable: A time log with the complexity stated for each solution.
The take-home shape: a typed fetch with loading, error and empty states, a paginated table, summary statistics in a pure module.
Deliverable: A small dashboard with one test per statistic and per request state.
Architecture: the hotel search page and the travel booking site; rendering per page, micro-frontend boundaries, caching layers, observability.
Deliverable: Two one-page designs with the reported follow-up questions answered in writing.
Behavioural: stories about conflict, a production incident, deadlines versus quality, mentoring and disagreeing with product, told as context, action and result.
Deliverable: Six stories with a measurable result, mapped to the culture-fit and technical-strategy topics the accounts list.
Mock loop: one coding hour, one Platform hour and one architecture hour on a shared editor, each narrated.
Deliverable: A list of the questions you will ask the recruiter about the assessment, the Staff track, the tools and the timing.
Preparation FAQ
No. They are FrontendAtlas practice versions modelled on round types and prompts described in public, self-reported accounts and on Agoda's own process pages. The wording, the data and the test cases are ours.
The two Bangkok accounts that describe the tooling say so: the July 2026 account reports that all of its rounds were online on HackerRank with a week between them, and the September 2025 offer account says the Frontend Platform interview was also conducted through HackerRank. Agoda's process page describes a HackerRank online test as the coding assessment. One Gurgaon account names HackerRank for its coding round only, and the Code360 account names no tool, so confirm the tool for each round with the recruiter.
Agoda's process page lists it as the second of four rounds, after Coding and before System Design and Culture Fit. The interviewer's guide on the Agoda Engineering blog says the Platform round typically asks candidates to implement something related to Agoda and often includes reviewing, fixing and improving a given code snippet, playing the role of a lint tool. The frontend accounts describe three shapes: a web-fundamentals question-and-answer hour with no code in July 2026, a JavaScript implementation grown out of a resume item followed by behavioural questions in February 2025, and a discussion of component reusability, state management, API data handling and rendering performance in September 2025. Prepare for all three.
In the accounts used here the level is set after the Platform round. The July 2026 candidate applied for Staff and was moved to Senior after the second round; the September 2025 Senior candidate was moved to the Staff track and got an extra hour, a BE Platform interview on a hotel booking system; a commenter on the June 2025 Blind thread describes the same path: Staff consideration after the platform round, then one architecture round, then culture fit. Ask the recruiter which track you are on before the architecture round.
The accounts say yes, at easy-to-medium level and in JavaScript. The July 2026 Senior loop opened with Rank Transform of an Array and Climbing Stairs with 1, 2 or 3 steps, with complexity analysis; the February 2025 Staff loop had two medium problems one after the other with pair programming and feedback corrections; a September 2025 full-stack account describes two medium problems on HackerRank finished in 35 minutes. Some loops also open with a HackerRank assessment. The interviewer's guide says the Coding round looks for testing skills, critical and systematic thinking, code efficiency and readability, and computer science knowledge.
Free public practice
These public pages cover the utility, request-state, security, caching, rendering and testing skills used by the practice prompts. They are supporting drills, not claimed Agoda questions.
Public interview reports and official context
These links support the public context used by the guide. Their notes state what each source can and cannot establish about preparation.
One self-reported Bangkok relocation loop interviewed in July 2026 for a Staff role, moved to Senior after the second round, without an offer. It establishes three HackerRank rounds a week apart, the two easy problems with test-case and pull-request questions, the full question list of the web-fundamentals hour and the hotel search page architecture round; it cannot establish the current format or what other interviewers ask in the Platform round.
One self-reported Gurgaon loop from May to June 2025 with every round marked Cleared and a rejection as the outcome. It establishes the Stock Analyzer Dashboard take-home, the debounce follow-up, the travel booking architecture hour and the technical-strategy round; the page names no tool for the rounds, and its experience band disagrees with the account's eight-plus years.
One self-reported Bangkok loop from August to September 2025 that ended in an offer, read through the author's feed. It establishes the recruiter's seven-step list with durations, the Platform interview on HackerRank, the move to the Staff track with a BE Platform hour and the manager presenting the offer; it lists topics, not questions.
One self-reported Staff Frontend loop in Bangkok from February 2025 that ended in selection. It establishes two medium problems in JavaScript, the pipeline function extended to an async limit, the doctor appointment booking design and the advice not to list unprepared utilities on the resume; it cannot establish the current format.
One self-reported Gurgaon loop from June 2025 that ended with a rejection and no managerial round. It establishes the assessment with 8 HTML/CSS questions and 2 JavaScript problems, the HackerRank coding round and the platform topics; a commenter, not the poster, adds that the recruiters and interviewers were in Bangkok and describes the Staff track.
One self-reported Staff loop from July 2025 by a Bangalore candidate interviewing for Thailand relocation, not selected. It establishes a phone screen on JavaScript basics, promises and a sliding-window problem, a DSA and JavaScript round and a live HackerRank stack problem; it ends earlier in the loop than the Bangkok accounts.
Official page describing a HackerRank online test as the coding assessment, four rounds (Coding, Platform, System Design and Agoda Culture Fit), a final decision typically within two weeks of the last round, and the front-end stack of TypeScript with React and Redux, Rspack and Vite. The live site blocks automated reads, so it was read from an archive capture of April 2026; it names no interview questions.
An interviewer's guide on the Agoda Engineering blog. It states what the Coding round looks for and that the Platform round typically asks candidates to implement something related to Agoda and often includes reviewing, fixing and improving a code snippet; it is from 2023 and names no questions.
Published by Agoda
Agoda publishes these pages itself. They describe the process and expectations in the company's own words; they do not list interview questions, and FrontendAtlas is not affiliated with Agoda.
| Page | What it covers | Checked |
|---|---|---|
| How we hire: the Tech team interview process | A HackerRank online test as the coding assessment, the four rounds the Tech interview process typically includes (Coding, Platform, System Design and Agoda Culture Fit), a final decision typically within two weeks of the last interview round, and the front-end stack (TypeScript with React and Redux, Rspack and Vite for bundling, micro-front-end and cross-platform solutions). | Oct 2026 |
| Interview guide | The CAR method (Context, Action, Results) used in interviews, two rounds of video interviews before the final stages for most candidates, and the parts of the process (live system design, technical Q&A and behavioural interviews) that must be completed without AI unless the candidate is asked to use it. | Oct 2026 |
| Preparing for an interview at Agoda (Agoda Engineering) | A 2023 interviewer's guide to the Coding round (testing skills, critical and systematic thinking, code efficiency and readability, computer science knowledge) and the Platform round (implementing something related to Agoda, and reviewing, fixing and improving a given code snippet as a lint tool would). | Oct 2026 |
Full company practice
This public guide is complete enough to plan a focused week. Premium unlocks the real-time search with debounce and caching case, the car rental booking frontend case, the React paginated data table drill and the wider premium library of coding, concept and system-design practice.