Applying to Razorpay in India? This ATS guide for Site Reliability Engineer reveals the exact keywords, skills, and formatting Razorpay's resume screening checks for — with real tips to get past the filter. Use this guide to understand what Razorpay's ATS looks for — and check your own resume with our free AI-powered analyzer.
Check My Site Reliability Engineer Resume for RazorpayFree · No signup required · 3 free scans
Resume Strategy
Lead with reliability outcomes and incident management experience: 'Reduced mean time to recovery from 45 minutes to 12 minutes by implementing automated incident detection, runbook automation, and deployment rollback, improving payment system availability from 99.95% to 99.99%.' Highlight on-call experience and specific incidents you handled — SRE resumes that include postmortem learnings demonstrate the right mindset. Emphasize Kubernetes operational experience (cluster upgrades, resource management, troubleshooting), monitoring and observability stack (Prometheus, Grafana, Jaeger), and automation tooling you have built. Include programming skills (Go, Python, Bash) with specific examples of tools or automation you have written. If transitioning from a traditional ops role, highlight any infrastructure-as-code, automation, or scripting projects that demonstrate engineering thinking. For candidates from services companies managing client infrastructure, focus on incident response experience and reliability improvement projects. Mention any compliance or security experience (PCI-DSS, SOC 2) as this is directly relevant to Razorpay's regulated environment.
Site Reliability Engineers at Razorpay ensure the uptime and performance of India's leading payment infrastructure, where every minute of downtime translates to blocked transactions and revenue loss for millions of merchant businesses. The SRE team manages a microservices architecture running on Kubernetes across multiple AWS availability zones, with extensive use of Prometheus, Grafana, and distributed tracing for observability. CTC ranges from 16-25 LPA for junior SREs to 35-50 LPA for senior roles, with the SRE salary range reflecting the specialized but critical nature of the work. SREs at Razorpay operate at the intersection of software engineering and operations — they build internal tools for deployment automation, develop runbooks for incident response, design capacity planning models, and implement chaos engineering practices to test system resilience. The role demands deep understanding of Linux internals, networking (payment systems rely on stable network connectivity to banking partners), and database performance tuning. PCI-DSS compliance adds a security dimension that is absent in most SRE roles at non-financial companies.
These skills appear most in Razorpay's Site Reliability Engineer job descriptions. Use the exact phrasing below — ATS matches keywords verbatim.
Razorpay SRE hiring managers screen for production incident management experience, Kubernetes operational expertise, and the ability to build tooling that improves system reliability. They want engineers who have been on-call for production systems, handled real incidents under pressure, and implemented improvements that prevented recurrence. Resumes that demonstrate experience with incident response (detection, triage, mitigation, postmortem), SLO/SLA definition and tracking, and reliability improvement projects stand out. Common rejection reasons include listing monitoring tools without showing how you used them to improve reliability, no incident management experience, and SRE experience limited to infrastructure provisioning without software engineering. For candidates from traditional operations or sysadmin backgrounds, the critical gap is often the software engineering aspect — Razorpay SREs write Go or Python code to automate away operational toil, and manual processes are not acceptable.
These are the most frequent reasons Site Reliability Engineer resumes fail Razorpay's ATS or get filtered during recruiter review.
No mention of SLO/SLI experience — the defining characteristic of SRE vs generic ops
Incident response not quantified — mean time to detect/resolve matters
Missing on-call experience despite it being core to the role
Not featuring Go, Ruby on Rails, React prominently — Razorpay Site Reliability Engineer roles rely heavily on this stack
Razorpay values reliability — mention uptime SLAs, incident response experience, and fault-tolerant system design. Ignoring this is a common reason Razorpay resumes get filtered
The Razorpay SRE interview includes a Linux and networking fundamentals round (process management, memory, TCP/IP, DNS, load balancing), a system design round focused on reliability (design monitoring and alerting for a payment system, handle a specific failure scenario like a database failover during peak traffic), a coding round (write a tool in Go or Python that solves an operational problem — log parser, health checker, or deployment script), and a hiring manager round. Expect scenario-based questions: a merchant reports intermittent payment failures, walk through your debugging approach from symptom to root cause. Understanding of SLIs, SLOs, error budgets, and how they apply to payment systems is expected.
SRE (Site Reliability Engineering) was coined by Google and focuses specifically on service reliability — SLOs, error budgets, and eliminating toil. DevOps is a broader cultural and process philosophy. SREs typically write more production code than DevOps engineers and have a stronger software engineering background. The roles overlap but SRE implies more rigorous reliability engineering.
Very important — it's the core language of SRE. Show that you defined SLIs (what to measure), set SLOs (what target to hit), and used error budgets to decide when to freeze features vs. ship. This signals you understand the Google SRE model that the industry has converged on. Without it, you may come across as a rebranded ops person.
Razorpay is India's leading payments infrastructure company with a tech stack centered on Go, Ruby on Rails, React, PostgreSQL, Kafka. Strong engineering brand. Referral-heavy. Values deep technical understanding of distributed systems. Their culture is engineering-first culture. high bar for system reliability (payments infra). strong code review culture. For Site Reliability Engineer roles, align your resume with these priorities and highlight relevant technologies from their stack.
Razorpay's typical Site Reliability Engineer interview process: Online coding → system design deep-dive → 2 technical interviews focusing on distributed systems → cultural round. Prepare specifically for Razorpay's format — their process differs meaningfully from other companies in the industry.
Razorpay values reliability — mention uptime SLAs, incident response experience, and fault-tolerant system design. Payments domain experience is a strong advantage. Additionally, Razorpay's engineering culture emphasizes engineering-first culture — weave this into your experience descriptions. Research Razorpay's recent engineering blog posts and tech talks to reference specific initiatives or technologies they're investing in.
Dive deeper into career resources for Site Reliability Engineer roles at Razorpay.
Free ATS Check
Upload your resume + the Razorpay JD → get your real ATS score, missing keywords, and gap analysis in 30 seconds.
Score My Resume FreeFree · 3 scans · No signup required