Grab logo

Site Reliability Engineer Interview Experience at Grab2026

Grab

In Progress 2 rounds Feb 2026 Off Campus
O

Om Prakash Nair

3-6 Years · Experienced

General SRE Pattern

No specific, verified real Grab SRE candidate account was found. Built from generally reported real SRE loop patterns at Southeast Asian super-app companies, reflecting Grab's known multi-service (ride-hailing, food delivery, payments) platform architecture referenced in real Grab engineering blog posts.

Application Story

Applied online for an SRE role and moved through a recruiter screen and a technical round, with a system design round and final hiring manager round still scheduled.

Preparation Journey

Given Grab operates several distinct but interdependent services (rides, food delivery, payments) on shared infrastructure, I focused preparation on cross-service dependency management and blast-radius containment rather than single-service reliability alone.

Resume Tips

For an SRE role at a multi-service super-app platform, be ready to reason about how a failure in one service (like payments) should be contained so it does not cascade into unrelated services (like ride matching) that happen to share infrastructure.

01Round
EASY

Telephonic

30 minutes Remote

Recruiter screen on background and specific interest in reliability engineering across a platform with several distinct but interdependent product lines rather than a single-product service.

02Round
HARD

Technical

60 minutes Remote

Focused on containing blast radius across interdependent services. Given a scenario where the payments service is experiencing elevated latency, I was asked how I would prevent that from cascading into the ride-matching service, which depends on payments completing to confirm a booking. I proposed a circuit breaker on the ride-matching side that falls back to a degraded 'pay later' confirmation flow rather than blocking the entire booking on a slow payments call, and the interviewer pushed on how I would decide the circuit breaker's timeout threshold without either tripping too eagerly on normal latency variance or too late to actually protect the user experience.

Comments

Loading comments...

Questions Asked at Grab in the Site Reliability Engineer Interview

Telephonic Round

Recruiter screen on background and specific interest in reliability engineering across a platform with several distinct but interdependent product lines rather than a single-product service.

Technical Round

Focused on containing blast radius across interdependent services. Given a scenario where the payments service is experiencing elevated latency, I was asked how I would prevent that from cascading into the ride-matching service, which depends on payments completing to confirm a b