🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Agoda's backend team owns the mission critical domains of a global travel platform: inventory, pricing, booking, payments and the customer and partner platforms. These are high scale, fault tolerant distributed systems running with high availability, low latency and zero downtime expectations, shipped dozens of times a day. The stack is Scala, Go, Java and Kotlin with Kafka and Aerospike, on strong CI/CD, automation and observability foundations. What makes this posting good is its honesty about the split: it says you stay hands-on with coding and system design 50 to 60 percent of the time, which is a rare and useful number to publish at staff level. Apply if you want booking and payments scale, where consistency problems are real rather than hypothetical. Who it is for: Requirements. 8 to 12 years of backend engineering experience. Experience with NoSQL databases such as Cassandra, MongoDB or Aerospike. What you would do. Design and build scalable distributed systems and microservices. Lead development of complex features and technical initiatives end to end. Drive system design, API design and engineering best practice. Own scalability, performance, reliability and fault tolerance of services. Optimise high throughput, low latency systems. Contribute to cross team collaboration and system alignment. Stay hands-on with coding and system design 50 to 60 percent of the time. Mentor engineers and support team capability growth. Participate in technical decision making and architectural improvements. Handle production issues, root cause analysis and continuous improvement. The 50 to 60 percent number is worth the price of admission. Very few staff level postings tell you how much of the job is still coding. Agoda does, in writing, which means you can hold them to it and you know what you are signing up for. The team and stack. High scale, fault tolerant distributed systems for a platform serving millions of users daily, owning inventory, pricing, booking, payments and customer and partner platforms. Systems run with high availability, low latency and zero downtime expectations using Scala, Go, Java and Kotlin with Kafka and Aerospike. The team ships dozens of releases a day. Visa. Agoda records "Visa sponsored: False" on this requisition and the title says Gurugram based, so this is for candidates already able to work in India. Department is listed as IT Engineering. Who this is for. A backend engineer with eight or more years who wants scale and wants to keep writing code. JVM and Scala experience transfers most directly. Agoda also runs a Level 5 version at 11+ years in the same office, also in this edition, which adds architecture and cross team leadership. .
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.