agoda logo
Agoda· Staff Software Engineer

Agoda Staff Software Engineer Interview Experience

Posted
25 May 2026
196 reads

Summary

I interviewed for a Staff Software Engineer role at Agoda; I cleared the coding round but could not pass the system design/platform round.

How it went

Recently interviewed with Agoda for Staff Software Engineer role. Could not clear the system design/platform round. Sharing the questions and discussion topics for others preparing for senior backend/platform roles.

Round 1 - Coding Round (60 mins)

Question 1 - Simple Chemical Formula Evaluation

Write a function:

calculateWeight(String formula)

Requirements:

  • Supported elements:
    • C -> 12
    • H -> 1
    • O -> 8
  • No parentheses
  • Single-digit multipliers only

Example:

Input: CH4

Output: 16

Explanation: C = 12 H4 = 1 x 4 = 4 Total = 16

Question 2 - Complex Chemical Formula Evaluation

Enhancement over previous problem:

  • Nested parentheses supported
  • Multipliers after parentheses apply to entire group

Examples:

Input: H(CH4)2

Output: 33

Input: ((CH4))

Output: 16

Main concepts:

  • Stack
  • Parsing
  • Recursive/group evaluation

Round 2 - Platform/System Design Round (60 mins)

Architecture Problem

Scenario: A booking platform needs to expose APIs for external suppliers to fetch booking information.

Requirements:

  • Support 10-20 suppliers
  • Suppliers fetch bookings using different filters:
    • last 5 minutes
    • last 2 hours
    • last 1 day
    • next 7 days check-ins
    • next 30 days check-ins
  • Peak traffic:
    • ~100 requests/minute

Existing proposal from team:

  • External Booking API calls internal Booking API
  • New endpoint fetches bookings by supplier ID and date range

Main discussion areas:

  • Why external APIs should not directly hit core booking service
  • Read replicas vs OLTP DB
  • CDC/event streaming
  • Pagination and cursor-based APIs
  • Incremental sync tokens
  • Rate limiting/throttling
  • Caching strategy
  • Security/authentication
  • Supplier isolation

Architecture topics interviewer focused on:

  • Scalability
  • Loose coupling
  • External API design
  • Data synchronization
  • Production readiness

Code Review Discussion

Second part of round involved reviewing Java code for supplier booking query API.

Focus areas:

  • Clean code principles
  • Single Responsibility Principle
  • Dependency Injection
  • Removing duplicate cache logic
  • Enum-based behavior encapsulation
  • Validation cleanup
  • Exception handling
  • Logging practices
  • Cache key design
  • Separation of mapper responsibilities

Interview was heavily focused on:

  • Backend architecture thinking
  • Maintainability
  • Real-world production systems
  • Senior/staff-level engineering judgment

Hope this helps others preparing for Agoda platform/backend interviews.

Questions asked (3)

  1. 01

    Simple Chemical Formula Evaluation

    Data Structures & Algorithms

    Write a function calculateWeight(String formula) that computes the molecular weight of a chemical formula. Supported elements: C = 12, H = 1, O = 8. The formula contains no parentheses and only single‑digit multipliers. Example: Input: CH4 Output: 16 (C = 12, H4 = 1×4 = 4, total = 16).

  2. 02

    Complex Chemical Formula Evaluation

    Data Structures & Algorithms

    Extend the previous problem to support nested parentheses and multipliers that apply to the entire group. Example 1: Input H(CH4)2 Output 33. Example 2: Input ((CH4)) Output 16. Required concepts include stack‑based parsing and recursive/group evaluation.

  3. 03

    Booking Platform API Design

    System Design

    Design a booking platform API that external suppliers can use to fetch booking information. Requirements: support 10‑20 suppliers; suppliers may filter bookings by last 5 minutes, last 2 hours, last 1 day, next 7 days check‑ins, next 30 days check‑ins; peak traffic ~100 requests/minute. Discuss architecture choices such as avoiding direct hits to core booking service, read replicas vs OLTP DB, CDC/event streaming, pagination and cursor‑based APIs, incremental sync tokens, rate limiting, caching strategy, security/authentication, and supplier isolation. Emphasize scalability, loose coupling, external API design, data synchronization, and production readiness.

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at Agoda recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

Be the first to share your thoughts and start the discussion!