Razorpay hub
Razorpay Online Assessment
Overview
Razorpay online assessment (OA) is the first hard filter for many fresher and lateral engineering drives. This page covers format, sample Razorpay OA questions, an 8-week prep plan, and mistakes that sink strong candidates.
Patterns are from student reports for 2025-2026. Confirm your invite.
Razorpay hiring flow after the OA
| Stage | What candidates report | What you must show |
|---|---|---|
| 1. Online assessment | Timed DSA OA | Correctness + reasonable complexity |
| 2. Technical interviews | DSA + projects + payments intuition | Explain approach and edge cases |
| 3. Later rounds | HM / HR | Depth + communication |
| 4. HR / offer | Role, location, CTC | Consistency with resume |
Razorpay Online Assessment format
| Component | From student reports details |
|---|---|
| Platform | HackerRank / similar |
| Duration | About 90-120 minutes (confirm invite) |
| Question mix | 2-3 DSA problems; occasional tech MCQs |
| Languages | Java, C++, Python |
| Scoring | Automated tests |
| Advance rate | Competitive fintech filter |
What makes Razorpay OA feel distinct
- Fintech product DSA bar
- Payments domain flavor (idempotency, webhooks, ledgers)
- Medium-hard coding under time
- Interviews deepen reliability thinking
Question types
Core
- Hashing, streams, sliding windows
- Graphs/heaps
- DP/greedy
- Simulation of payment flows
Secondary
- API/reliability discussion in interviews
- SQL basics for some roles
Usually not in OA
- Full PCI-DSS whitepapers in OA time
- Bank clerk quant papers
Sample Razorpay Online Assessment questions
Question 1: idempotent payment ids in window
Question 2: webhook retry backoff count
Question 3: settle merchant balances
Question 4: rate limit API keys
Question 5: ledger subarray sum k
Question 6: merge payout windows
8-Week prep plan
| Weeks | Focus | Exit criteria |
|---|---|---|
| 1-2 | Arrays, hashing, two pointers | 40+ clean easy/medium |
| 3-4 | Trees/graphs/heaps as relevant | Implement BFS/DFS cold |
| 5-6 | Domain-flavored drills for Razorpay | Timed section comfort |
| 7 | Full mocks at OA duration | Finish required problems with tests |
| 8 | Weak-topic repair | Re-solve misses in 48 hours |
Daily loop
- One timed medium problem
- Write complexity + 3 edge cases before coding
- Log misses by pattern
- Weekly full mock
Common mistakes
- Ignoring duplicate/retry edge cases
- O(n^2) on large transaction streams
- No domain vocabulary (idempotency, webhook)
- Weak Java/Python fluency
- Skipping mocks
Day-of checklist
- Skim all problems for 3-4 minutes and order by familiarity
- Submit a correct simpler solution before over-optimizing if time is tight
- Invent edge cases the samples omit
- Do not leave a problem fully blank if a partial tested approach can score
- After the test, write down every problem from memory for interview prep
Interview transition plan (48 hours after OA)
- Re-solve your OA problems cleanly
- Prepare STAR stories (ownership, conflict, failure, impact)
- Revise OOPs, DBMS, OS one-pagers
- Rehearse a 2-minute project narration