Academic snapshot
Marks: 7.0+ CGPA / 70% (candidate-reported)
Degree: B.Tech / B.E. / M.Tech
Backlogs: None active
Year: Final-year and recent grads (~1 year)
UBER Placement Papers 2026
Uber is a global transportation technology company that connects riders with drivers through its mobile app. Founded in 2009, Uber operates in 70+ countries and has expanded into Uber Eats, freight, and autonomous vehicles. Uber India engineering hubs work on payments, mapping, and platform optimization.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Who can apply to Uber in 2026?
Who this hub is for
- For: Students targeting Software Engineer I / SDE-1 (and early SDE II) at Uber - India hubs and global remote/hybrid loops that still run the same OA + DSA bar.
- Not the same track: Driver-partner ops, pure city ops, or non-tech roles. Those bars do not map to this coding → design → managerial loop.
- Experienced hires: L5A / senior loops add BPS depth and heavier design. Use fresher sections as a base, then read senior interview notes separately.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA window, PPT timing, college CGPA list when printed | Medium-hard coding bar, interview depth |
| Careers portal / referral | Resume screen volume; sometimes no hard published CGPA | Still expect OA + tech loop; BPS appears more in off-campus write-ups |
| Intern → full-time | Conversion interviews may skip a stage | You still defend projects and code |
Off-campus does not mean easier coding. It often means more applicants fighting the same 60-90+ minute filter - and sometimes an extra BPS gateway before the final loop is even scheduled. If your CGPA sits near 7.0, spend energy on timed mocks, not on hunting a mythical lower cutoff blog post.
Degree, projects, and “is 7.0 enough?”
Is 7.0 CGPA enough? Yes - it matches the commonly reported 7.0 / 70% floor. Selection still hinges on OA correctness, graph/heap fluency, and design narration. A 7.1 with clean timed coding beats an 8.8 that freezes on edge cases.
What helps the resume screen: One project you can defend end-to-end (stack choice, hardest bug, metric), any internship with ownership language, and honest tech keywords you can explain. Certificates are optional extras - DSA and OA mocks matter first. See certifications only after fundamentals are solid.
Who usually fits: You like timed medium-hard DSA, you can talk through graphs without freezing, and you can explain ride-matching in plain words. Latency / reliability stories from college projects help managerial rounds.
Who struggles: LeetCode-only grinders who never timebox; design answers that open with “Kafka + Redis” and no requirements; candidates who treat BPS as optional soft chat when the write-up says it is the schedule gate.
Branch note: CS/IT/ECE dominate candidate reports, but related streams clear when DSA is strong and the JD includes them. Read your notice; do not assume every circuit branch is auto-included.
Branch & skills
Preferred: CS / IT / ECE
Languages: Python, Java, C++
Also seen: Go, JavaScript, Kotlin
Focus: DSA, graphs/heaps, ride systems
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 7.0+ CGPA / ~70% across 10th, 12th, graduation | Must clear all three when the JD says so |
| Degree | B.Tech / B.E. / M.Tech | Related computing degrees on many posts |
| Branch | CS, IT, ECE (preferred) | Strong DSA helps adjacent branches on some drives |
| Year | Final year + recent grads (~1 year) | Internship → conversion paths also appear |
| Backlogs | No active backlogs | Clear them before offer paperwork |
| Gap | Explain cleanly if present | Valid reasons usually fine when skills are strong |
| Coding languages | Python, Java, C++ | Stick to one for OA + interviews |
Selection chances by CGPA band
| CGPA range | Rough chances | Reality check |
|---|---|---|
| 7.0-7.4 | Medium | Eligible; OA + BPS decide |
| 7.5-8.4 | High | Competitive shortlisted band with solid OA |
| 8.5+ | Very high if tech holds | CGPA alone never clears design / managerial |
Uber CGPA criteria
The minimum CGPA required is 7.0 CGPA / 70% across 10th, 12th, and graduation is the commonly cited campus floor. Treat it as a shortlisting filter when printed - Uber still decides on OA correctness, BPS (when present), and interview narration. Always verify your drive notice.
Uber does not publish one universal India cutoff for every SDE drive. Numbers above are candidate-reported from campus notices, JDs, and interview write-ups (as of August 2026). Your placement cell mailer always wins.
Uber placement papers - last few years
Download 2026 Uber placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What Uber previous year papers actually train
Uber does not publish one permanent official paper set. “Previous year papers” on this site are pattern trainers for the first filter and early technical rounds - not leaked live assessments.
| Round (typical) | What to practice |
|---|---|
| Online assessment | Timed accuracy on Uber OA (60-90+ min): 2-3 medium-hard DSA |
| BPS gateway (when present) | Production-code coding + high-level design in one sitting |
| Technical DSA | Live coding narration: brute force → optimize → edge cases |
| Design / LLD | Ride-matching, rate limiting, location / ETA intuition |
| Managerial / HR | Why Uber?, ownership under ambiguity, relocation |
Themes that keep repeating (2024-2026)
- 2024 cycles: OA stayed coding-heavy - 2-3 medium-hard problems, often on HackerRank. Graph and heap themes show up early. Off-campus write-ups start calling out BPS as a true schedule gate after OA.
- 2025 loops: More notes describe hashing + intervals + Union-Find cousins alongside classic graphs/DP. Design chat around matching / routing / ETA appears after you clear code. Students who only drilled unsorted LeetCode without timeboxes lost easy marks.
- 2026 prep expectation: Keep graph fluency, heap/Top-K, and interval merge warm. Expect design rounds to stay level-appropriate (actors, APIs, bottlenecks) - not staff-level distributed systems theater for every fresher. Treat PDF packs as pattern catalogs: Master the interval template, do not memorize that exact story.
How to use one paper set in a single sitting
- Timed: run a full 75-90 minute mock (2-3 coding) with the same language you will use on test day.
- Untimed review: rewrite the cleaner solution; list three edge cases you missed (empty graph, single node, overflow).
- Map each coding miss to a theme (graph / heap / DP / Union-Find / intervals) and pull two cousins from coding questions.
- Spend 15 minutes explaining ride-matching or distributed rate limiting out loud like a teammate.
- Log one STAR story the session reminded you of (ownership under a broken demo, conflict on a team deadline).
Paper review template: Date · DSA themes · Time left · Design sketch topic · Behavioral story practiced. Use it after every mock so mistakes become a queue, not a vibe.
Related problems to practice
| Theme you saw in a set | What to drill next | Why Uber asks it |
|---|---|---|
| Shortest path / BFS layers | Multi-source BFS, Dijkstra variants | Routing, ETA intuition, connectivity |
| Top-K / priority queues | Heap + bucket-sort variants | Nearest drivers, surge priorities, alerts |
| Merge intervals | Overlap, insert interval | Trip windows, discount / surge periods |
| Union-Find / components | Path compression, rank | Connectivity, clustering nearby entities |
| Hash map + sliding window | Frequency maps, two pointers | Location buckets, rate windows |
| DP on sequences / grids | Memo → tabulation | Path counting, optimization under constraints |
2024 PDFs often drill “merge overlapping delivery/trip slots.” Own the interval template - sort by start, merge when next.start <= cur.end - then drill a related problem with open/closed boundaries. That transfers to interviews; memorising the story text does not.
Ride-matching mental model (fold into paper review): rider request → geohash/quadtree lookup of nearby drivers → score (ETA, rating, acceptance) → assign → update availability. Say the failure modes (no drivers, timeout, double-assign) before naming a queue.
Rate-limiting mental model: token bucket or sliding window per user/IP → Redis-style shared counter for multi-instance → graceful 429 + retry. Fresher depth: correctness and consistency trade-offs, not a full SRE runbook.
Uber placement process, round by round
Uber hires freshers through campus placement cells, the careers portal, referrals, and internship conversion. After resume screen, the shape is product-company style: hard timed OA, then DSA + design depth by level, sometimes a BPS gateway, then managerial and HR.
Application methods
Campus recruitment
Through college placement cells - PPT, then OA and interviews on a batch timeline.
Online applications
Apply on Uber careers for early-career / fresher tech roles; follow the invite mailer for platform and duration.
Referrals & internships
Employee referrals improve visibility. Intern conversion still needs defendable code and projects.
1. Resume / eligibility screen
Placement cell or recruiter checks degree, CGPA floor when printed (7.0+ / 70% commonly reported), backlogs, and year of passing. Projects and internships help when volumes are high. This is a gate, not the hard filter - coding is.
2. Online Assessment - Uber OA
Candidate reports commonly describe a 60-90+ minute assessment with 2-3 medium-hard coding problems. Platforms: HackerRank or CodeSignal-style. Exact duration varies by drive - treat the table as a working map, not a sealed blueprint.
| Component | Typical range | Focus |
|---|---|---|
| Coding problems | 2-3 | Graphs, heaps, hashing, intervals, Union-Find, DP |
| Duration | 60-90+ min | Confirm on invite |
| Languages | Python, Java, C++ (+ Go/JS/Kotlin) | One language end-to-end |
| Clear rate | ~20-25% | Fully passing solutions matter |
Pass bar in practice: Correct, fully passing solutions beat a brilliant half-answer. Advancement after OA is often cited around 20-25% - treat the filter as real.
Student tip: Spend 3-4 minutes skimming all prompts. Bank the solvable one first. Invent two edge cases before submit. Do not burn the clock proving a fancy algorithm if a clean O(n log n) already passes.
Example timing for a 75-minute OA
| Minute | Move |
|---|---|
| 0-5 | Skim all statements; mark easy wins |
| 5-30 | Problem A: restate → brute → optimize → code → sample tests |
| 30-55 | Problem B (harder graph/heap): same loop; leave breadcrumbs if stuck |
| 55-70 | Problem C or harden B |
| 70-75 | Edge cases only - do not open a new hard rabbit hole |
Example timing for a 90-minute OA
| Minute | Move |
|---|---|
| 0-5 | Skim + rank difficulty |
| 5-35 | First medium: full AC attempt |
| 35-70 | Second (often graph/DP): plan aloud on paper first |
| 70-85 | Third or polish second |
| 85-90 | Harden tests; check off-by-one / empty inputs |
Deeper OA notes and drills: Uber Online Assessment.
3. Bps gateway - coding + high-level design
Several off-campus and L5A write-ups describe BPS as a true gate: clear it, and the remaining loop gets scheduled; fail it, and you do not proceed. Format candidates report: medium coding with production-code expectations, plus high-level design discussion in the same round.
Treat BPS like a mini final loop in one sitting:
- Clarify requirements and constraints
- Ship clean, readable code (not contest golf)
- Sketch design: actors → APIs → data → bottlenecks
- Discuss trade-offs without buzzword fog
If your invite does not mention BPS, do not invent panic - campus batches often go OA → technicals. If it does, prep accordingly.
4. Technical interview 1 - DSA (~45 min)
Video or onsite shared editor. Expect 1-2 DSA problems plus a short project warm-up. Patterns candidates report: trees, graphs, hashing, heaps, DP.
You should:
- Clarify constraints (null inputs, duplicates, directed vs undirected)
- Narrate brute force → bottleneck → target complexity
- Code in your chosen language without syntax stalls
- Walk edge cases and complexity at the end
Interviewers care about debugging out loud. Silent staring after a failed mental test case is a common reject signal even when the idea was right.
Example narration shape (Top-K nearest drivers by score): “Brute force is sort all candidates O(n log n). For top-k we can heap in O(n log k).” I’ll use a min-heap of size k keyed by score… Empty set returns empty; ties - I’ll state the rule before coding.”
5. Technical interview 2 - System Design / LLD (~45 min)
Depth scales with level. Freshers get actors, APIs, data choices, bottlenecks. Mid-levels get more distributed trade-offs.
Typical prompts:
- Ride-matching: nearby drivers, scoring, assignment, double-booking
- Real-time location / ETA: update frequency, stale location
- Distributed rate limiting: per-user quotas across instances
- Payment / trip lifecycle: reserve → pay → complete → refund
Worked mini-outline - ride-matching:
- Actors: rider, driver, matching service, location service, trip service.
- Happy path: request → fetch nearby → score → offer → accept → start trip.
- Failure: no drivers / timeout / driver cancels → expand radius or re-queue.
- Geo: geohash or quadtree for “nearby”; say why you picked one.
- Scale later: only after the above is clear - caching hot geohashes is fine; do not lead with a buzzword diagram.
Worked mini-outline - rate limiting:
- Requirement: N requests per user per window.
- Algorithm: token bucket vs sliding window - pick one and defend.
- Distributed: shared store (Redis-style) vs sticky sessions.
- Failure: store down → fail open vs fail closed - say the product choice.
6. Technical interview 3 - depth round (~45 min)
Advanced coding or deeper design / specialization, depending on level and prior performance. Some loops mix algorithms with architecture follow-ups from your resume. Culture and communication still count - explain trade-offs like a teammate.
7. Managerial round (~45 min)
Why Uber (not “biggest ride app” only), ownership under ambiguous requirements, conflict with a teammate, impact metrics, relocation. Scenario prompts are common: matching latency spikes during peak; a payment lag; a teammate wants to ship broken. Uber-shaped answers protect the rider/driver experience, take ownership of the next step, and quantify impact when you can.
8. HR / offer (~30 min)
Background, joining date, CTC structure (base vs RSUs), notice / exams. Know the ₹18-25 LPA SDE I band so compensation talk is grounded. Ask one real question about the team’s surface (matching, payments, maps) - it beats “what is the culture?”
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | OA (coding) | 60-90+ min | Timed medium-hard accuracy |
| 2 | BPS (when present) | ~45-60 min | Coding + design gateway |
| 3 | Technical 1 (DSA) | ~45 min | Code + narration |
| 4 | Technical 2 (design/LLD) | ~45 min | Ride systems reasoning |
| 5 | Technical 3 | ~45 min | Depth / specialization |
| 6 | Managerial | ~45 min | Ownership, ambiguity, fit |
| 7 | HR | ~30 min | Logistics, CTC, joining |
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT week then OA window |
| OA completion → shortlist | Few days common | ~20-25% advance often cited |
| BPS (if any) → final loop schedule | Days | Clear BPS before remaining rounds |
| Interview loop | ~1-2 weeks | Tech → design → managerial → HR |
| Offer / paperwork | Days after final round | Written offer wins over verbal |
| End to end | ~3-4 weeks common | Off-campus can stretch |
OA pattern cheat-sheet
| Component | Focus | Prep move this week |
|---|---|---|
| Coding Q1-Q2 | Graphs, heaps, hashing, intervals | Two timed mediums back-to-back |
| Coding Q3 | Union-Find / DP / harder graph | One hard with partial credit plan |
| Design follow-ups | Matching, rate limit, ETA | Explain one flow in 3 minutes aloud |
| Managerial / HR | Why Uber, ownership | Two STAR stories + relocation answer |
Uber aptitude, coding & interview practice
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
How to train for Uber this season
If a Uber invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Uber sits around ₹18-25 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Uber eligibility for freshers 2026 is candidate-reported: commonly 7.0+ CGPA / 70% across 10th, 12th, and graduation. Degree: B.Tech/B.E./M.Tech in CS, IT, ECE, or related fields. Final-year students and recent graduates (within ~1 year). No active backlogs. Preferred branches CS/IT/ECE; strong programmers from related streams also clear when the JD allows. Always verify your campus drive notice or careers posting.
What you are training for: Uber fresher / early-career loops typically run: Online Assessment (60-90+ minutes, 2-3 medium-hard coding on HackerRank/CodeSignal-style) → sometimes a BPS coding+design gateway → technical DSA rounds → design/LLD depth by level → managerial → HR. Campus and off-campus routes feed a similar bar. End-to-end often 3-4 weeks from application to offer.
Short version of the prep split: Split prep roughly 40% DSA (graphs, heaps, hashing, intervals, Union-Find, DP), 25% system design / LLD (ride-matching, rate limiting), 20% timed coding mocks on HackerRank-style platforms, 15% interview/behavioral. Languages: Python, Java, C++ (also Go/JS/Kotlin). Clear OA accuracy before deep design theater.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Timed aptitude + one easy coding problem a day, plus a one-page cs fundamentals sheet. Open the Uber previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Uber drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Uber usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Uber?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Two full mocks, then only error-log topics - no new patterns. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Uber-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the Uber story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Uber PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed Uber papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Uber papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Uber-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
10-day crash version
Days 1-3: one timed Uber paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Uber. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
What to carry into the interview room
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For Uber, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
Tracking that does not become a second job
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three Uber mistakes, you are collecting content, not preparing.
Extra drill block (1)
Sit one more mixed Uber set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
Uber fresher CTC in India (2026)
Figures below are candidate-reported as of August 2026 for India hiring conversations. Uber does not publish a single public fresher CTC table for every role. Always confirm base, bonus, and RSUs on the written offer.
Software engineer roles
| Level | Experience (typical) | Base (rough) | Total package (candidate-reported) | Notes |
|---|---|---|---|---|
| Software Engineer I | 0-1 years | ₹15-20 LPA | ₹18-25 LPA | New grads / freshers |
| Software Engineer II | 1-2 years | ₹20-28 LPA | ₹25-35 LPA | Early career |
| Senior Software Engineer | 3-5 years | ₹30-42 LPA | ₹35-50 LPA | Design depth expected |
| Staff Software Engineer | 5+ years | ₹45-60 LPA | ₹50-70 LPA | Leadership + scope |
Student reports often discuss total package including RSUs. Vesting schedules and refreshers vary - ask HR for the equity vesting timeline, not only the headline LPA.
Other roles students ask about
| Role | Level | Total package (reported bands) | Requirements |
|---|---|---|---|
| Product Manager | Entry | ₹25-35 LPA | MBA or strong technical PM path |
| Data Engineer | Mid | ₹30-45 LPA | Pipelines, distributed data |
Benefits students commonly mention
- Health insurance: medical coverage for employee and dependents (plan details vary)
- RSUs / equity: part of total compensation conversations
- Learning budget: courses, conferences, certifications after joining
- Hybrid / flexible norms: team-dependent; confirm with hiring manager
- Meals / office perks: location-dependent
Negotiation tip: Know the SDE I band before HR. Ask for base vs stock split in writing. Do not anchor only on a friend’s Twitter screenshot from a different year or city.
Uber hiring updates for 2026
Hiring bar 2026
OA remains the main volume filter (~20-25% clear in many reports). Graphs, heaps, and interval/Union-Find cousins stay warm. Design depth rises with level.
Bps visibility
Off-campus and some L5A loops still describe BPS as a schedule gate after OA. Campus batches may skip the label but keep coding + design pressure later.
India engineering growth
Bangalore, Hyderabad, and Gurgaon continue to appear in fresher and experienced hiring chatter for payments, mapping, and platform teams.
Domain flavor
Matching, routing, ETA, and rate limiting show up in design chats more than generic “design Instagram.” Prep mobility-shaped examples.
Process shape students report in 2026: virtual interviews remain common; end-to-end 3-4 weeks is still a useful planning number; faster loops happen for strong OA + BPS clears. AI/ML and autonomy teams hire, but fresher SDE loops still live or die on DSA first.
Prep implication: do not over-index on trendy ML certificates if your OA graph skills are weak. Certificates after fundamentals - see certifications.
Uber placement FAQs
What is Uber eligibility criteria for freshers 2026?
Candidate-reported floor: 7.0+ CGPA / 70% across 10th, 12th, and graduation; B.Tech/B.E./M.Tech in CS, IT, ECE, or related; final-year or recent grads (~1 year); no active backlogs. Preferred branches CS/IT/ECE. Always verify the drive notice - Uber does not publish one universal cutoff for every India SDE drive.
What is the Uber placement process?
Typical shape: OA (60-90+ min, 2-3 medium-hard coding) → sometimes BPS (coding + high-level design gateway) → technical DSA → design/LLD (depth by level) → managerial → HR. Campus and off-campus feed a similar bar. End-to-end often 3-4 weeks.
How many rounds are there in Uber interview?
Most fresher loops report OA plus about 3 technical-style stages, then managerial and HR - roughly 5-6 stages after application. Some off-campus / L5A write-ups insert BPS before the final loop is scheduled. Count the stages on your invite, not a fixed global number.
Can I download Uber placement papers PDF for free?
Yes. Free Uber placement papers PDF and previous-year style OA/DSA sets for 2024-2026 are on this site (including /uber/uber-placement-paper-2026.pdf). No registration for the main downloads. Papers are pattern trainers, not leaked live assessments - use them for themes and timing, not memorisation.
What is Uber salary for freshers 2026?
As of August 2026 (student reports): SDE I ₹18-25 LPA, SDE II ₹25-35 LPA, Senior ₹35-50 LPA. Total-package talk often includes RSUs. Confirm base vs equity on the written offer; bands vary by location and level.
How to prepare for Uber placement 2026?
Split time roughly 40% DSA, 25% design/LLD, 20% timed coding mocks, 15% interview/behavioral. Prioritize graphs, heaps, hashing, intervals, Union-Find, and DP. Practice ride-matching and rate limiting aloud. Languages: Python, Java, C++ (also Go/JS/Kotlin). See the prep section above and preparation guide.
What is the Uber online assessment (OA) pattern?
Typically 60-90+ minutes, 2-3 medium-hard coding problems on HackerRank / CodeSignal-style platforms. Topics: graphs, heaps, hashing, intervals, Union-Find, DP. Candidate-reported clear rate about 20-25%. Aim for at least two fully passing solutions. Details: online assessment.
What is Uber BPS gateway round?
In several off-campus and L5A reports, BPS mixes coding (often LeetCode-medium with production-code expectations) and high-level design. Candidates describe it as a gateway: clear BPS, then the remaining final loop is scheduled. If your invite names BPS, rehearse coding + design in one sitting - do not treat it as optional soft chat.
What system design topics appear in Uber interviews?
Common fresher/mid prompts: ride-matching, real-time location / ETA, distributed rate limiting, and trip/payment lifecycle. Start with actors → APIs → data → bottlenecks. Geohash/quadtree intuition helps for “nearby.” Lead with requirements, not Kafka.
What programming languages are allowed in Uber coding rounds?
Primary: Python, Java, C++. Also accepted in many invites: Go, JavaScript, Kotlin. Confirm the platform list on your OA mailer. Pick one language early and keep it for mocks and interviews - Uber cares more about problem-solving than language count.
Uber vs Google vs Amazon - which is better for freshers?
Uber: mobility/real-time systems, ₹18-25 LPA SDE I band (student reports), strong OA + design flavor. Google: algorithm depth, Googleyness, often higher L3 bands in student chatter. Amazon: Leadership Principles + Bar Raiser, SDE-1 bands commonly in a similar India product range. Choose on team, learning, location, and written offer - not brand tweets. Compare hubs: Google, Amazon.
Uber vs Ola vs Swiggy - which is better for freshers?
Uber: global scale, graphs/routing flavor, ₹18-25 LPA SDE I. Ola: India mobility focus, often slightly different entry bands in reports. Swiggy: food delivery / logistics product engineering. Pick by domain (rides vs food) and written CTC. See Ola, Swiggy, Zomato.
Any pro tip for Uber placement preparation?
Bank one solvable OA problem first, then attack the harder graph/heap prompt. Practice explaining ride-matching in plain words before interview day. If your loop includes BPS, treat it as the real schedule gate - readable production code plus a clean design sketch in the same sitting.
Does Uber allow active backlogs?
Candidate reports and campus JDs commonly say no active backlogs at application or joining. Clear them before paperwork. If your notice is silent, ask the placement cell in writing.
Is an internship at Uber required to get a full-time offer?
No. Many freshers clear campus or off-campus SDE I without a prior Uber internship. Intern → full-time conversion exists and can skip a stage, but the coding bar still applies. Strong OA + interviews beat waiting for an intern badge.
Where should I practice Uber-style coding questions?
Use timed mocks on HackerRank-style UIs, Uber-tagged mediums on LeetCode, and the nested banks on this site: coding questions, online assessment, and year pages under 2024, 2025, 2026.
What roles do freshers usually join at Uber?
Most student reports target Software Engineer I. Adjacent early-career paths (data, SRE) appear less often for campus freshers and may have different screens. Read the JD - do not assume every Uber posting is the same SDE I loop.
What recent candidates reported
An off-campus SDE-1 candidate described a HackerRank OA with 3 medium-hard DSA in 75 minutes, then Uber’s BPS round mixing coding and high-level design: “This round is a gateway; you are eligible for the final loop only if you clear this” (GeeksforGeeks). Only after BPS came the DSA + LLD + hiring-manager loop - a process shape freshers often underestimate versus a plain OA-to-interview path.
A May 2024 Uber L5A candidate explained on GeeksforGeeks that Round 1 Coding BPS is the true gate: one LeetCode-medium with production-code expectations. Critically, “If you clear this round, the next 4 rounds are going to be scheduled for you irrespective of your performance in the subsequent rounds.” The remaining loop mixed Algorithms, Depth in Specialization, greenfield design, and a Manager collaboration/leadership design discussion before offer feedback.
Takeaways for 2026 prep: (1) timebox OA like a contest; (2) if BPS appears, treat it as the schedule key; (3) keep design narration ready even when the first filter is pure coding. More write-ups: interview experience.
Similar companies
If Uber is one of several product offers you want, compare process shape and domain flavor - not only brand:
Google · Amazon · Microsoft · Ola · Swiggy · Zomato
- Google / Amazon / Microsoft: heavier algorithm or LP/Googleyness culture gates; useful if you want global platform exposure alongside mobility.
- Ola: India mobility peer - similar domain vocabulary, different company scale and CTC bands.
- Swiggy / Zomato: logistics and delivery systems with India ops intensity; good parallel prep for matching/ETA intuition even when the product is food, not rides.