Academic snapshot
Floor: Often 6.5 / 65%
Degrees: B.E./B.Tech/M.Tech/MCA
Backlogs: None active
Gap: Max ~1 year documented
Paytm Placement Papers 2026
Paytm is a leading Indian digital payments and financial services company known for its mobile wallet, UPI, and ecommerce products. Founded in 2010, it serves hundreds of millions of users across payments, banking, and commerce. Paytm recruits engineers for fintech platforms, mobile apps, and large-scale transaction systems.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Paytm eligibility & CGPA (2026)
Paytm does not always publish one universal national CGPA cutoff. What students see depends on campus JD wording vs careers portal / contest posts. Treat numbers below as candidate-reported (as of August 2026).
Who this hub is for
- For: Students targeting SDE-1 / Software Engineer roles on Paytm’s payments and fintech platform teams.
- Also useful: Intern+FTE and some DevOps/QA fresher loops (coding + SQL/OOPs flavour differs - read the invite).
- Not the same track: Pure business / sales roles, or assuming Paytm OA equals PhonePe OA.
Degree, projects, and “is 6.5 enough?”
Yes - 6.5 / 65% meets the commonly reported floor on many posts. It is not a selection guarantee. A 6.7 with two fully passing OA solutions and a clear idempotency story beats an 8.5 who freezes on graphs.
Projects that help: APIs, transactional workflows, wallets/ledgers (even toy), concurrency, or data integrity. Certificate stacks with zero systems talk rarely impress Round 2.
On-campus vs off-campus vs contests
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA window, PPT timing, college CGPA list when printed | Coding bar, interview depth |
| Careers portal / referral | Resume screen volume | Still expect OA + tech loop |
| Tech Hunt / hackathons | Alternate visibility into the funnel | You still defend DSA and design |
| Intern → FTE | Conversion may shorten stages | You still defend projects and code |
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 6.5+ CGPA / ~65% across 10th, 12th, graduation | 7.5+ is a more competitive shortlist band |
| Degree | B.E./B.Tech/M.E./M.Tech/MCA | Related computing degrees on many posts |
| Branch | CS, IT, ECE, EE (and related) | Strong DSA can help adjacent branches |
| Year | Final year + recent grads (~1 year) | Intern conversion paths also appear |
| Backlogs | No active backlogs | Clear before selection/joining |
| Gap years | Often max ~1 year | Full-time degrees preferred |
| Languages | Java, C++, Python, Go | Stick to one for OA + interviews |
Skills & focus
Primary: Medium-hard DSA
Secondary: Payments system design
First filter: Timed OA (90-120 min)
Differentiator: Ownership + customer-impact stories
Selection feel by CGPA band
| CGPA range | Rough chances | Reality check |
|---|---|---|
| 6.5-6.9 | Meets many reported floors | Need strong OA |
| 7.0-7.4 | Safer competitive band | Helps resume screen |
| 7.5-8.0+ | Stronger early shortlist odds | OA/interviews still decide |
| Below printed floor | Often filtered before OA | Focus on drives where you qualify |
Paytm placement papers - last few years
Download 2026 Paytm placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What Paytm previous year papers actually train
Paytm does not publish one permanent official paper set. “Previous year papers” on this site are pattern trainers for OA and early technical rounds - not leaked live assessments.
| Round (typical) | What to practice |
|---|---|
| Online assessment | Timed accuracy on 2-3 DSA problems + debugging stamina |
| Technical interviews | Live coding narration + payments design at fresher depth |
| Managerial / Team Fit | Customer focus, innovation, ownership STAR stories |
| HR | Why Paytm, location, CTC, joining logistics |
Themes that keep repeating (2024-2026)
- 2024 cycles: OA stayed coding-heavy with occasional debugging. Arrays, trees, graphs, and DP dominate. Wallet / payment gateway design appears in SDE interviews. Students who only drilled Easy problems lost the shortlist.
- 2025 loops: Stronger pressure on runnable code with complexity analysis in shared IDEs. Team Fit remains mandatory in many SDE stories. SQL still shows up on some intern/DevOps tracks.
- 2026 prep expectation: Keep medium-hard DSA warm, add payments reliability vocabulary (idempotency, retries, reconciliation), and rehearse values stories. Treat PDF packs as pattern catalogs.
How to use one paper set in a single sitting
- Timed: run a full 90-120 minute mock with 2-3 coding prompts (+ one debugging pass if present).
- Untimed review: rewrite the cleaner solution; list three money-related edge cases (duplicate txn, partial failure, empty batch).
- Map each miss to a theme and pull cousins from coding questions.
- Spend 15 minutes explaining a payment gateway happy path + one failure out loud.
- Log one STAR story mapped to customer focus / ownership / innovation.
Related problems to practice
| Theme you saw in a set | What to drill next | Why Paytm asks it |
|---|---|---|
| Max subarray / sliding windows | Kadane + windows | Stream / txn windows |
| Shortest path | BFS / Dijkstra | Routing / graph modelling |
| Coin change / DP | Classic DP templates | Wallet denomination intuition |
| Duplicate events | Hashing + windows | Idempotent payment intents |
| Settlement min transfers | Graph modelling | Ledger simplification |
| Rate limiter | Sliding window counters | API abuse protection |
2025 PDFs often drill “settle balances with min transfers.” Own the graph modeling template, then drill a related problem with fees or partial settlements. That transfers to interviews; memorising the story text does not.
What a good Paytm PDF is for
Students search “Paytm previous year paper PDF download” expecting a leaked HackerRank set. Useful packs instead give you timed DSA cousins, debugging practice, and payment design prompts. Ignore Telegram “exact OA with 92% cutoff” claims - Paytm does not publish those numbers.
Papers section - year cards are maps, not prophecies
When you open /paytm/2024/, /paytm/2025/, or /paytm/2026/, read them as theme guides. Salary bands on year pages can drift versus the hub’s ₹16-22 LPA fresher band - prefer the hub range for expectation-setting and the year page for question flavour.
Mock review ritual (15 minutes after every OA sim)
- Which problem did you start, and why?
- First failing test case you missed?
- Complexity you claimed vs what you coded?
- One payments edge case you never considered?
- One STAR story the frustration reminded you of?
Write answers in an error log. Next week’s plan comes from that log, not from random LeetCode daily.
Paytm hiring rounds in 2026
Paytm hires freshers through campus placement cells, the careers portal, referrals, Tech Hunt / hackathons, and internship conversion. After resume screen, the shape is product-fintech: timed OA, DSA, payments design, Team Fit, then HR.
Application methods
Campus recruitment
Through college placement cells - PPT, then OA and interviews on a batch timeline.
Careers / contests
Apply on Paytm careers; watch Tech Hunt, hackathons, and coding contests for alternate entry.
Referrals
Employee referrals improve visibility. You still need passing OA code and clear interviews.
1. Resume / eligibility screen
Placement cell or recruiter checks degree, CGPA floor when printed (6.5+ / 65% commonly reported), backlogs, and year of passing. Internships and systems-flavored projects help when volumes are high. This is a gate - OA coding is the hard filter.
2. Online coding assessment - 90-120 min
Candidate reports commonly describe 2-3 DSA problems on HackerRank or Paytm’s internal tool, sometimes with debugging prompts. Advance rates in chatter sound harsh (teen percentages) - normal for product fintech.
| Component | Typical shape (reported) | Focus |
|---|---|---|
| Coding problems | 2-3 DSA | Arrays, trees, graphs, strings, DP |
| Debugging | Occasional | Find/fix bugs under time |
| Duration | 90-120 min | Full solutions + edge cases |
| Languages | Java, C++, Python, Go | Confirm invite list |
Student tip: Skim all prompts in 5 minutes. Bank two clears before chasing a glamorous hard. Candidate chatter often cites ~10-15% advancing from OA - use that as motivation for mocks, not despair.
Example timing for a 120-minute OA
| Minute | Move |
|---|---|
| 0-5 | Skim all statements; mark easy wins |
| 5-50 | Fully solve problem 1 with tests |
| 50-95 | Solve problem 2; protect edge cases |
| 95-120 | Problem 3 or debugging; harden tests if 1-2 are solid |
Deeper OA notes: Paytm Online Assessment.
OA sample themes
- Maximum sum subarray / window aggregates on txn streams
- Shortest path in a graph of payment nodes
- Minimum coins / DP wallet-style prompts
- Deduplicate transaction IDs inside window W
- Detect cycles in a payment relationship graph
3. Technical interviews - 2-3 rounds (~45-60 min each)
Shared editor or Google Meet IDE. Expect DSA live coding, complexity narration, project deep-dives, and for SDE-1/2 depth: payment gateway / wallet design.
You should:
- Clarify constraints (money as integers, duplicates, timeouts)
- Narrate brute → optimize
- Write runnable code when asked
- Walk edge cases and complexity
Worked mini-outline - payment gateway collect:
- Actors: payer app, Paytm-like switch, bank/UPI rail, merchant.
- Happy path: create intent → call rail → mark success → credit ledger.
- Failure: timeout after debit unknown → idempotent retry with same key.
- Consistency: at-least-once with dedupe vs exactly-once dreams - say what you can build as a fresher.
- Observability: correlation IDs, reconciliation jobs, mismatch alerts.
Worked mini-outline - wallet transfer:
- Actors: sender wallet, receiver wallet, ledger service.
- Happy path: lock/check balance → debit → credit → emit receipt.
- Failure: credit fails after debit → compensating credit or saga step.
- Concurrency: optimistic versioning vs row locks - pick one and defend.
- Audit: immutable ledger entries beat “update balance only.”
Why Paytm OA feels harder than services coding rounds
Services coding often rewards one clean array problem. Paytm OA expects medium-hard thinking under 90-120 minutes, sometimes with debugging. Students who only practised Easy problems hit TLE or incomplete second prompts. Train with back-to-back mediums weekly so the real OA tempo feels familiar.
Candidate chatter about harsh OA shortlist rates is normal for product fintech. Your control knob is mocks and error logs.
4. Managerial / team fit - ~45 min
Paytm values: customer focus, innovation, ownership. Scenario questions on ambiguity, teamwork, and leadership. Light technical follow-ups appear. Use STAR with metrics.
5. HR / offer - ~20-30 min
Why Paytm, location (Noida / Bengaluru / other), joining vs exams, CTC context around ₹16-22 LPA, benefits/ESOPs. Ask one real question about team surface (payments, wallet, lending, commerce).
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | OA (coding) | 90-120 min | Timed DSA + debugging |
| 2 | Technical (2-3) | 45-60 min each | Code + payments reasoning |
| 3 | Team Fit | ~45 min | Values + ownership |
| 4 | HR | 20-30 min | Logistics + motivation |
Some drives merge later rounds. Trust the invite.
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT then OA window |
| OA → shortlist | Days to a week | Competitive pools |
| Technical loop | 1-2 weeks | Multiple tech rounds |
| Team Fit + HR | Often same cluster | Values + logistics |
| Offer / paperwork | 2-3 days common | Written offer wins |
| End to end | ~2-4 weeks | Off-campus can stretch |
Sample coding patterns
Drill arrays/windows, graph BFS, and classic DP (coin change style). Narrate complexity every time. Prefer clean code over clever one-liners in interviews.
Payment gateway and wallet engines: data model, APIs, concurrency, retries, reconciliation. Start with requirements, not Kafka.
Customer focus = solved a user pain with a metric. Ownership = you took responsibility when something broke. Innovation = simpler approach that worked.
Managerial / team fit - what “customer focus” sounds like
You do not need a fintech internship. You need a story where a real user (classmate, club member, app user) had friction, you fixed it, and you can measure the outcome. Empty “I care about customers” lines get challenged. Rehearse a 90-second version and a 3-minute version.
OA pattern cheat-sheet
| Component | Focus | Prep move this week |
|---|---|---|
| Coding Q1-Q3 | Arrays, trees, graphs, DP, hashing | Two timed mediums back-to-back |
| Debugging | Read failing tests carefully | Fix one broken snippet daily |
| Design follow-ups | Idempotency, retries, ledger | Explain one flow in 3 minutes aloud |
| Team Fit | Customer focus, ownership, innovation | Two STAR stories spoken |
| HR | Why Paytm, location | Noida/Bengaluru answer ready |
Paytm 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.
Where your Paytm prep time should go
If a Paytm 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 Paytm sits around ₹16-22 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): Paytm eligibility for freshers 2026 is candidate-reported: often 65% or 6.5+ CGPA across 10th, 12th, and graduation; B.E./B.Tech/M.E./M.Tech/MCA in CS, IT, ECE, EE or related fields; final-year students and recent graduates; no active backlogs; max ~1 year gap on many notices. Strong DSA decides shortlists after the academic screen. Always verify your drive notice or Paytm careers post.
What you are training for: Paytm fresher SDE loops commonly run: Application / resume screen → Online Coding Assessment (90-120 min, 2-3 DSA problems plus occasional debugging) → 2-3 Technical interviews → Managerial / Team Fit → HR / offer. Total timeline is often 2-4 weeks.
Short version of the prep split: Split time roughly: 50% DSA, 20% system design / OOP for payments, 20% Paytm values STAR stories (customer focus, innovation, ownership), 10% aptitude/communication. Solve 100+ mediums and take weekly 90-120 min OA mocks.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Language fluency: rewrite 10 old solutions in one language until you stop hunting syntax. Open the Paytm 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 Paytm 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 Paytm 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 Paytm?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Sleep, id photocopies, and a dry run of the oa platform if the invite names one. 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 Paytm-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 Paytm story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Paytm 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 Paytm 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 Paytm papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Paytm-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 Paytm 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 Paytm. 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 Paytm, 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 Paytm mistakes, you are collecting content, not preparing.
Extra drill block (1)
Sit one more mixed Paytm 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.
Paytm fresher CTC in India (2026)
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on role, location, and written components. Paytm does not officially publish these midpoints.
Software engineer bands students ask about
| Level | Experience | Typical total package (reported) | Notes |
|---|---|---|---|
| SDE-1 | New grad | ₹16-22 LPA | Primary fresher band for this hub |
| SDE-2 | ~2-4 years | ₹24-30 LPA | Outside fresher default |
| Senior SDE | ~5-8 years | ₹40-55 LPA | Outside fresher default |
Other roles
| Role | Typical reported band | Notes |
|---|---|---|
| QA Engineer | ₹7-12 LPA | Testing / automation focus |
| DevOps (entry-mid) | ₹8-18 LPA | Cloud / CI-CD stories |
| Data / PM tracks | Wide bands | Follow that JD |
Confirm base, bonus, ESOP, and benefits on the written offer.
Benefits students actually care about
- Health insurance
- ESOPs for many engineering bands
- Learning / internal training
- Hybrid options on some teams
- Wellness / assistance programs
How to talk CTC in HR
Know the ₹16-22 LPA fresher context, ask for the written breakup, and clarify joining vs exams. One calm question beats aggressive negotiation with no market anchor.
Base vs bonus vs ESOP literacy
When HR shares a number, ask:
- What is fixed vs variable?
- Is ESOP included in the headline CTC?
- What is the joining bonus (if any) and clawback?
- Which city is the offer for?
Do not argue midpoints from placement WhatsApp groups. The written letter is the only number that matters for your decision.
Paytm hiring updates for 2026
- Virtual OA + interviews remain the default for many drives.
- Debugging / scenario prompts appear more often in OA chatter.
- Team Fit is treated as mandatory in many SDE stories - do not skip values prep.
- Tech Hunt / student programs remain useful alternate visibility paths.
- Treat ₹16-22 LPA as a reported SDE-1 band, not a promise for every college.
- Compared with PhonePe hubs, Paytm fresher chatter often sits slightly lower on CTC midpoints - compare written offers, not memes.
What “ownership” means for freshers
You do not need a production pager story. You need a college example where you noticed a risk, did something concrete, and measured the outcome. Paytm moves money - panels listen for whether you hide bugs or surface them early.
Documents and portal hygiene
- Keep academic marks consistent with the careers form - BV catches typos.
- Screenshot invite duration, platform, and language list.
- For contest paths (Tech Hunt), still treat the later OA/interviews as the real exam.
- If you have internship NDAs, prepare a public project narrative you can defend.
Networking and referral note
Referrals improve resume visibility; they do not skip coding bars. Prepare as if the OA is unchanged - because it is.
Contests as a side door, not a shortcut
Paytm Tech Hunt and hackathons can get your resume noticed. They do not replace medium-hard DSA. If you place well in a contest, still run full OA mocks the week before interviews - the problem distribution and IDE constraints differ from contest platforms. Treat contest wins as confidence, not as proof you can clear a 120-minute campus OA without practice this week.
Common questions about Paytm hiring
Process & papers
What is the Paytm placement process for freshers?
Typical SDE path: Application screen → Online Coding Assessment (90-120 min) → 2-3 Technical interviews → Managerial/Team Fit → HR/offer. Timeline often 2-4 weeks.
How many interview rounds does Paytm usually have?
Most fresher loops report about four major stages (OA, technical cluster, Team Fit, HR), with 2-3 conversations inside the technical stage. Count the mailer.
Can I download Paytm placement papers PDF for free?
Yes. Free Paytm placement papers PDF and 2024-2026 style practice sets are on this site. Start with the 2026 PDF or the paper archive.
What does the Paytm OA look like?
Candidate-reported formats: 2-3 DSA problems in 90-120 minutes, sometimes with debugging. Focus arrays, trees, graphs, strings, DP. Aim for fully correct optimal solutions.
Eligibility & offer
What eligibility / CGPA do fresher Paytm drives usually expect?
Commonly reported: 6.5+ CGPA / 65% across academics, CS/IT/ECE/EE (related), no active backlogs, max ~1 year gap. Your drive notice overrides this page.
What is Paytm fresher salary in India?
Candidate-reported SDE-1 CTC often lands around ₹16-22 LPA (as of August 2026). Confirm the written offer.
Do I have to relocate?
Common hubs include Noida and Bengaluru. Hybrid options appear on some roles. Be honest about preference early.
Prep & Paytm-specific
How should I prepare for Paytm?
Split time roughly 50% DSA, 20% design/OOP, 20% values STAR, 10% aptitude/comms. Details: preparation guide.
What languages can I use?
Typically Java, C++, Python, Go. Pick one you can debug live under time pressure.
Paytm vs PhonePe vs Razorpay - how should I choose?
Choose by domain and written offer. Compare hubs: PhonePe · Razorpay. Paytm fresher chatter often cites ~₹16-22 LPA; others may differ by year and role.
Does Paytm hire via hackathons?
Yes - Tech Hunt and similar contests appear in candidate reports as visibility paths. Coding and interview bars still apply afterward.
Are Paytm placements only for CS/IT?
Primarily CS/IT/ECE/EE with strong programming. Other branches sometimes appear when the notice allows exceptional coding profiles - read the JD.
Any pro tip that actually changes outcomes?
Clear two OA problems fully before chasing a third hard. Keep an error log. Rehearse one payment-flow design aloud weekly. Prepare Team Fit STAR stories for customer focus, innovation, and ownership early.
Where can I read real interview experiences?
Start with Paytm interview experience on this site, then cross-check reputable public write-ups. Use them as maps, not scripts.
What recent candidates reported
On-campus SDE intern+fte (2025)
In March 2025, an ABES on-campus SDE Intern+FTE candidate cleared resume shortlisting then a technical assessment with three medium coding problems plus two SQL queries; “After a week, the results were declared, and the technical interview was scheduled,” with two virtual Google Meet coding rounds where the interviewer shared an IDE and required runnable C++ with complexity analysis (Medium).
Transferable takeaways: SQL can appear beside DSA; expect runnable code and complexity talk; timelines can include a week between OA and interviews.
Devops intern colour (2024)
A 2024 on-campus DevOps Intern candidate for Paytm Noida described a fully virtual funnel on GeeksforGeeks: resume shortlist, then a 60-minute round with SQL, Java OOPs, and DSA. In the first technical interview they wrote, “I was extremely nervous and stumbling in answering the first question itself, the interviewer told me not to worry and to take as much time as I wanted.” A tech+managerial round on CI/CD and cloud followed two hours later; verdict: selected.
Transferable takeaways: Non-SDE tracks still probe fundamentals; interviewers may give you space if you stay structured; same-day clustered rounds happen.
After you clear OA - waiting-week plan
- Two timed mediums every other day.
- Rewrite two STAR stories mapped to customer focus / ownership.
- Sketch payment gateway collect with one failure mode.
- Practice runnable code + complexity narration in your OA language.
- Sleep and location preference (Noida / Bengaluru / other).
Experience story bank
| Story type | Prompt you should answer | Metric to include |
|---|---|---|
| Customer focus | Solved a user pain | Before → after |
| Ownership | Took responsibility when something broke | What you fixed |
| Innovation | Simpler approach that worked | Time/cost saved |
| Ambiguity | Unclear requirements | How you scoped |
| Conflict | Disagreement on approach | Resolution |
Mini OA drill students should rehearse cold
Prompt: Deduplicate payment intents that share the same idempotency key inside a sliding window W, keeping the first success.
- Clarify: late events, clock skew, success vs failure precedence.
- Brute: store all events and scan - too slow / too memory-heavy.
- Better: hash map of key → status with window eviction.
- Edges: empty stream, duplicate successes, failure then success.
- Say complexity before coding.
What hurt other candidates
- Perfect CGPA with weak OA timing
- Design buzzwords without failure modes
- Team Fit stories with no metrics
- Arguing CTC from Telegram groups
- Ignoring debugging practice until it appears live
More narratives: Paytm interview experience.