The hiring process
| Round | Format | What's tested |
|---|---|---|
| Online Assessment | ~90 min | Timed algorithmic coding |
| Technical – DSA | ~45–60 min | Live problem-solving depth |
| Machine Coding / LLD | ~60–90 min | Object modelling and clean code |
| HLD / System Design | ~45–60 min | Designing at ride-hailing scale |
| Hiring Manager / HR | ~20–40 min | Ownership and culture fit |
Process and cutoffs vary by drive/team and change over time — confirm on the official careers page.
Round-by-round: exactly what's asked & how to prepare
Online Assessment
~90 minA HackerEarth/HackerRank-style test with 2–3 problems ranging from easy to medium-hard. You are scored on correctness against hidden tests and, for some problems, on passing large inputs within the time limit. Partial credit exists, so bank the easy problem first.
- Sliding-window over a stream of ride events
- Shortest path / Dijkstra variant on a road graph
- DP on interval scheduling for driver shifts
- Greedy allocation with a priority queue
- String parsing of trip logs
- Grind LeetCode arrays/strings/graphs/DP mediums (leetcode.com)
- Time yourself on Striver's A2Z DSA sheet (takeuforward.org)
- Practice fast I/O and edge cases on HackerEarth mock tests
- Rehearse writing bug-free code without a debugger
- Chasing the hardest problem and leaving easy points on the table
- Ignoring integer overflow and empty-input edge cases
- Not testing against large inputs before submitting
- All-tests-pass on at least the two easier problems
- Clean, readable solutions with correct complexity
- Efficient use of the time budget
Technical – DSA
~45–60 minOne to two medium-hard problems on a shared editor, usually graphs, trees, or DP. The interviewer cares as much about how you narrate trade-offs as the final code. Expect follow-ups that tighten complexity or change the input scale.
- Graph connectivity for road-network partitioning
- K-nearest drivers via heap or grid bucketing
- DP for optimal fare/route segmentation
- LRU-style cache for hot map tiles
- Interval merging for surge windows
- Solve 15–20 graph and DP mediums, dry-running each aloud
- Practice stating brute force → optimized before coding (NeetCode roadmap)
- Rehearse complexity analysis for every solution
- Do 3–4 mock interviews on Pramp
- Coding before agreeing on the approach
- Going silent while thinking
- Skipping complexity discussion the interviewer expects
- Structured brute-force-to-optimal progression
- Correct handling of tricky edge cases
- Clear complexity reasoning
Machine Coding / LLD
~60–90 minYou design and implement a small system with real classes, extensibility, and thread-safety considerations. Interviewers reward clean abstractions and testable code over cramming every feature. Common at SDE-2 and above.
- Design an in-memory ride-booking allocator
- Task manager / scheduler backed by a set data structure
- Rate limiter for the pricing service
- Parking-lot or cab-fleet OOP model
- Notification dispatcher with pluggable channels
- Study LLD patterns (refactoring.guru for SOLID and design patterns)
- Build 3–4 machine-coding problems end to end in your language
- Practice writing interfaces first, then implementations
- Read the low-level-design-primer (github.com/prasadgujar)
- Jumping to code without clarifying requirements
- God classes with no separation of concerns
- Ignoring concurrency where the prompt implies it
- Clean, extensible class boundaries
- Working, compilable code within the time box
- Sensible handling of edge cases and thread-safety
HLD / System Design
~45–60 minAn open-ended design of a system Ola actually runs, focused on scale, latency, and consistency trade-offs. You drive the whiteboard: requirements, APIs, data model, bottlenecks. Depth expectations rise sharply from SDE-2 to SDE-3.
- Design real-time driver-rider matching
- Surge pricing pipeline with fresh demand signals
- Live location tracking and ETA at millions of pings/sec
- Payments and wallet with idempotency
- Geo-sharded search for nearby drivers
- Work through the System Design Primer (github.com/donnemartin)
- Watch Gaurav Sen and ByteByteGo design breakdowns (YouTube)
- Practice estimating QPS, storage, and bandwidth aloud
- Design 4–5 systems end to end with a timer
- Skipping requirement and scale clarification
- Hand-waving the data model and consistency choices
- No discussion of bottlenecks or failure modes
- Clear requirement scoping and back-of-envelope numbers
- Justified storage and consistency trade-offs
- Awareness of hot-partition and latency pitfalls
Hiring Manager / HR
~20–40 minA mix of past-project deep dive and behavioral questions about ownership, ambiguity, and speed. Ola runs lean and fast, so they probe for bias-to-action and end-to-end responsibility. Expect a few questions on why Ola specifically.
- A project you shipped under a tight deadline
- A production incident you owned end to end
- Disagreement with a teammate or manager
- Handling shifting requirements
- Why mobility / why Ola
- Prepare 5–6 STAR stories with metrics
- Research Ola's product lines and recent launches
- Prepare thoughtful questions about the team
- Practice concise 2-minute story delivery
- Vague stories with no measurable impact
- Blaming teammates in conflict examples
- No specific reason for wanting Ola
- Concrete ownership with quantified outcomes
- Calm reasoning through ambiguity
- Genuine interest in the mission
What to master
- Arrays & strings
- Graphs & shortest paths
- Dynamic programming
- Trees & heaps
- Low-level design / OOP
- Distributed system design
- Concurrency basics
- Databases & caching
Eligibility
open — role-based
Ola salary & compensation (2026)
Ola pays competitive India CTC with a real ESOP and variable component that grows sharply at senior levels.
| Role / Level | Experience | India — total CTC | US — total comp | What to know |
|---|---|---|---|---|
| SDE-1 | 0–2 yrs | ₹16–26 LPA | — | mostly fixed; small joining bonus and modest ESOP |
| SDE-2 | 2–5 yrs | ₹28–45 LPA | — | fixed + ~15–20% variable; ESOP becomes meaningful |
| SDE-3 / Senior | 5–8 yrs | ₹45–70 LPA | — | larger ESOP grants and higher variable weighting |
| Staff / Lead | 8–12 yrs | ₹70 LPA–1.1 Cr | — | ESOP is a large slice of total comp |
| Principal / EM | 12+ yrs | ₹1.1–1.8 Cr+ | — | heavily ESOP-weighted; negotiable |
How the package is structured
- Structure is fixed base + performance variable + ESOP; ESOP weight rises steeply from SDE-3 up.
- Competing offers move the fixed base the most; negotiate that first.
- Ask about ESOP strike price, vesting, and the latest 409A/valuation to value equity honestly.
- Level placement drives comp more than negotiation — aim to interview at the highest justifiable level.
Indicative 2026 market ranges aggregated from public sources (levels.fyi, Glassdoor, AmbitionBox, candidate reports). Compensation varies widely by location, team, level calibration, and negotiation — use these as directional benchmarks, not guarantees.
Your prep plan
- Days 1–4: drill arrays, strings, and graphs to solid medium level
- Days 5–7: DP and trees plus one timed OA simulation
- Days 8–9: build two machine-coding problems end to end
- Days 10–11: practice three HLD designs with QPS math
- Day 12: write and rehearse six STAR stories
- Days 13–14: mixed mocks and review weak topics
Want this plan dated to your interview?
Upload your resume and tell Whis your interview date — get a personalized, day-by-day plan built around your gaps, then run Whis live in the interview.
Get my personalized planFrequently asked questions
Is Ola Cabs the same interview as Ola Electric?
The core DSA and design bar is similar, but Ola Electric roles may lean harder into embedded, IoT, or platform topics depending on the team. Confirm the team's focus with your recruiter.
How much system design should a fresher expect?
SDE-1 loops are DSA-heavy with light LLD. Meaningful HLD kicks in from SDE-2 onward.
Does the OA allow partial scoring?
Yes, most Ola OAs award per-test-case credit, so submit working partial solutions rather than nothing.