Solutions Architect
Razorpay · Bengaluru · 12+ yrs experience · Posted 2026-07-14
Tech stack: Kafka, AI
Apply on the company site · Get a referral for this role
Razorpay salary & ratings · Razorpay interview process · More live openings
About the role
Responsibilities:
- Every rupee that moves through RazorpayX touches a bank integration you will own, architect, and make faster — owning end-to-end reliability and performance of payment rails.
- You will sit at the intersection of RazorpayX platform engineering and partner bank systems — accountable for the reliability, performance, and architecture of every payment corridor.
- This is a hands-on IC role: you write code, shape architecture, and directly influence bank-side systems to drive SR, latency, and availability improvements at scale.
- What You'll Own
- Platform Reliability
- Own SR, Latency, and Availability as primary KPIs — drive structural fixes, not patches.
- Define SLOs per bank corridor; build observability frameworks for real-time health visibility.
- AI-driven anomaly detection and LLM-assisted RCA to cut MTTR on SR drops.
- Banking Ecosystem & Partner Engineering
- Primary technical counterpart to bank engineering — drive API design, architecture reviews, and joint SLA sessions.
- Standardize onboarding playbooks; identify STP opportunities to eliminate manual touchpoints.
- Work across UPI, IMPS, NEFT, RTGS to maintain Razorpay's technical advantage. › ML-based failure prediction for proactive traffic re-routing before SLA breaches.
- Platform Strategy & Architecture
- Build reusable, bank-agnostic integration layers — not one-off bank-specific implementations.
- Drive internal decisions: retry strategies, circuit breakers, idempotency, queue designs.
- Own the 12–24 month technical roadmap for the RazorpayX banking integration layer. › Champion AI-native infra: self-healing integrations, intelligent fallback routing, adaptive rate limiting.
- Cross-Functional Partnerships Drive prioritization with Engineering, Banking Partnerships, Operations, Finance, Compliance, and Merchant Success — translating merchant pain into root technical causes and shipping fixes.
- Required Experience Payments Domain
- Deep knowledge of UPI, IMPS, NEFT, RTGS — including bank-side processing pipelines, settlement cycles, and failure taxonomy.
- Hands-on experience building and operating bank integrations at scale.
- Technical Skills
- Distributed Systems — consistency, idempotency, failure handling at high throughput.
- APIs & Event-Driven Architecture — Kafka, queue-based retry, dead-letter handling, exactly-once semantics.
- Observability — metrics, distributed tracing, structured logging (Prometheus/Grafana or equivalent).
- Preferred Background
- 8–12+ years in payments, banking tech, or fintech — meaningful time in platform/infra engineering.
- Built or scaled payout infrastructure processing millions of transactions per day.
- Proven ability to influence without authority — across internal teams and external bank partners.
- Strong product thinking: every architectural decision traced back to customer and business impact.
Qualifications:
- Experience listed by Razorpay posting: 12+ years.
- Official department: Business.
- Location listed by Razorpay: Bangalore, India.
Qualifications
- Experience listed by Razorpay posting: 12+ years.
- Official department: Business.
- Location listed by Razorpay: Bangalore, India.
Responsibilities
- Every rupee that moves through RazorpayX touches a bank integration you will own, architect, and make faster — owning end-to-end reliability and performance of payment rails.
- You will sit at the intersection of RazorpayX platform engineering and partner bank systems — accountable for the reliability, performance, and architecture of every payment corridor.
- This is a hands-on IC role: you write code, shape architecture, and directly influence bank-side systems to drive SR, latency, and availability improvements at scale.
- What You'll Own Platform Reliability
- Own SR, Latency, and Availability as primary KPIs — drive structural fixes, not patches.
- Define SLOs per bank corridor; build observability frameworks for real-time health visibility.
- AI-driven anomaly detection and LLM-assisted RCA to cut MTTR on SR drops.
- Banking Ecosystem & Partner Engineering
- Primary technical counterpart to bank engineering — drive API design, architecture reviews, and joint SLA sessions.
- Standardize onboarding playbooks; identify STP opportunities to eliminate manual touchpoints.
- Work across UPI, IMPS, NEFT, RTGS to maintain Razorpay's technical advantage. › ML-based failure prediction for proactive traffic re-routing before SLA breaches.
- Platform Strategy & Architecture
- Build reusable, bank-agnostic integration layers — not one-off bank-specific implementations.
- Drive internal decisions: retry strategies, circuit breakers, idempotency, queue designs.
- Own the 12–24 month technical roadmap for the RazorpayX banking integration layer. › Champion AI-native infra: self-healing integrations, intelligent fallback routing, adaptive rate limiting.
- Cross-Functional Partnerships
- Drive prioritization with Engineering, Banking Partnerships, Operations, Finance, Compliance, and Merchant Success — translating merchant pain into root technical causes and shipping fixes.
- Required Experience Payments Domain
- Deep knowledge of UPI, IMPS, NEFT, RTGS — including bank-side processing pipelines, settlement cycles, and failure taxonomy.
- Hands-on experience building and operating bank integrations at scale.
- Distributed Systems — consistency, idempotency, failure handling at high throughput.
- APIs & Event-Driven Architecture
- Kafka, queue-based retry, dead-letter handling, exactly-once semantics.
- Observability — metrics, distributed tracing, structured logging (Prometheus/Grafana or equivalent).
- Preferred Background 8–12+ years in payments, banking tech, or fintech — meaningful time in platform/infra engineering.
- Built or scaled payout infrastructure processing millions of transactions per day.
- Proven ability to influence without authority — across internal teams and external bank partners.
- Strong product thinking: every architectural decision traced back to customer and business impact.