Razorpay is not hiring for a general software engineering role that happens to sit inside a payments company. They are hiring people who want to work on financial infrastructure and are genuinely interested in how money moves, not because payments is trendy, but because the technical problems are interesting and the failure costs are real.
If that framing does not land for you, that is worth knowing before you spend time tailoring your resume for them.
What "mischief makers" actually means
Razorpay describes their culture as seeking "mischief makers" and self-starters. This is easier to understand if you read it as: people who do not wait for permission, who find problems and fix them before being asked, and who take real ownership rather than working to scope.
On a resume, this shows up in two ways. First, in the nature of your projects: did you build things that were not assigned to you? Did you contribute to open source, build a tool you actually used, or solve a problem you identified yourself? Second, in the specificity of your proof: do your bullets show that you went deeper than the minimum requirement, or does each project have exactly what was needed and nothing more?
Generic tech resumes with no ownership signal consistently fail at Razorpay. A resume that lists five projects with shallow bullets reads as someone who does the assigned work. That is not the profile they are hiring for.
CGPA matters less than your coding ability
Razorpay has no published CGPA policy, and by most accounts does not use a hard cutoff. The emphasis is on programming skill and problem-solving ability.
What this means in practice: a strong competitive programming profile, a well-built GitHub, or a fintech-relevant project carries more weight than your aggregate score. If your CGPA is average but your coding is strong, this is a legitimate path. If your CGPA is strong but your coding fundamentals are weak, that will surface quickly in their technical rounds.
For context on other product tech companies, Razorpay's emphasis on domain expertise and coding fundamentals is similar to other fintech and product-focused firms, though their specific cultural filter ("mischief makers") is distinctive.
Coding fundamentals here means: data structures and algorithms you can reason about under pressure, system design concepts (for backend roles), and the ability to write clean, correct code in your language of choice. Python, Java, and Go are all used internally. Pick the one you are strongest in and make sure your resume projects use it substantively.
The fintech angle is not optional
A backend engineer applying to Razorpay with zero fintech project context is at a structural disadvantage compared to a candidate with similar coding skills who has built something in the payments or finance space.
This does not mean you need production payment experience. It means your resume should show genuine interest in the domain with something to back it up. Projects involving payment flows, financial APIs, transaction processing, or even simple wallet or ledger implementations signal that you understand what Razorpay's systems do at a conceptual level.
A few specific signals that land well:
- A project that handles money movement, even in a simplified form (wallets, splitting bills, transaction history)
- Awareness of concepts like idempotency, double-spend prevention, or reconciliation (even if only applied in a toy project)
- Any experience with financial APIs (Stripe, Razorpay test mode, bank statement parsing, UPI flows)
- PCI-DSS awareness, even at a surface level, signals domain curiosity for roles touching payment data
For related fintech opportunities, see our Flipkart resume guide, which covers how their PhonePe arm approaches fintech hiring differently from their e-commerce platform.
You do not need to have worked at a bank. You need to show you find these problems interesting and have thought about them.
What to emphasize by role family
Software Engineer: strong programming fundamentals, backend or API experience, and at least one project with fintech context. Your bullets should show system thinking: what happens when the network drops, how do you handle a failed transaction, where does state live?
Site Reliability Engineer (SRE): reliability and observability evidence. If you have set up monitoring, investigated incidents even in a project context, or worked with logs and metrics, put that front and center. Razorpay processes millions of transactions daily. SRE at a payments company means the stakes for failure are immediate and visible.
Product Analyst: data handling, SQL depth, and analytical proof. Any work involving payment data analysis, funnel analysis, or fraud detection patterns (even in coursework or internships) is relevant. Communication and structured reasoning matter as much as technical skills here.
Writing bullets for a payments-sensitive role
The formula: action + what you built + the constraint or risk you addressed + what was validated.
Weak: "Built payment APIs."
Better: "Built REST APIs for payment intent creation with idempotency keys and retry logic. Added logging for failed transactions and validated against duplicate-processing scenarios in integration tests."
Weak: "Implemented authentication."
Better: "Implemented JWT-based authentication for an admin service with role-level access controls. Added request validation middleware and rotated secrets on expiry. Documented threat model assumptions for the token lifecycle."
The second version in each case shows someone who thought about failure modes. That is the mindset Razorpay is screening for. Every payment system is one edge case away from a production incident.
How you get in: campus drives and hackathons
Razorpay hires selectively. For campus candidates, the primary paths are college placement drives and hackathons. Hackathon performance is explicitly a hiring signal. If you have placed well in any fintech or coding hackathon, include it in your resume.
Off-campus applications go through their careers page. Volume is lower and competition is higher off-campus, so your resume needs to be sharper. The fintech project angle and the coding fundamentals both matter more in this channel.
Run your resume through ResumeGrade before you apply
Check your resume on ResumeGrade before submitting. The resume scoring will surface where your proof bullets are too vague and where your skills section makes claims your projects do not support. The job description matching against a real Razorpay posting will show you exactly where the gap is between what they are asking for and what your resume currently demonstrates.
The fintech gap is the most common one for candidates who have strong general engineering skills but have not framed their domain interest clearly.
Common reasons Razorpay applications stall
- Strong CGPA, weak coding fundamentals (surfaces immediately in technical rounds)
- No fintech angle: every project is general backend with no payment or financial domain relevance
- Ownership signals missing: bullets that describe team outputs rather than individual contribution
- Vague project descriptions that do not give an interviewer anything specific to probe
- Security or reliability claims with no concrete technical action behind them
ResumeGrade
See exactly where your resume falls short
Every issue this article covers — vague bullets, weak structure, poor role alignment — ResumeGrade catches automatically. Upload your resume as PDF or DOCX and get a structured score across formatting, keyword alignment, impact, and ATS compatibility in under a minute. Feedback is specific and actionable, not a black-box number. We never invent achievements; every suggestion stays tied to what you already wrote. See a sample report before you upload.
Bottom line
Razorpay is a specific target for a specific type of candidate: strong coder, genuine fintech curiosity, and a track record of building things independently. Your resume needs to show all three. CGPA does not save you if the coding or domain signal is weak.
Build at least one project with real payment or financial domain context before you apply. Then run your resume through ResumeGrade to make sure the proof reads clearly before you enter their pipeline.
How does ResumeGrade compare?
