Razorpay's DevOps hiring loop filters for engineers who architect for fintech-scale reliability and velocity. With a sub-2% acceptance rate, your resume must signal you've handled payment-grade SLOs, not just deployed containers. The internal rubric (E3-E6) heavily weights your direct impact on system uptime, developer productivity, and cost efficiency. Generic infrastructure management gets an auto-reject. Committees, including a Bar Raiser, evaluate your scope against Razorpay's core challenges: handling 500+ TPS during flash sales, securing PCI-DSS Level 1 environments, and scaling Kubernetes to 1000+ nodes with sub-second P99 latency.
ATS Insider Intelligence
How Keka HR Actually WorksKeka HR's parser at Razorpay heavily weights the 'Skills' and 'Experience' sections. It performs a first-pass match against a pre-configured keyword list for the role (e.g., 'Kubernetes', 'Terraform', 'Prometheus', 'SLO'). Recruiters then apply a manual scorecard tagging system for 'Scale', 'Ownership', and 'Complexity' based on evidence in your bullet points. PDFs are safe, but avoid multi-column layouts and text boxes—they can mangle the parsed text. Keka does NOT parse header/footer text. The system highlights keyword frequency but penalizes obvious stuffing; recent role impact (last 3 years) carries 70% of the weight. Knockout questions are often binary filters for specific experience like 'PCI-DSS compliance' or 'production K8s cluster management.'
🎯 ATS Keyword Arsenal
Razorpay • DevOps Engineer • Keka HR — Click any keyword to copy it
⚡ Technical Skills
🔧 Tools & Platforms
🧠 Behavioral / Soft Skills
🏢 Domain Expertise
See how many you're already using 👇
Keka HR's keyword scoring is the first gatekeeper. Without precise alignment, your resume is auto-filtered before a human ever sees it, wasting a referral or application.
Test Your Resume Against Razorpay's DevOps Engineer Keywords
Paste your resume bullets below to see how many of Razorpay's 39 target ATS keywords and impact metrics you match right now.
Expert Resume Tips for Razorpay
Lead every bullet with a fintech-scale metric (Uptime %, Latency ms, $ Saved).
Replace 'managed infrastructure' with 'maintained 99.995% uptime SLO for core payment APIs handling 500+ TPS, reducing P99 latency by 40ms through kernel parameter tuning.' Razorpay's rubric quantifies impact on business continuity and efficiency. Use concrete numbers for availability, deployment frequency, incident reduction, and cloud cost savings.
Why this matters at Razorpay
Hiring committees need calibrated evidence to slot you into E4 (project scope) vs E5 (multi-service/platform scope). Vague statements default to a lower level.
Explicitly name 'PCI-DSS' and 'Security Audit' if you have compliance experience.
Razorpay's status as a PCI-DSS Level 1 certified payment processor makes this a critical knockout filter. Detail your work in securing infrastructure, managing secrets with Vault, implementing network segmentation, and passing external audits. Don't bury it.
Why this matters at Razorpay
This is a non-negotiable domain requirement. Lack of explicit signaling here leads to immediate rejection by recruiters using Keka's tag filters.
Structure your experience using CAR (Challenge, Action, Result) not just responsibilities.
For each role, start with the core challenge (e.g., 'fragile deployments causing weekend rollbacks'), describe your technical actions ('implemented GitOps pipeline with ArgoCD and canary analysis'), and end with the quantified business result ('reduced deployment failures by 90% and enabled 50 daily zero-downtime releases').
Why this matters at Razorpay
The Bar Raiser evaluates the depth of problem-solving. Responsibility lists fail to demonstrate the 'why' and 'so what' needed for committee review.
Mirror Razorpay's stack keywords precisely: 'Kubernetes', 'Terraform', 'AWS', 'Prometheus'.
Use the exact terms from the job description and this guide's technical list. Synonyms like 'container orchestration' or 'provisioning tool' may not be in Keka's primary keyword list and can hurt your parse score. List them in a dedicated Skills section and again in bullet contexts.
Why this matters at Razorpay
Keka's first-pass ranking is heavily dependent on literal keyword matching. Recruiters often sort the applicant pool by this initial match score.
Show platform ownership, not just task execution.
Frame your work as building platforms for other engineers. Example: 'Designed and owned the internal developer platform for self-service provisioning, reducing environment setup time from 3 days to 30 minutes for 200+ product teams.'
Why this matters at Razorpay
Razorpay's senior levels (E5+) require 'multiplier' impact. Showing you enable other engineers signals higher scope and autonomy.
Before vs After: Real Bullet Rewrites
These are the exact bullets that get filtered vs. the ones that get through Keka HR and land interviews.
⚡ Insider Counter-Intuition
Contrary to popular advice, listing every technology you've touched hurts you at Razorpay. The hiring committee looks for depth and mastery in core areas (K8s, AWS, IaC) relevant to their stack. A resume showing you deeply solved complex problems with a focused stack signals higher competence than a broad, shallow tool list. They prefer a 'T-shaped' engineer—deep on platform fundamentals, broad on awareness.
Mistakes That Get DevOps Engineers Rejected at Razorpay
FAQ: DevOps Engineer at Razorpay
Does Razorpay's Keka HR ATS prefer PDF or DOCX resumes for DevOps roles?
PDF is safe and recommended. Ensure it is a text-based, not image-based, PDF. Keka's parser handles both, but complex formatting in DOCX (like linked text boxes) can sometimes corrupt during upload. Stick to a clean, single-column layout with standard fonts.
What is the typical career level (E3, E4, E5) for a DevOps Engineer at Razorpay?
E4 (Senior) is the most common hire, requiring ownership of a platform/service with multi-million user impact. E3 is for early-career engineers with 2-4 years' experience. E5 (Staff) requires defining best practices and platforms for the entire organization. Your resume's scope and impact metrics must align with the level you target.
How important is AWS experience compared to multi-cloud for Razorpay?
AWS is mandatory. Razorpay's infrastructure is heavily invested in AWS. Multi-cloud experience is a nice-to-have but never a substitute. Deep, production-grade expertise in AWS services (EKS, RDS, IAM, Networking) is a primary knockout criterion.
Should I include certifications like AWS Solutions Architect on my resume?
Yes, but only at the bottom. Razorpay values proven production experience over certificates. Listing certs can help with initial keyword matching in Keka, but they won't compensate for lack of scale and impact in your bullet points. Prioritize space for project evidence.
How does Razorpay evaluate experience with on-call and incident management?
It's a critical signal. Explicitly mention reducing MTTR (Mean Time to Resolve), improving alert precision, or conducting blameless post-mortems. Phrases like 'owned on-call for payment APIs' and 'reduced pager alerts by 60%' show operational maturity valued in fintech's high-stakes environment.
Related Resume Guides
Other Roles at Razorpay
Check Your Razorpay ATS Score
See exactly how many of these 40 keywords you're using right now.
Run ATS Check Free Build Resume with AI🔍 ATS Being Used
Keka HR
Optimize specifically for Keka HR to beat the automated filter before a human even sees your resume.
Stop Guessing. Start Matching.
Upload your resume and see exactly how many of these 40 Razorpay-specific keywords you're already matching — and which gaps are costing you the interview.