Razorpay Engineering Bangalore Interview 2026

Aap Razorpay Bangalore ke engineering role ke liye apply kar rahe ho, resume bheja, referral bhi try kiya, par dimaag me ek hi tension hai: interview me poochhenge kya? DSA hard hoga? System design me payment gateway ka design karwa denge? HR salary expectation pe lowball karega kya?

Razorpay ka naam sunte hi excitement bhi hoti hai aur pressure bhi. Fintech company hai, Bangalore engineering team strong hai, scale real hai, aur interviews me sirf “array reverse karo” type sawaal nahi aate. Yahan problem-solving, backend fundamentals, distributed systems, ownership, aur product thinking sab check hota hai.

Agar tum 2026 me Razorpay Engineering Bangalore interview target kar rahe ho, ye guide ek senior bhai/didi jaisa samjho. Isme process, rounds, expected questions, prep plan, salary range, resume tips, aur mistakes sab cover karenge, simple Hinglish me.

Razorpay Engineering Bangalore: role ka actual context#

Razorpay India ke top fintech startups me se ek hai. Payment gateway, banking products, payroll, vendor payments, subscriptions, fraud detection, settlement systems, ye sab iske ecosystem ka part hai.

Bangalore office engineering ke liye kaafi important hai. Backend, platform, infrastructure, data, security, frontend, mobile, SRE, DevOps, QA automation, sab type ke roles mil sakte hain.

Common engineering roles:

1. Software Development Engineer 1, SDE 1
2. Software Development Engineer 2, SDE 2
3. Senior Software Engineer
4. Backend Engineer
5. Frontend Engineer
6. Full Stack Engineer
7. Platform Engineer
8. Site Reliability Engineer, SRE
9. DevOps Engineer
10. Engineering Manager, EM

Freshers ke liye openings limited hoti hain, par off-campus ya referral se chance mil sakta hai. 1-3 years experience wale SDE 1/SDE 2 roles ke liye mostly DSA plus project depth hota hai. 4-7 years experience ke liye system design serious ho jata hai.

Razorpay interview 2026 me kya expect karein?#

Razorpay ka interview process role aur level ke hisaab se change hota hai, par generally structure kuch aisa hota hai:

1. Recruiter screening
2. Online coding test ya machine coding round
3. Technical Round 1, DSA/problem solving
4. Technical Round 2, backend/frontend depth
5. System design or low-level design
6. Hiring manager round
7. HR and compensation discussion

Kabhi-kabhi rounds combine bhi ho jaate hain. Agar referral strong hai, online test skip ho sakta hai, but guarantee nahi.

Razorpay jaise fintech me interviewer ye dekhna chahta hai:

• Tum clean code likhte ho ya sirf brute force?
• Edge cases samajhte ho?
• Database transactions samajh me aati hain?
• Race conditions kya hoti hain?
• Payment failure, retry, idempotency ka idea hai?
• Production issue handle kar sakte ho?
• Ownership hai ya “mujhe ticket mila tha maine kar diya” mindset?

Yahan ek important baat: Razorpay interview me “why fintech” ka answer bhi ready rakho. Bas “mujhe high-growth startup join karna hai” bolne se kaam nahi chalega.

Recruiter screening: simple round, par lightly mat lena#

Recruiter call usually 15-30 minutes ka hota hai. Isme technical deep dive nahi hota, but shortlist ya reject ka base ban sakta hai.

Common questions:

1. Current company aur role kya hai?
2. Notice period kitna hai?
3. Current CTC and expected CTC?
4. Bangalore relocate kar sakte ho?
5. Tech stack kya hai?
6. Razorpay me interest kyun hai?
7. Any competing offers?

Agar tum TCS, Infosys, Wipro, Accenture, Cognizant jaisi service company se ho, recruiter ye samajhna chahega ki tum product company pace handle kar paoge ya nahi.

Agar tum Paytm, PhonePe, Swiggy, Zomato, CRED, Meesho, Groww jaisi product/startup background se ho, tumhara profile comparatively easier sell ho sakta hai. But final decision interview performance pe hi hoga.

Salary expectation ka smart answer

Direct number bolne se pehle market range samjho.

Approx Razorpay Bangalore salary numbers, 2026 expectations ke hisaab se:

• SDE 1, 0-2 years: ₹18 LPA to ₹32 LPA
• SDE 2, 2-5 years: ₹30 LPA to ₹55 LPA
• Senior SDE, 5-8 years: ₹50 LPA to ₹85 LPA
• Staff/Lead level: ₹80 LPA to ₹1.3 Cr, role and stock mix pe depend

Ye total compensation hota hai, jisme fixed, bonus, ESOP/RSU type components ho sakte hain. Exact numbers company policy aur candidate profile pe vary karenge.

Smart line:

“Currently mera CTC ₹X LPA hai. Role, scope, fixed component aur overall compensation structure samajhne ke baad expectation discuss karna chahunga. Market ke hisaab se I am targeting around ₹Y LPA total compensation, but I am flexible for the right role.”

Online coding test: speed plus accuracy game#

Razorpay ka online test HackerRank, HackerEarth, Codility, ya internal platform pe ho sakta hai. Usually 60-90 minutes ka test hota hai.

Expected pattern:

1. 2 DSA questions
2. 1 medium, 1 medium-hard
3. Sometimes SQL or MCQ
4. Hidden test cases important hote hain

Topics jo prepare karne chahiye:

• Arrays and strings
• HashMap and HashSet
• Sliding window
• Two pointers
• Stack and queue
• Binary search
• Trees and BST
• Graph BFS/DFS
• Dynamic programming basics
• Greedy
• Heaps and priority queue

Fintech company hai to kabhi-kabhi transaction-style problem statement aa sakta hai, jaise wallet balance, fraud detection events, ledger entries, settlement grouping. Par base DSA hi hota hai.

Example coding questions

1. Given payment events, find duplicate transactions within 10 seconds.
2. Design a rate limiter for API requests.
3. Find top K merchants by transaction volume.
4. Validate refund eligibility from order and payment states.
5. Merge overlapping settlement windows.
6. Detect cycle in transaction dependency graph.
7. Find shortest path between bank nodes with transaction cost.

Tumhe syntax perfect chahiye. Java, Python, C++, Go, JavaScript, jo language use karte ho usme confident raho. Razorpay backend teams me Go, Java, PHP, Node.js, Python type stacks ka exposure mil sakta hai, but interview me language flexible hoti hai.

Technical Round 1: DSA interview ka actual pressure#

Ye live coding round hota hai. Interviewer tumhe problem deta hai, tum screen share karke code likhte ho.

Most candidates yahin galti karte hain: problem sunte hi code likhna start.

Better approach:

1. Problem ko repeat karo.
2. Input-output clarify karo.
3. Constraints pucho.
4. Brute force explain karo.
5. Optimized approach discuss karo.
6. Complexity bolo.
7. Code likho.
8. Dry run karo.
9. Edge cases test karo.

Example:

“Main pehle brute force O(n²) soch raha hoon, but agar n 10⁵ hai to ye pass nahi karega. HashMap use karke O(n) me kar sakte hain.”

Ye line interviewer ko dikhati hai ki tum mature ho, bas LeetCode ratta nahi maar rahe.

DSA round ke favorite areas

Razorpay me payment-scale thinking important hai, to ye patterns useful rahenge:

• Deduplication using HashMap
• Time window problems
• Event ordering
• Rate limiting
• Concurrent requests style logic
• Graph dependency
• Prefix sums
• Priority queue for top K
• LRU cache type design

Agar tum SDE 2 ke liye ja rahe ho, ek problem ke baad follow-up definitely aa sakta hai.

Follow-up examples:

• What if input is streaming?
• What if data does not fit in memory?
• What if two services write same transaction?
• How will you handle duplicate webhook events?
• Can this be done with lower space?

Technical Round 2: backend depth, real engineering starts here#

Agar tum backend role ke liye apply kar rahe ho, ye round bahut important hai. Yahan DSA se zyada practical backend knowledge check hota hai.

Expected topics:

1. REST APIs
2. Database design
3. SQL queries
4. Indexing
5. Transactions
6. Isolation levels
7. Caching
8. Message queues
9. Concurrency
10. Idempotency
11. Logging and monitoring
12. Error handling

Razorpay payment company hai, to interviewer ye pooch sakta hai:

“Suppose user ne payment kiya, bank ne amount debit kar diya, but Razorpay ko callback nahi mila. System kya karega?”

Iska answer simple nahi hai. Tumhe states, retries, reconciliation, idempotency, and eventual consistency samajhna padega.

Good answer structure:

1. Payment ko unique payment_id milega.
2. Initial state created/pending hogi.
3. Bank redirect/callback async aa sakta hai.
4. Callback duplicate ho sakta hai, idempotent processing chahiye.
5. Agar callback missing hai, scheduled reconciliation job bank se status fetch karega.
6. Final state success/failed update hogi.
7. Merchant webhook reliably send hoga, retry policy ke saath.
8. Ledger entries atomic honi chahiye.
9. Monitoring alerts lagne chahiye if pending payments spike.

Ye answer interviewer ko impress karega because tum production thinking dikha rahe ho.

SQL and database questions

Prepare these properly:

1. Difference between primary key and unique key
2. Clustered vs non-clustered index
3. Composite index ka order kyun important hai
4. Transaction ACID properties
5. Isolation levels: read committed, repeatable read, serializable
6. Deadlock kya hota hai
7. Optimistic vs pessimistic locking
8. Pagination: offset vs cursor
9. Query optimization basics
10. Normalization vs denormalization

Sample SQL question:

“Given payments table with merchant_id, amount, status, created_at, find top 10 merchants by successful payment volume in last 30 days.”

Tum query likho:

SELECT merchant_id, SUM(amount) AS total_volume
FROM payments
WHERE status = 'success'
  AND created_at ≥ NOW() - INTERVAL '30 days'
GROUP BY merchant_id
ORDER BY total_volume DESC
LIMIT 10;

Then index discuss karo:

• Index on (status, created_at)
• Maybe (merchant_id, status, created_at)
• For large tables, partition by created_at
• Aggregation precompute kar sakte hain analytics use case me

System design round: Razorpay me yeh game changer hai#

SDE 2 and above ke liye system design kaafi important hai. SDE 1 me low-level design ya small service design aa sakta hai.

Common system design questions:

1. Design a payment gateway
2. Design a wallet system
3. Design a URL shortener
4. Design a rate limiter
5. Design a notification system
6. Design a ledger system
7. Design webhook delivery service
8. Design merchant dashboard analytics
9. Design refund processing system
10. Design UPI transaction status tracking

Razorpay interview me payment-related design aana very possible hai.

Design a payment gateway: answer ka structure

Agar interviewer bole “Design Razorpay-like payment gateway”, panic mat karna. Full Razorpay design nahi chahiye. Ek scoped version chahiye.

Clarify first:

• Scale kya hai?
• Payment methods: cards, UPI, netbanking?
• Merchants kitne?
• Transaction per second kitna?
• Sync or async flow?
• Refunds include karna hai?
• Webhooks chahiye?

Basic components:

1. Merchant API service
2. Auth service
3. Payment orchestration service
4. Bank/UPI provider integration service
5. Payment state machine
6. Database
7. Ledger service
8. Queue system
9. Webhook service
10. Reconciliation service
11. Monitoring and alerting

Payment states:

• created
• authorized
• captured
• failed
• refunded
• partially_refunded
• pending

Important design points:

• Idempotency key for create payment API
• Never trust client amount
• Use server-side merchant order amount
• Store provider reference IDs
• Webhooks can be delayed or duplicated
• Use queues for async processing
• Retry with backoff
• Reconciliation jobs for mismatch
• Audit logs for every money movement
• Encryption and security compliance

Idempotency ko simple way me samjho

Payment systems me user double click kar sakta hai. Network timeout ho sakta hai. Merchant API retry kar sakta hai.

Agar same request twice process ho gayi, user ka double charge ho sakta hai. Fintech me ye disaster hai.

Solution: idempotency key.

Merchant same request ke saath ek key bhejta hai. Server check karta hai:

• Agar key new hai, process request
• Agar key already used hai, old response return
• Agar request body different hai, reject

Ye concept Razorpay interview me definitely kaam aayega.

Low-level design, LLD: clean code matters#

LLD round me object-oriented design aur code structure check hota hai. Java candidates ke liye common, but Python/Go candidates se bhi design pooch sakte hain.

Possible questions:

1. Design splitwise
2. Design parking lot
3. Design rate limiter
4. Design wallet
5. Design order/payment state machine
6. Design notification system
7. Design invoice generation system
8. Design subscription billing

Razorpay style LLD: “Design a payment retry system” ya “Design a wallet ledger”.

Good LLD answer me ye hona chahiye:

• Classes/entities clear
• Interfaces sensible
• Extensibility without overcomplication
• Error handling
• State transitions
• Test cases

Example entities for wallet:

• User
• Wallet
• Transaction
• LedgerEntry
• WalletService
• TransactionRepository
• BalanceService

Ledger ke liye important rule:

Available balance ko directly update karna easy hai, but ledger entries source of truth honi chahiye. Har credit/debit ka immutable entry ho. Balance compute ya cached ho sakta hai.

Frontend engineering interview: Razorpay dashboard type thinking#

Agar tum frontend role ke liye ja rahe ho, DSA thoda light ho sakta hai, but JavaScript, React, performance, browser fundamentals strong chahiye.

Expected topics:

1. JavaScript closures
2. Event loop
3. Promises and async/await
4. Debouncing and throttling
5. React hooks
6. State management
7. Component design
8. Forms and validation
9. API error handling
10. Performance optimization
11. Accessibility basics
12. Testing with Jest/RTL

Possible machine coding tasks:

1. Build transaction table with filters
2. Build autocomplete search
3. Build payment status dashboard
4. Build multi-step checkout form
5. Build toast notification system
6. Build pagination/infinite scroll
7. Build retryable API component

Razorpay frontend me dashboard, checkout, merchant experience, analytics UI jaise products hain. Toh UX clarity important hai.

Good frontend candidate ye discuss karega:

• Loading state
• Empty state
• Error state
• Retry button
• Pagination
• API cancellation
• Debounced search
• Responsive design
• Security, like XSS prevention
• Accessibility labels

SRE, DevOps, Platform roles: reliability ka interview#

Agar tum SRE ya platform engineering ke liye apply kar rahe ho, interview ka focus alag hoga.

Topics:

1. Linux fundamentals
2. Networking
3. DNS, HTTP, TCP
4. Kubernetes
5. Docker
6. CI/CD
7. Observability
8. Incident management
9. Autoscaling
10. Rate limiting
11. Load balancing
12. Disaster recovery

Razorpay jaise payment systems me downtime ka direct business impact hota hai. Agar payment success rate 99.5 percent se 98 percent ho gaya, merchants ka trust hit hota hai.

Expected questions:

• API latency spike ho raha hai, debug kaise karoge?
• Kubernetes pod crash loop me hai, kya check karoge?
• Database CPU 95 percent hai, next steps?
• Payment callback service down hai, incident response?
• Blue-green vs canary deployment?
• What is circuit breaker?
• How do you reduce MTTR?

Good answer always structured hona chahiye:

1. Impact assess karo
2. Metrics dekho
3. Logs and traces check karo
4. Recent deployments check karo
5. Rollback option evaluate karo
6. Mitigation first, root cause later
7. Communication clear rakho
8. Postmortem with action items

Hiring manager round: culture fit nahi, ownership fit#

Hiring manager round ko log “casual” samajh ke lightly lete hain. Galat. Yahan decide hota hai ki tum team me kaise perform karoge.

Common questions:

1. Tell me about a project you owned end-to-end.
2. Biggest production issue you handled?
3. Conflict with teammate ka example?
4. Tight deadline me kya kiya?
5. Technical decision galat nikla, kaise handle kiya?
6. Why Razorpay?
7. Why leave current company?
8. What kind of team do you enjoy?
9. How do you handle ambiguity?
10. What are you looking for in next role?

STAR format use karo:

• Situation
• Task
• Action
• Result

Example answer:

“Hamare payment reconciliation job me delay aa raha tha. Daily 2 lakh records process hote the aur job 5 hours le raha tha. Maine query profiling ki, batching add ki, index optimize kiya, aur parallel workers introduce kiye. Processing time 5 hours se 45 minutes ho gaya, aur pending reconciliation alerts 70 percent reduce hue.”

Numbers add karo. Interviewer ko measurable impact pasand aata hai.

HR round: compensation, notice period, offer negotiation#

HR round me polite but prepared raho. Startup compensation structure kabhi simple nahi hota.

Poochne wale questions:

1. Current fixed salary?
2. Variable bonus?
3. ESOP/RSU?
4. Expected fixed?
5. Notice period negotiable hai?
6. Any offers from TCS, Infosys, Wipro, Swiggy, Zomato, Paytm, PhonePe?
7. Joining timeline?

Agar tumhare paas competing offer hai, honestly batao. Fake offer mat bolo. Background verification me issue ho sakta hai.

Negotiation tips

1. Pehle role scope samjho.
2. Fixed component clearly pucho.
3. Variable payout history pucho.
4. Stock vesting schedule samjho.
5. Joining bonus possible hai kya pucho.
6. Notice period buyout discuss karo.
7. Offer breakup written me lo.

Line use kar sakte ho:

“I am excited about the role and team. Based on my current compensation, market range for similar Bangalore fintech roles, and the scope discussed, I was expecting closer to ₹X LPA total compensation. Is there any flexibility in the fixed or joining bonus component?”

Professional tone rakho. Desperate mat lagna, arrogant bhi mat lagna.

Razorpay ke liye resume kaise banana hai#

Resume ATS-friendly hona chahiye. Fancy Canva template, icons, photo, rating bars, 2-column design, ye sab avoid karo. Product companies me recruiters quickly scan karte hain.

Best format:

1. Name, phone, email, LinkedIn, GitHub
2. Summary, optional
3. Skills
4. Work experience
5. Projects
6. Education
7. Achievements

Skills section me kya likhein

Backend candidate:

• Languages: Java, Go, Python, JavaScript
• Backend: Spring Boot, Node.js, REST APIs, gRPC
• Databases: PostgreSQL, MySQL, Redis, MongoDB
• Messaging: Kafka, RabbitMQ, SQS
• Cloud: AWS, GCP, Docker, Kubernetes
• Observability: Prometheus, Grafana, ELK

Frontend candidate:

• JavaScript, TypeScript
• React, Next.js
• Redux, Zustand
• HTML, CSS, Tailwind
• Jest, React Testing Library
• Web performance
• REST APIs, GraphQL

But sirf keywords bharna mat. Work experience me proof dikhao.

Bad bullet:

“Worked on payment APIs and database.”

Good bullet:

“Built refund status API handling 50K daily requests, added Redis caching and reduced p95 latency from 420ms to 180ms.”

Resume bullets me numbers zaroor daalo

Strong bullets:

• Improved API latency by 35 percent by optimizing SQL indexes and reducing N+1 queries.
• Built reconciliation job processing 1.2M transactions daily with retry and alerting.
• Reduced payment failure investigation time by 40 percent using structured logs and dashboards.
• Designed webhook retry mechanism with exponential backoff, improving delivery success from 94 percent to 99.2 percent.
• Migrated legacy cron service to queue-based workers, reducing timeout errors by 60 percent.

Agar tum fresher ho:

• Built UPI-like payment simulator with wallet ledger, idempotency, and transaction history.
• Created React dashboard for merchants with filters, charts, and pagination.
• Solved 450+ DSA problems on LeetCode/GFG, focusing on graphs, DP, and heaps.
• Interned at startup and built REST APIs used by 5K monthly users.

30-day prep plan for Razorpay Engineering Bangalore#

Agar interview 1 month baad hai, ye plan follow karo.

Week 1: DSA base strong karo

Daily:

1. 2 medium problems
2. 1 previous solved problem revise
3. 30 minutes complexity analysis
4. 15 minutes dry run practice

Topics:

• Arrays
• Strings
• HashMap
• Sliding window
• Binary search
• Stack

Goal: speed build karna.

Week 2: advanced DSA plus SQL

Daily:

1. 1 graph/tree problem
2. 1 heap/DP problem
3. 2 SQL queries
4. 1 mock explanation

Topics:

• Trees
• Graphs
• Priority queue
• DP basics
• SQL joins
• Indexing

Goal: medium-hard se dar kam karna.

Week 3: backend and system design

Daily ek design topic:

1. Payment gateway
2. Webhook service
3. Rate limiter
4. Wallet ledger
5. Notification system
6. Refund system
7. Analytics dashboard

Har design me ye cover karo:

• Requirements
• APIs
• Database schema
• Components
• Failure cases
• Scaling
• Monitoring

Goal: structured thinking.

Week 4: mocks and resume stories

Daily:

1. 1 mock coding round
2. 1 behavioral story
3. 1 project deep dive
4. Resume bullet revision
5. Company research

Prepare 6 stories:

• Project ownership
• Production bug
• Performance improvement
• Conflict
• Learning new tech
• Failure or mistake

Common mistakes jo rejection karwa deti hain#

Razorpay interview me candidate smart hota hai, but mistakes basic hoti hain.

Avoid these:

1. Problem clarify kiye bina code start karna
2. Edge cases ignore karna
3. Complexity nahi batana
4. System design me only buzzwords bolna
5. Database transactions nahi samajhna
6. Idempotency ka concept weak hona
7. Resume me fake scale likhna
8. HR ko unrealistic salary bolna without reason
9. Current company ko badmouth karna
10. “I don’t know” bolne se darrna

Actually “I don’t know” acceptable hai agar uske baad tum reasoned guess karo.

Example:

“I haven’t implemented Kafka exactly at this scale, but I understand the producer-consumer model, partitions, consumer groups, and retry handling. I would think about ordering guarantees and duplicate processing first.”

Ye honest and mature lagta hai.

Razorpay vs TCS, Infosys, Wipro interview difference#

Agar tum service company background se ho, difference samajhna zaroori hai.

TCS, Infosys, Wipro me many roles project allocation based hote hain. Interview me Java basics, SQL, project explanation, HR stability questions common hote hain.

Razorpay, PhonePe, Paytm, Swiggy, Zomato type product/startup companies me focus hota hai:

• Ownership
• Scale
• Data structures
• System design
• Real production trade-offs
• Fast execution
• Product impact

Isliye apne service company project ko product-style me present karo.

Instead of:

“I worked on client banking project.”

Say:

“I worked on loan repayment module for a banking client, built APIs for payment schedule updates, handled transaction status updates, and optimized reconciliation query from 12 seconds to 3 seconds.”

Story same hai, presentation better hai.

Questions tum interviewer se pooch sakte ho#

Interview ke end me “Do you have any questions?” aata hai. “No” mat bolna.

Good questions:

1. Team currently kis product area pe kaam kar rahi hai?
2. This role ka first 3 months expectation kya hoga?
3. Engineering team ka on-call process kaisa hai?
4. Code review culture kaisa hai?
5. Payment reliability ke liye team ka main metric kya hai?
6. Is role me backend/system design ownership kitna hoga?
7. Current technical challenges kya hain?
8. Team India scale pe kaunse problems solve kar rahi hai?

Ye questions tumhe serious candidate dikhate hain.

Final checklist before Razorpay interview#

Interview se 24 hours pehle ye checklist follow karo:

• Resume ek baar read karo
• Top 3 projects revise karo
• 5 DSA patterns revise karo
• Payment gateway flow revise karo
• Idempotency, retry, reconciliation clear karo
• SQL indexes revise karo
• Salary expectation range decide karo
• Laptop, internet, IDE ready rakho
• Notepad ready rakho
• 2 questions interviewer ke liye ready rakho

Interview ke din:

• 10 minutes pehle join karo
• Problem repeat karo
• Loud thinking karo
• Agar stuck ho, hint ask karo
• Code clean rakho
• Test cases run karo
• Calm raho

Final thought: Razorpay crack karna possible hai, bas random prep mat karo#

Razorpay Engineering Bangalore interview tough ho sakta hai, but impossible nahi. Tumhe bas teen cheezein clearly dikhani hain: problem-solving, production thinking, aur ownership.

DSA se entry milti hai. Backend/system design se trust banta hai. Hiring manager round me tumhari maturity dikhti hai. HR round me negotiation hota hai.

Agar tum TCS, Infosys, Wipro se ho, ya Paytm, PhonePe, Swiggy, Zomato jaise product company se, dono cases me story matter karti hai. Resume pe impact dikhna chahiye, interview me clarity dikhni chahiye.

Sabse pehle apna resume ATS-friendly banao, kyunki interview room tak pahunchne se pehle bot aur recruiter dono scan karte hain. Apna resume free me check karo: JobRise Free ATS Checker