Academic snapshot
Marks: 70% or 7.0 CGPA throughout 10th, 12th, graduation
Degree: B.Tech / B.E. / M.Tech (CS/IT/related)
Backlogs: None active on most drives
Year: Final-year and recent grads (within ~2 years)
Urban Company Placement Papers 2026
Urban Company, formerly UrbanClap, is a home services marketplace founded in 2014 and headquartered in Gurgaon. Its engineering teams build matching, booking, and partner quality systems for on-demand services. Urban Company recruits campus graduates for backend, mobile, and data engineering roles.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Who can apply to Urban Company in 2026?
Urban Company is a product SDE loop, not a bank aptitude paper. The printed floor is often 70% throughout. The real cut is two passing coding solutions, then whether you can design a marketplace out loud.
Who this hub is for
- For: Students targeting Software Engineer / SDE-1 campus and off-campus loops.
- Not the same track: Category ops, partner onboarding non-eng, experienced EM searches.
- ECE/related: Eligible when the notice lists them and DSA is real. A hardware project does not replace graphs.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA window, PPT | 90-min coding bar |
| Careers / referral | Resume volume | Still expect OA + two techs |
| Intern → FTE | May skip a stage | You still defend code and design |
Off-campus does not mean easier DP. It often means more applicants fighting the same HackerRank.
Degree, 7.0, and “is 7.0 enough?”
Is 7.0 CGPA enough? It matches the commonly reported floor. A 7.1 who finishes two OA problems beats a 9.0 that fails hidden tests. A 8.0 with 68% in 12th still dies if the JD says throughout.
Branches: CS/IT dominate. Related streams when DSA is strong and the college list allows.
Gaps and backlogs: Active backlogs are a usual blocker. Gaps need a skills story.
What helps the resume screen: One project with a metric, contest signal when real, any internship with ownership. See certifications after OA mocks.
Skills they actually filter
OA: 2-3 medium coding
Tech 1: DSA live
Tech 2: Marketplace design / LLD
Languages: Python preferred; Java/JS fine
Academic floor students usually see
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| Graduation | 70% or 7.0 | Mailer wins |
| 10th & 12th | Often same throughout rule | Keep scans |
| Degree type | B.Tech CS/IT | Related if listed |
| Backlogs | None active | Confirm drive |
| Coding | Python/Java/JS/C++ | Stick to one |
Who usually fits and who struggles
Good fit: You like timed coding, you will talk through a matching system, and you can live with Gurgaon/hybrid as named.
Harder path: You only read system-design blogs and skip OA; you freeze until you know “the” class diagram; you quote Amazon 35 LPA in HR; you cannot explain a no-show partner.
Urban Company previous year paper PDFs
Download 2026 Urban Company placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What Urban Company previous year papers actually train
Urban Company does not publish one permanent official paper set. Papers on this site are pattern trainers for DSA and marketplace design.
| Round (typical) | What to practice |
|---|---|
| OA | 2-3 medium DSA, 90 min |
| Tech 1 | Live coding, complexity, edges |
| Tech 2 | Matching, booking, LLD |
| Managerial | Impact STAR, product sense |
| HR | City, CTC, why marketplace |
Themes that keep repeating (2024-2026)
- Classic SDE OA: 90 minutes, 2-3 medium-hard coding, HackerRank/CodeSignal, Python-friendly, ~30-40% pass rumours.
- On-campus SDE-1 (then UrbanClap, GFG, Day-0, updated Apr 2024): 1.5-hour coding test plus three one-hour interviews. LFU-like task manager, driverless cab LLD, then VP Engineering managerial with multi-array pair-sum generalizations. “At all points, I felt as if I were in a meeting with interviewers to design new products for the company.”
- Same loop, Interview 2: driverless cab booking app, classes and methods from requirements. Lesson: “The important thing was to be a little creative and discuss all your ideas with your interviewer so that he/she can guide you while going forward.”
- 2025 nested notes: arrays/hashing, graphs, DP; design of matching and booking; behavioural impact.
- 2026 prep expectation: still DSA first. Add one booking/matching sketch. Do not assume an aptitude paper.
How to use one paper set in a single sitting
- Timed: 90 minutes, two problems, submit with tests.
- Untimed: rewrite the slower problem with complexity.
- One 25-minute matching-system sketch (actors, API, failure).
- One LLD class list for a cab or task manager.
- One STAR story with a metric.
Related drills
| Theme | Drill next | Why Urban Company asks it |
|---|---|---|
| Arrays / hashing | Frequency, two pointers | OA |
| Graphs | BFS/DFS, shortest path | Allocation |
| DP | Knapsack/LCS family | OA medium |
| Matching design | Partner ↔ job | Marketplace |
| LLD | Cab / LFU | 2021-2024 campus notes |
Urban Company hiring rounds in 2026
Urban Company hires through campus cells, careers / portals, and referrals. After eligibility, the shape is product SDE: coding OA, two technicals, managerial, HR.
Application methods
Campus placement
Final-year batches. Listen for OA platform and whether managerial is separate.
Careers portal
Direct apply. Resume screen then OA.
Referral
Improves screen odds. DSA still happens.
1. Resume / eligibility screen
70% / 7.0 throughout when printed, listed degree, no active backlogs. Gate.
2. Online Assessment (~90 min)
Student-reported working map:
| Section (typical) | Questions (reported range) | Time feel | Focus |
|---|---|---|---|
| Coding | 2-3 | 90 min | Arrays, strings, DP, graphs |
Pass habit: read both prompts. Finish one fully. Then the second. A third partial is worse than two ACs. Languages: Python, Java, JS, C++. Hidden tests. Student rumours: 30-40% OA pass. Your invite wins.
3. Technical 1 (~45-60 min)
Live DSA. Talk constraints. Edges. Complexity. Brief project.
4. Technical 2 (~45-60 min)
Marketplace design or LLD. Matching, booking, geo, ratings. Cab-booking class design in older notes. Discuss so they can steer you.
5. Managerial (~45 min)
Impact, conflict, ownership. Sometimes more design or a generalization problem (pair-sum style). Feels like a product meeting when it goes well.
6. HR (~30 min)
Why Urban Company, city, CTC/ESOP, joining. Know ₹18-25 LPA. The letter wins.
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / screen | 3-5 days | Degree + % check |
| OA | 1 day | 90 min |
| Tech 1 + 2 | 5-7 days | Virtual common |
| Managerial | 2-3 days | Sometimes merged |
| HR | 1-2 days | Short |
| Offer | 2-3 days | Written letter wins |
| End to end | ~2-3 weeks campus often | Off-campus can stretch |
Matching habit (the explanation people skip)
Matching is not “ML assigns the best partner.” Say: job (time, geo, skill, duration) ↔ partner (skill, rating, location, availability). Name one constraint (travel time) and one failure (no-show). Interviewers want the chain. Silent “we would use AI” is the fail.
Example shape: score = skill match × rating × inverse distance, then a greedy assign with a re-try queue when a partner declines. Say you would measure accept rate and late arrivals. Stop at one bottleneck unless they ask you to refine.
Weekend mock
Saturday 10:00: 90-minute two-problem OA.
Saturday 12:00: rewrite the slower problem.
Saturday 16:00: 30-minute matching design with a friend who interrupts.
Sunday 11:00: one LLD class list.
Sunday 12:00: STAR + why-Urban-Company.
Two weekends of that beat collecting unread LLD PDFs.
Documents pack
10th, 12th, degree, ID, resume one page. Throughout 70% means the 12th PDF matters.
How interviews get scheduled
Campus: PPT → OA → shortlist → virtual loops. Off-campus: more resume noise. Screenshot the invite. If the PPT never mentioned aptitude, do not panic-build CAT. If it named HackerRank, run two timed sets on that UI.
After an OA mock, the only review that matters
Pick the problem you failed hidden tests on. Write three extra cases. Speak the approach. Re-reading 40 editorials you already got right is how people feel busy and still fail the second OA question.
Geo matching without a PhD
You do not need a GIS course. You need: store partner location, filter by radius (haversine or a grid approximation), rank by distance and rating, recompute when a partner moves. Say what you would do at 10 partners vs 10,000 (grid/geohash). That is fresher depth. Drawing a neural net is not.
Ratings without becoming Trust & Safety VP
Write path: after job complete, customer rates 1-5. Read path: show average on partner card. Abuse: revenge 1-stars, fake 5-stars. One control: only completed jobs can rate, plus a simple velocity limit. Stop. You are an SDE-1 candidate, not writing the 2027 policy.
Pair-sum follow-ups (from the VP round note)
If they generalise “two sum” to three arrays, clarify: distinct indices, target, duplicates. Start with sort + two pointers or hash. State O(n^2) vs better if sorted. Talk before you write nested loops you cannot finish in the remaining 15 minutes. The meeting feeling is the point: they want to work with you, not watch you panic-code.
Five rounds vs four
Some mailers merge managerial and HR. Some skip a design round for intern conversions. Do not memorise “exactly five.” Memorise OA then code then marketplace talk then stories.
Urban Company practice pages
Use the linked practice pages below. This hub stays the spine.
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant/logic if a mixed paper appears; still useful speed.
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.
A practical Urban Company prep plan
If a Urban Company 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 Urban Company 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): Candidate-reported floor is often 70% or 7.0 CGPA across 10th, 12th, and graduation. Degrees commonly listed: B.Tech/B.E./M.Tech in CS, IT, or related. Final-year and recent grads (within ~2 years); no active backlogs. Strong Python/Java/JavaScript plus DSA. Verify the notice.
What you are training for: Typical SDE loop: Online Assessment (~90 min, 2-3 medium coding) → Technical 1 (DSA, 45-60 min) → Technical 2 (marketplace system design / LLD, 45-60 min) → Managerial (behavioural + impact, ~45 min) → HR (~30 min). Some drives merge managerial with HR. About 2-3 weeks on many campus batches.
Short version of the prep split: Split time roughly 45% DSA (arrays, hashing, graphs, DP), 25% marketplace system design / LLD, 20% timed OA mocks, 10% STAR stories and Why Urban Company. Python is the usual OA language. Full plan: /urban-company/preparation-guide/.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Urban Company 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 Urban Company 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 Urban Company 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 Urban Company?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Star stories + one project walkthrough recorded on your phone. 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 Urban Company-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 Urban Company story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Urban Company 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 Urban Company papers on three different days, then interview prep on the leftovers.
How to train for Urban Company DSA and marketplace design
Week calendars live on the preparation guide. This H2 is the focus split.
Time split
| Bucket | Share | What “done” looks like |
|---|---|---|
| DSA + OA mocks | ~45% | Two problems in 90 minutes, tests green |
| Marketplace design / LLD | ~25% | One sketch with a failure mode |
| Timed contest hygiene | ~20% | Error log of speed vs concept |
| STAR + HR | ~10% | Why marketplace, city, CTC band |
If you only read High Scalability posts, stop for two weeks and sit OA mocks. If you only grind LeetCode easy, add one matching design so Tech 2 is not a blank stare.
This week
- One timed OA from coding questions.
- Ten medium DSA with an error log.
- One matching/booking sketch.
- One LLD class list (cab or LFU).
- One STAR with a number.
What not to waste time on
- Design blogs with zero OA
- 400 easy LeetCode without a 90-minute mock
- Quoting 35 LPA Amazon in HR
- “We will use Kafka and K8s” with no bottleneck
- Treating managerial as HR small talk
Two-week focus if the drive is soon
Week A: daily 90-minute two-problem set; one design sketch.
Week B: every other day full OA; one LLD with a friend; HR why-Urban-Company recorded twice.
How to say “why Urban Company” without a brochure
You want two-sided marketplace problems (partner quality, matching, on-time jobs), not a generic “consumer internet passion.” You will relocate to Gurgaon if the letter says so. You know the ₹18-25 LPA band and you will read ESOP footnotes. That is enough.
Design types worth a week, not a lifetime
You do not need 40 system-design videos. You need representatives:
- Matching (skill + geo + time)
- Booking (hold, confirm, cancel, no-show)
- Ratings (write path, abuse)
- LLD cab / task manager
- One surge / load idea at fresher depth
For each type, run a 20-minute sketch, then explain one to a roommate in 90 seconds.
OA hygiene they actually grade
Hidden tests punish off-by-one and empty input. Write three extra cases before submit. Python is fine; do not switch languages mid-OA. If you have 15 minutes left, add edge cases, not a third half-problem.
Night-before checklist
- Charger, ID, resume that matches projects you will defend
- One matching sketch on paper
- Two DSA patterns you always miss, rewritten
- STAR + city
- Sleep. Morning freeze on problem 1 is how 30-40% pass without you
What marketplace hiring means
Urban Company is not trying to be TCS and not trying to be Google. The DSA OA brand is real. The cab-LLD panel is also real. You can be a 7.0 or an 8.5; both still have to pass tests. You cannot outsource matching to a buzzword slide. You cannot skip OA because a senior said “they only do design.” Read your mailer. Then practise both.
If Urban Company, Swiggy, and Zomato all land the same week, compare DSA vs logistics design weight, city, and the letter. Do not pick on brand memory from a 2019 food-tech story.
DSA week that actually maps to the OA
You do not need 600 problems. You need representatives with timed reps:
- Prefix / two pointers / sliding window
- Hash maps (frequency, prefix sums)
- Heap / LFU cousin
- Graph BFS (shortest hops, not contest max-flow)
- DP on strings or knapsack family
For each, do three timed mediums, then explain one in 90 seconds. If you cannot explain it, you do not own it. Interviewers will ask a cousin, not the same LeetCode number.
Booking state machine you should draw once
requested → matched → en route → in service → completed, plus cancelled and no-show from several nodes. Say who can cancel, what refund means at fresher depth, and what you log. That drawing is more useful than naming six AWS services.
How hybrid and on-call actually get asked
Managerial may ask late-night incidents. Have one story: you watched a metric, you rolled back or you fixed a query, you wrote a note. If you have never done that, use a campus project outage (the fest site died, you checked logs). Inventing a FAANG on-call is an integrity fail.
Urban Company fresher CTC in India (2026)
Figures below are candidate-reported India bands (as of August 2026).
| Track | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Software Engineer | ₹18-25 LPA | Primary campus band |
| Senior SWE (indicative, 2-3 yrs) | ₹25-35 LPA | Not campus default |
| Tech lead (indicative) | ₹35-50 LPA | Experience |
| Product / backend mid (indicative) | ₹22-35 LPA | Role posts vary |
Confirm the written offer. ESOP, joining bonus, and variable language varies.
Benefits students actually care about
Health insurance, ESOP, learning budget, hybrid on many teams, meals, cab or allowance. Ask HR about joining location. Do not assume only Gurgaon WFH.
How to talk CTC in HR
Know ₹18-25 LPA and that ESOP is not cash. Ask how the package splits. One calm question beats a 40 LPA demand copied from a Telegram group.
Offer-stage discipline
- Read city and ESOP vest
- 10th/12th/degree % must match
- OA shortlist is not an offer PDF
Urban Company hiring updates for 2026
- DSA OA remains the door. 2-3 medium in 90 minutes.
- Marketplace design weight increased in student notes vs a pure second DSA round.
- Managerial still feels like a product meeting when it goes well (GFG quote).
- ₹18-25 LPA is the commonly cited fresher band; confirm the letter.
- Hybrid continues; location still asked.
Net for 2026: do not prepare as if this were Infosys aptitude or a bank OA. Pass the coding test. Talk matching.
ESOP in one honest paragraph
Student CTC bands often blend base, bonus, and stock. Stock is not cash on joining day. Vesting takes years. HR will not be impressed if you treat ₹25 LPA as a savings account. Ask how the offer splits. Compare base across Swiggy/Zomato/Urban Company if you have multiple letters. Do not compare headline CTC from a 2022 blog to a 2026 PDF.
Day-of OA checklist
Stable internet, charged laptop, one language picked, sample input tested in the first two minutes, notepad for brute-force ideas. If the platform allows custom test cases, add empty and already-sorted. If it does not, write them on paper and trace. Mute Slack. A 90-minute paper does not forgive a 12-minute “quick doubt” on WhatsApp. If power or the platform dies, screenshot the error and mail the recruiter with the time. Do not silently sit for 40 minutes hoping it “comes back.” Recoverable incidents are documented. Silent ones look like you quit. Keep the recruiter email from the invite in a note on your desktop before the test starts, not in a buried placement-cell PDF you cannot open while the timer runs. Save the OA link and login before the window, not at minute one.
Gurgaon vs other cities (why the letter wins)
Gurgaon is the story hub. Letters can name other locations or hybrid. Write a yes/no this week. Students who “will decide after the offer” stall joining.
Partner quality is the product
Urban Company sells a job done well, not a food ETA. Design talk should mention skill, rating, punctuality, and rework. If you only copy a food-delivery design, the panel will ask what is different. Answer: longer job duration, skill matching, and a no-show that wastes a customer’s evening. That one contrast is worth more than naming Redis.
How to use older UrbanClap write-ups
The GFG SDE-1 story is 2021 campus, updated 2024. Platforms and round names move. The habits stay: timed coding, LLD conversation, managerial as a meeting. Do not memorise the exact LFU prompt as if 2026 will paste it. Do memorise talking while you design. If a 2026 mailer adds an aptitude section, sit one mixed mock. If it does not, do not invent one.
Intern vs FTE loops
Intern conversions may skip OA or collapse HR. Still keep two STAR stories and a matching sketch. Campus FTE is the full funnel. Off-campus FTE is the full funnel plus more resume noise. Do not assume a referral skips HackerRank. Do assume a referral still needs passing tests.
What “discuss with the interviewer” looks like in the room
Say: “I would start with a hash from job id to partner id, then add a geo index if volume needs it. Is the bottleneck match latency or partner accept rate?” Wait. Let them pick. Then design that bottleneck. Students who deliver a 10-minute monologue without a question miss the whole GFG lesson. Students who ask “what should I do?” without a starting sketch also miss it. Start simple. Ask one fork. Continue.
FAQs students ask about Urban Company placements
Papers & process
Can I download Urban Company placement papers PDF for free?
What is the Urban Company placement process for freshers?
Typical path: 90-minute coding OA → DSA interview → marketplace design/LLD → managerial → HR. About 2-3 weeks on many batches.
How many rounds does Urban Company usually have?
Most fresher loops report 4-5. Some merge managerial and HR. Count the mailer.
What is the exam pattern?
Student-reported 90 minutes, 2-3 medium coding problems. Details: online assessment.
Eligibility & offer
What eligibility / CGPA do fresher drives usually expect?
Commonly 70% or 7.0 throughout; CS/IT B.Tech; no active backlogs. Your notice wins.
What is Urban Company fresher salary in India?
Candidate-reported SDE CTC often ₹18-25 LPA (as of August 2026). The written offer is the only number that matters.
Are active backlogs allowed?
Usually no at application. Cleared backlogs are commonly fine. Confirm the JD.
Prep & Urban Company-specific
How should I prepare?
Roughly 45% DSA/OA, 25% marketplace design, 20% timed mocks, 10% STAR/HR. Guide: preparation guide.
What languages can I use?
Python, Java, JavaScript, C++. Python is the most cited. Stick to one.
What design questions show up?
Partner matching, booking, geo, ratings, cab LLD, LFU-like task managers. Talk actors and failure modes.
Urban Company vs Swiggy vs Zomato?
Urban Company is home-services matching at a cited ₹18-25 LPA band. Swiggy is food/quick-commerce logistics. Zomato is food + discovery. Compare recent notes and letters.
Any pro tip that actually changes outcomes?
Two passing OA solutions first. Then one matching sketch you can discuss like a meeting. Do not wait for a perfect 300 LeetCode count.
Where can I read real interview experiences?
Urban Company interview experience plus the GFG notes in the stories section.
Should I skip DSA and only do LLD?
No. OA is the funnel. LLD can strand you later. Do both at fresher depth.
What recent candidates reported
SDE-1 on-campus, then UrbanClap (GFG, updated Apr 2024)
Campus visit November 2021, Day-0. 1.5-hour coding test plus three one-hour interviews. LFU-like task manager, driverless cab LLD, VP Engineering managerial with multi-array pair-sum generalizations. “At all points, I felt as if I were in a meeting with interviewers to design new products for the company.” Source: GeeksforGeeks Urban Company SDE-1.
Takeaway: talk like a collaborator. Silent perfect class diagrams are worse than a messy sketch you discuss.
Same loop, Interview 2
Software Engineering Manager asked for a driverless cab booking app: classes, data members, member functions from requirements. Process lesson: “The important thing was to be a little creative and discuss all your ideas with your interviewer so that he/she can guide you while going forward.”
Takeaway: LLD is a conversation. Start simple. Add surge or no-show when they ask.
Composite 2025 notes
What helped: passing OA tests, talking before coding, one matching failure mode. What hurt: design jargon without a bottleneck; treating managerial as HR; quoting another company’s CTC.
After you clear OA
- Re-work every failed hidden test.
- One matching sketch.
- One LLD class list.
- Two STAR stories.
- Sleep and city answer. Do not open a new ML course.
Mini matching close you should be able to run cold
Assign a beauty job at 6pm in a 5 km radius.
- Filter partners by skill + availability + geo.
- Score rating, distance, last-job fatigue.
- Offer top 1-3; timeout; fallback.
- Track accept and on-time.
- Risk: always picking the same 4.9 star and burning them out.
That is an SDE-1 close. A 12-slide “AI marketplace OS” pastiche is not.
LLD cab rubric (from the GFG note)
Start with objects: Rider, Driver, Trip, Location, Pricing. Methods: requestRide, matchDriver, start, end, cancel. Then add one wrinkle they ask (surge, no-show, multiple stops). Do not open with Kafka. Do not freeze because you never “practised this exact prompt.” Discuss. Let them steer. That was the candidate’s actual lesson.
LFU-like task manager: capacity, get/put, eviction of least frequently used, tie-break. HashMap + frequency lists is the expected shape. Talk complexity before you code. If they generalise to pair-sums across arrays, clarify constraints and start with a sort or hash, not a triple nested loop you cannot finish.
Managerial as a product meeting
The GFG quote is the rubric: you are designing with them, not performing a viva. Bring a metric from a project (p99, conversion, crash rate). Bring a conflict you resolved without villainising a teammate. Bring a “what I would rebuild.” Empty “I am a team player” is how people look junior after a strong LLD.
Python OA hygiene
Prefer clear loops over clever one-liners that fail a type. Watch recursion limits. Convert input the way the platform shows in the sample. If the problem is DP, state the state and transition in a comment, then code. Hidden tests love empty arrays and already-sorted input.
More narratives: Urban Company interview experience.