Ola is coding-first with mobility marketplace flavor later. Clear OA before polishing domain stories.
What actually rejects people
Weak coding with only ‘mobility domain’ talk.
First round: Ola OA + interviews
Time split that matches how candidates report outcomes (not a marketing pie chart):
DSA 45%
Projects 25%
Culture 20%
Mocks 10%
Patterns are from student reports and vary by role and drive. Trust your college placement email over blog folklore.
Stage
Time
What they check
OA
timed
DSA
Tech + HR
multiple
Coding + ownership
Understand eligibility criteria (6.5+ CGPA, no backlogs)
Study exam pattern (OA with DSA problems, technical interviews, system design)
Practice previous year Ola placement papers with solutions
Master DSA fundamentals (arrays, trees, graphs, DP) - solve 100+ problems on LeetCode/HackerRank
Learn system design basics (ride matching, payment systems, scalability)
Prepare for technical interviews (coding, algorithms, projects)
One timed block that matches Ola’s first round (coding + culture)
Log misses: topic + why you failed (speed, concept, carelessness)
Re-solve yesterday’s misses cold
Twice a week: 10 minutes of resume/project narration out loud
Week
Focus
Exit criteria
1-2
DSA fundamentals
Clean easy/medium solves
3-4
Projects + ownership stories
Resume bullets measurable
5-6
Mocks + culture
Explain trade-offs under pressure
7-8
Weak topics + HR
No unfinished ‘hero’ projects on resume
Order problems by confidence after a 3-4 minute skim
Passing test cases beats a brilliant half-solution
Invent edge cases before submit; watch timeboxes
Restate → brute force → optimize → code → test
Show ownership; unfinished resume projects get punished.
Tie CS answers to a project when it strengthens the point
Why Ola, why this team/role, location flexibility
STAR with a metric; pick 2-3 real company values and prepare proof
Graphs/heaps/hashing
Dispatch/matching reasoning
Working code in one language
Projects you actually shipped
Ownership stories
Product sense lite
Breadth across stack claimed on resume
Full-length mock every other day
Light revision only - no new rabbit holes
Sleep, ID proofs, machine/network checklist for test day
30 days out: weekly full OA-style mocks; close weak DSA patterns; draft STAR stories.
7 days out: alternate mock / review days; re-solve misses cold; no new patterns.
Day before: skim notes, check machine/network/ID logistics, sleep.
Weak coding with only ‘mobility domain’ talk - fix this first
Preparing only interviews while failing Ola’s first round
Collecting notes without timed mocks
Listing five frameworks on the resume and defending none
Changing language/stack one week before the drive
Listing half-built side projects as production
Uber · Zomato · Swiggy · Flipkart · Paytm · Zoho
Next step: Run one timed mock this week that matches Ola’s first round (coding + culture), then build the weeks around your weakest section - not around what is most fun to study.