Academic snapshot
Marks: 70% or 7.0+ CGPA (when listed)
Degree: B.Tech/B.E./M.Tech CS/IT/Electronics/related
Year: Final year + recent grads (~1 year)
Backlogs: None active preferred
Razorpay Placement Papers 2026
Razorpay is India’s leading fintech company for business payments, founded in 2014 by Harshil Mathur and Shashank Kumar. It offers payment gateway services, business banking, and related financial products used by millions of merchants. Engineering culture leans developer-friendly APIs and high-scale transaction systems.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Who can apply to Razorpay in 2026?
Razorpay hires like a product fintech, not a service-company mass drive. The printed CGPA floor gets you into the funnel; the 90-minute OA and payment-design talk decide whether you see an offer.
Who this hub is for
- For: Final-year and early-career engineers targeting Software / Product Engineer roles on payments, banking rails, and merchant APIs.
- Not the same bar: Pure sales, support, or non-engineering marketing roles - different funnels entirely.
- Intern paths: PSE Intern and similar tracks still run resume-driven technicals; only list stack keywords you can defend (Kafka, PostgreSQL, Spring) in depth.
Degree, CGPA, and branch reality
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 70% or 7.0+ in 10th, 12th, graduation when listed | Higher GPA helps resume screen; OA still decides |
| Degree | B.Tech / B.E. / M.Tech in CS, IT, Electronics, or related | Circuital branches appear when DSA is strong |
| Backlogs | None active at application / joining | Clear before offer paperwork |
| Experience | Freshers and ~0-2 years | Intern → full-time / PPO tracks also appear |
| Languages | Python, Java, C++, Go | One deep language for OA + interviews |
| Gaps | Max ~1 year on many notices | Full-time degrees only |
Is 7.0 enough? It matches the commonly reported floor. A 7.1 with clean timed coding and a crisp payment-gateway story beats an 8.8 that freezes on graphs. Razorpay values technical depth alongside academics - treat CGPA as a gate, not a scoreboard.
Gaps: Short gaps are easier to explain with projects or an internship story than silence. Full-time degrees only on most notices.
Skills bar
Primary filter: Medium-hard DSA under time
Interview differentiator: Payment system design
Languages: Python, Java, C++, Go
Hub: Bengaluru (hybrid norms vary by team)
Who usually fits and who struggles
Good fit: You enjoy medium-hard LeetCode-style problems, can talk about idempotent payment APIs and failure retries without jargon soup, and have one project you can defend for 20 minutes. Comfort with Bengaluru relocation helps.
Harder path: You only practiced aptitude MCQs; you skip system design because “freshers don’t get design”; you cannot explain your own project’s data model. Razorpay’s OA clear rate is often cited around ~10-15% - guessing through edge cases fails quietly.
Campus shortlists vs off-campus reality
Razorpay’s campus volume is not Infosys-scale. Some colleges see a drive; many students enter through careers, referrals, or hackathons. That changes psychology:
- Fewer seats means OA cutoffs feel harsher even when the problem set looks “fair.”
- Referrals improve the chance a human reads your resume; they do not soften hidden tests.
- Hackathons / contests can shorten the invite queue but still expect you to defend code and design.
- Intern conversion / PPO may skip a stage but still expects deep resume defense.
If your college does not have Razorpay on the calendar, start a careers + referral + hackathon plan early. Waiting for a PPT that never comes is how a year disappears.
Building payment intuition without a fintech internship
You do not need a payments internship to clear Round 2. You do need vocabulary backed by diagrams:
- Read Razorpay’s public product surfaces (Checkout, Payment Links, X banking) as a merchant and note trust/friction points
- Sketch how a payment might move through API → auth → capture → settlement → webhook
- List three failure modes (duplicate webhook, partial capture, settlement mismatch)
- Propose one metric per failure mode
Do this once a week for a month. Interviewers can tell the difference between someone who watched a 40-minute YouTube system-design video and someone who thought about money movement.
Coding themes mapped to Razorpay OA
| Theme | Why Razorpay-like OAs use it | Cousin drills |
|---|---|---|
| Hash maps | Frequency, first unique, anagrams | Two-sum family |
| Two pointers / sliding window | Subarray constraints | Longest substring variants |
| Trees / BST | Hierarchical data | LCA, validate BST |
| Graphs | Relationships, dependencies | BFS shortest, cycle detect |
| DP | Optimization under constraints | Knapsack light, LIS, string DP |
After every mock miss, pull two cousins from the same family on coding questions. Theme repetition beats random hard problem hopping.
Behavioral signals Razorpay managers notice
Beyond STAR templates, managers listen for:
- Ownership language (“I drove” vs “we were told”) without stealing credit
- Merchant empathy for developer experience, not only backend cleverness
- Trade-off honesty (“we shipped X knowing Y debt”)
- Learning speed when they change the problem mid-discussion
- Resume honesty - listing Kafka you never used is a common reject story
Practice one story where you were wrong and corrected course. Perfect-hero stories sound fake.
Offer-stage checks
If you clear HR:
- Read equity vesting and location clauses carefully
- Confirm hybrid expectations with the hiring manager if possible
- Do not resign from another offer until the written Razorpay letter lands
- Background verification expects consistent CGPA and employment dates
Excitement is fine. Process discipline still matters at startups.
Razorpay placement papers - last few years
Download 2026 Razorpay placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What Razorpay previous year papers actually train
Razorpay does not publish a permanent official paper bank. Sets on this site are pattern trainers for the OA and early technical rounds - not leaked live assessments.
| Round (typical) | What to practice |
|---|---|
| Online assessment | 90-min stamina on 2-3 medium-hard coding problems (arrays, strings, DP, graphs) |
| Technical 1 | Live DSA narration: brute force → optimize → edges |
| Technical 2 | Payment design: gateways, webhooks, distributed systems, merchant APIs |
| Managerial / HR | Impact stories, Why Razorpay?, Bengaluru / hybrid logistics |
Themes that keep repeating (2024-2026)
- 2024: Dynamic programming on arrays/strings, graph BFS/DFS, and interview emphasis on payment-domain vocabulary. Students who only drilled unsorted “random hard” without timed 90-minute blocks lost easy marks on incomplete solutions.
- 2025: More notes stress optimization and edge-case completeness - partial brute force that fails hidden tests is a common reject story. Design chats lean toward scalable payment and settlement systems. Resume keywords get probed hard in intern and PE loops.
- 2026 prep expectation: Keep medium-hard DSA warm; expect design rounds for many SWE tracks, not only seniors. Some Product Engineer paths mix MCQs + two LeetCode mediums before Java/Spring technicals. AI chatter appears in product talk - do not replace DSA with buzzwords.
How to use one paper set in a sitting
- Timed: 90 minutes, 2-3 problems, same language as test day.
- Untimed review: rewrite the cleaner solution; list three edges you missed.
- Map each miss to a theme (DP / graph / two pointers) and pull cousins from coding questions.
- Spend 20 minutes sketching a payment retry or webhook idempotency design aloud.
- Log one STAR story the session reminded you of (outage, ownership, conflict).
Razorpay placement process, round by round
Razorpay hires through campus, careers portal, referrals, and hackathons. Major campus volume still clusters in placement season (often August-December); off-campus and referrals run more continuously. Same technical bar either way - referrals mainly improve resume visibility.
How to apply
Campus
Placement cell PPT → resumes → OA → onsite/virtual interviews. Season-aligned slots.
Direct apply
Razorpay Careers with resume + portfolio. Resume screen then OA invite when roles are open.
Hackathons / referrals
Contests and employee referrals can shorten the queue; you still clear the same OA and design bar.
Round-by-round walkthrough
-
Online Assessment - 90 minutes
Section Questions Time Difficulty Focus Coding 2-3 90 min Medium-Hard Arrays, strings, DP, graphs, trees Platform is often HackerRank or Razorpay’s internal tool. No negative marking. Hidden tests punish skipped edges. Languages: Python, Java, C++, Go. Candidates commonly report ~10-15% clear this stage.
Time boxing: lock one “sure” problem first, then invest in the second for a clear bar, then attempt the third. Two clean ACs with complexity notes beat three half-broken solutions.
-
Technical Interview 1 - ~45 minutes
1-2 live coding problems: DSA, arrays/strings, trees/graphs, DP. Interviewers watch approach, code quality, communication, and edge handling. Roughly 40-50% of OA survivors advance in student reports.
-
Technical Interview 2 - ~45 minutes
Payment system design and project deep-dive: payment gateway, transaction processing, distributed systems, APIs, databases. They care how you trade consistency vs availability, handle duplicate webhooks, and explain your past work. About 50-60% of Round 1 survivors move on in many write-ups.
-
Managerial Round - ~45 minutes
Behavioral + light technical ownership: impact, collaboration, conflict, Razorpay culture fit. Success often cited around 60-70% of Round 2 candidates.
-
HR - ~30 minutes
Background, Why Razorpay?, compensation discussion, Bengaluru/hybrid logistics. Most candidates who reach HR with clean prior rounds receive offers if location and integrity checks pass (~80-90% in optimistic student tallies).
Timeline from application to offer
| Phase | Duration | What happens |
|---|---|---|
| Application & screening | 3-5 days | Resume review |
| Online assessment | 1 day | Coding test + evaluation |
| Technical interviews | 5-7 days | Round 1 + Round 2 scheduling |
| Managerial | 2-3 days | Behavioral + ownership |
| HR | 1-2 days | Offer discussion |
| Result | 2-3 days | Offer letter / onboarding |
Total: often 2-3 weeks once you are actively in process (faster for strong candidates). Product Engineer and intern funnels can feel denser on resume probing even when calendar days look short.
What interviewers listen for
- OA: Correctness first, then complexity. Narrate assumptions in comments if the platform allows.
- Design: Actors, APIs, data stores, failure modes - not buzzword architecture diagrams.
- Projects: Metrics and trade-offs. “We used Kafka” without why is a red flag.
- Managerial: Ownership language. Impact over title-dropping.
Managerial round: impact language that works
Razorpay managerial interviews reward specificity. Weak answers sound like campus training slides (“I am a team player”). Stronger answers sound like shipping logs:
- “We cut p95 latency on X from 800ms to 320ms by …”
- “A payment webhook retried twice and double-credited; I added idempotency keys and a reconciliation job …”
- “Two teammates disagreed on schema; I proposed a migration plan with rollback …”
Prepare three impact stories with numbers. If you lack production metrics, use project metrics (error rate in tests, load-test RPS, user count in a college deployment). Fake metrics are worse than honest small numbers.
Contests, referrals, and intern funnels
| Path | What changes | What stays hard |
|---|---|---|
| Campus | Batch OA windows | Medium-hard DSA |
| Careers + referral | Resume visibility | Same OA/design bar |
| Hackathon shortlist | Faster invite | Design + ownership talk |
| PSE Intern / PE tracks | Resume keyword probing | Defend every stack claim |
If you are contest-strong but design-weak, start payment sketches now. If you are design-strong but slow on OA, your referral will not save a failed hidden-test suite.
Comparing Razorpay to other fintech prep
| Company vibe | Prep you can reuse | What to add for Razorpay |
|---|---|---|
| PhonePe / Paytm | DSA volume | Merchant API / B2B payment sense |
| CRED | Payments vocabulary | Gateway + settlement depth vs rewards UX |
| Flipkart/Swiggy | Medium-hard OA stamina | Idempotency / ledger design |
Reuse DSA ruthlessly. Do not reuse a generic “I love fintech” HR answer - Razorpay interviewers have heard it all week.
Study resources on this site
- Online assessment for format notes
- Coding questions for theme cousins after each mock miss
- Interview experience for round flavor
- Preparation guide for longer week plans
- Year pages (2024, 2025, 2026) when you want annotated solutions
Download the 2026 PDF for offline timed runs when your hostel Wi-Fi dies mid-mock - it happens.
Where to practise for Razorpay
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 Razorpay this season
If a Razorpay 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 Razorpay 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): Razorpay eligibility for freshers 2026 (from student reports): typically 70% or 7.0+ CGPA in 10th, 12th, and graduation; B.Tech/B.E./M.Tech in CS, IT, Electronics, or related; final-year students and recent grads (within ~1 year); no active backlogs; max ~1 year gap; full-time degrees only. Strong DSA and payment-systems design help after the academic gate. Verify on Razorpay Careers or your campus JD.
What you are training for: Typical Razorpay loop: Online Assessment (90 min, 2-3 medium-hard coding problems) → Technical Interview 1 (DSA, ~45 min) → Technical Interview 2 (payment system design / projects, ~45 min) → Managerial (~45 min) → HR (~30 min). End-to-end often 2-3 weeks. Some Product Engineer or intern paths add resume-driven deep dives or extra coding.
Short version of the prep split: Split time roughly: DSA ~50%, payment/system design ~25%, timed coding mocks ~15%, projects/behavioral ~10%. Drill medium-hard arrays, strings, DP, and graphs; practice payment gateway, idempotency, and distributed design prompts; keep Python, Java, C++, or Go sharp for live coding.
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 Razorpay 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 Razorpay 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 Razorpay 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 Razorpay?” 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 Razorpay-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 Razorpay story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Razorpay 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 Razorpay 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 Razorpay papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Razorpay-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 Razorpay 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 Razorpay. 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 Razorpay, 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 Razorpay mistakes, you are collecting content, not preparing.
Extra drill block (1)
Sit one more mixed Razorpay 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.
Razorpay fresher CTC in India (2026)
Figures below are candidate-reported as of August 2026. Treat them as bands, not offer letters. Location (Bengaluru primary) and team shift totals.
Software roles
| Level | Experience | Base (approx.) | Total package | Typical background |
|---|---|---|---|---|
| Software Engineer (SDE-1) | 0-1 years | ₹15-20 LPA | ₹18-25 LPA | Strong DSA freshers |
| Software Engineer (SDE-2) | 2-4 years | ₹22-28 LPA | ₹25-35 LPA | Systems / design focus |
| Senior Software Engineer | 4-6 years | ₹30-40 LPA | ₹35-50 LPA | Ownership + leadership |
| Product Engineer | Entry-mid | ₹18-28 LPA | ₹18-28 LPA | Product sense + shipping |
Benefits candidates care about
Health cover for employee & family, stock/equity participation, learning budget, hybrid norms on many teams, meals/snacks at office, wellness support. Equity details vary by level and grant - read the offer letter, do not negotiate from blog averages alone.
Hybrid work and culture questions you should expect
- Are you willing to relocate to Bengaluru?
- How do you handle ambiguous merchant requirements?
- Tell me about feedback you disagreed with.
- What does “developer-friendly payments” mean to you technically?
Prepare honest answers. If you need fully remote forever, say so early - better a clean reject than a mismatched offer.
Final 72 hours
| Time | Do | Do not |
|---|---|---|
| T-72h | One light mock + design sketch | Start a new DP textbook |
| T-48h | Project rehearsal aloud | Sleep debt |
| T-24h | Error-log skim + Why Razorpay? | Caffeine experiment |
| Morning | ID, charger, water | New LeetCode hard |
Razorpay loops punish heroes who cram and reward students who protect sleep and narration.
Offer negotiation notes students forget
When the verbal band lands around ₹18-25 LPA:
- Ask what is fixed vs variable and how ESOPs vest
- Confirm joining bonus and relocation support in writing
- Compare against PhonePe / CRED offers on the same timeline, not LinkedIn screenshots
- Never resign from another role until the signed Razorpay letter is in your inbox
Razorpay hiring updates for 2026
Hiring shape 2026
Engineering hiring continues across backend, product engineering, and full-stack. Payments infra and merchant experience stay central.
Process notes
System design weight in interviews remains high. Resume-driven deep dives show up more in intern and PE notes - defend every keyword.
Company context
Bengaluru remains the primary hub. Confirm live openings on Careers before assuming regular campus volume.
Prep implication
Do not wait for a “new pattern” rumor. Double down on timed medium-hard DSA and payment-shaped design talks.
FAQs students ask about Razorpay placements
Papers & downloads
Can I download Razorpay placement papers PDF?
Yes. Free Razorpay placement papers PDF with previous-year style coding, DSA, payment design themes, and interview practice are on this site - no registration. Start with the 2026 PDF and year pages. Papers train patterns; they are not guaranteed clones of your live OA.
Process & rounds
What is the Razorpay placement process?
Typical fresher loop: Online Assessment (90 min, 2-3 medium-hard coding problems) → Technical 1 (DSA, ~45 min) → Technical 2 (payment system design / projects, ~45 min) → Managerial (~45 min) → HR (~30 min). End-to-end often 2-3 weeks. Some PE/intern tracks insert extra coding or resume deep dives.
How many rounds are there in Razorpay interview?
About five core stages for many SWE freshers (OA + two tech + managerial + HR). Exact count shifts by role - Product Engineer and intern funnels may add MCQs or HM coding.
What is Razorpay online assessment exam pattern?
Usually 90 minutes, 2-3 coding problems, medium-hard, arrays/strings/DP/graphs, on HackerRank or Razorpay’s tool, no negative marking. Hidden tests matter. Clear rates often cited around ~10-15%.
Does Razorpay hire through hackathons?
Yes. Campus, careers, referrals, and hackathons/coding contests all appear in student reports. Contests can shorten the invite queue; you still clear the same OA and design bar.
Interview content
What questions are asked in Razorpay technical interview?
Live DSA; payment system design (gateway, webhooks, scale); project deep-dives; behavioral ownership stories. Interviewers watch approach narration and edge cases as much as the final answer.
What is Razorpay system design interview like?
~45 minutes on payment-shaped architecture: APIs, data stores, retries/idempotency, consistency, and security. Fresher depth - clear components and trade-offs - not staff-level distributed systems theater.
Eligibility & languages
What is Razorpay eligibility criteria for freshers 2026?
From student reports: 70% or 7.0+ CGPA when listed across 10th/12th/graduation; B.Tech/B.E./M.Tech in CS/IT/Electronics/related; final-year or recent grads (~1 year); no active backlogs; max ~1 year gap. Verify your JD.
What programming languages are allowed in Razorpay?
Python, Java, C++, or Go are the usual interview languages. Python and Java are most common. Pick one language you can debug live under time pressure.
Are backlogs allowed at Razorpay?
Active backlogs are the usual blocker at application or joining. Cleared historical backlogs are generally fine if the notice does not say otherwise.
Salary & comparison
What is Razorpay salary for freshers?
Candidate-reported: SDE-1 ~₹18-25 LPA; SDE-2 often ₹25-35 LPA (2-4 YOE); Senior ~₹35-50 LPA (4-6 YOE). Confirm written offers; bands move by team and year.
Razorpay vs PhonePe vs CRED - which is better?
Razorpay - B2B payments infrastructure / merchant APIs. PhonePe - UPI/consumer payments at huge scale. CRED - premium credit-card rewards / member experience. Overlapping high-teens to mid-20s LPA chatter for strong freshers - choose on domain and team, not slogans.
Prep tip
How to prepare for Razorpay placement?
Rough split: DSA 50%, payment design 25%, timed mocks 15%, projects/behavioral 10%. Weekly 90-minute OA simulations + aloud design practice beat passive video watching.
Any pro tip for Razorpay placement preparation?
Budget real time for payment design - especially idempotency and failure modes. Explain solutions clearly; Razorpay rewards clean thinking as much as finishing every OA problem. Only list resume skills you can defend.
Is Bengaluru / hybrid work required?
Bengaluru is the primary engineering hub; many teams use hybrid norms. HR will check relocation willingness - answer honestly.
Does Razorpay ask aptitude MCQs in the OA?
Most fresher SWE reports emphasize coding-heavy OAs (2-3 problems in ~90 minutes). Some Product Engineer notes mention MCQs + two coding problems - always read your invite. Do not burn your prep calendar on CAT-level quant if your pattern is coding-only; keep light aptitude warm via the mock quiz just in case.
What is Razorpay PSE Intern interview like?
Intern write-ups often describe a ~1-hour technical on Google Meet, then a hiring-manager round that digs into resume keywords. Lesson from selects: only mention skills you can explain in depth - interviews are highly resume-driven.
Razorpay - recent candidate experiences
In August 2025, an on-campus Razorpay PSE Intern candidate (18 shortlisted; ₹50k stipend + 8.5 LPA PPO track) sat a ~1-hour Google Meet technical then a 30-minute hiring-manager round that dug into resume keywords like Kafka/PostgreSQL they hadn’t used deeply - their lesson: “only mention skills on your resume that you can confidently explain in depth, as interviews are highly resume-driven” (GeeksforGeeks).
A Product Engineer 2 candidate contacted via Instahyre detailed on GeeksforGeeks an OA (20 MCQs + two LeetCode mediums), two Java/Spring technical rounds, then a Hiring Manager coding+situational loop. They thought the HM went well after clarifying subarray vs subset and applying Kadane’s, but later learned “I was rejected due to feedback indicating that I couldn’t consider all possible scenarios for the problem” - a reminder that Razorpay’s final bar is edge-case completeness.