About this role
Ignore the Solutions Architect title for a moment: the posting states plainly that this is a hands on individual contributor role where you write code and shape architecture. Razorpay processes over $180 billion in annualised transactions, and this role owns the reliability, performance and architecture of every bank integration behind RazorpayX. You would own success rate, latency and availability as primary metrics, define service level objectives per bank corridor, build observability for real time health, and work across UPI, IMPS, NEFT and RTGS. It is also the technical counterpart to partner bank engineering teams, driving API design and architecture reviews with them. This is deep payments infrastructure work at national scale, and there is very little else like it on this board.
Who this is for
Asks for 8 to 12+ years in payments, banking technology or fintech, with meaningful time in platform or infrastructure engineering.
Required payments domain knowledge: deep understanding of UPI, IMPS, NEFT and RTGS including bank side processing pipelines, settlement cycles and failure taxonomy, plus hands on experience building and operating bank integrations at scale.
Required technical skills: distributed systems with consistency, idempotency and failure handling at high throughput; APIs and event driven architecture including Kafka, queue based retry, dead letter handling and exactly once semantics; and observability covering metrics, distributed tracing and structured logging with Prometheus or Grafana or equivalent.
Day to day, grouped as the posting does: platform reliability, owning success rate, latency and availability as primary indicators, driving structural fixes rather than patches, defining service level objectives per bank corridor, and building observability frameworks, with AI driven anomaly detection and LLM assisted root cause analysis to reduce mean time to recovery. Banking ecosystem and partner engineering, acting as primary technical counterpart to bank engineering teams, driving API design, architecture reviews and joint service level agreement sessions, standardising onboarding playbooks and identifying straight through processing opportunities. Platform strategy and architecture, building reusable bank agnostic integration layers rather than one off implementations, driving decisions on retry strategies, circuit breakers, idempotency and queue design, and owning the 12 to 24 month technical roadmap for the banking integration layer. Plus cross functional work with engineering, banking partnerships, operations, finance, compliance and merchant success.
Location is Bengaluru. No office day count and no interview process are published.
Fit note: the posting says explicitly that this is a hands on IC role, which resolves the usual ambiguity around architect titles.
Required payments domain knowledge: deep understanding of UPI, IMPS, NEFT and RTGS including bank side processing pipelines, settlement cycles and failure taxonomy, plus hands on experience building and operating bank integrations at scale.
Required technical skills: distributed systems with consistency, idempotency and failure handling at high throughput; APIs and event driven architecture including Kafka, queue based retry, dead letter handling and exactly once semantics; and observability covering metrics, distributed tracing and structured logging with Prometheus or Grafana or equivalent.
Day to day, grouped as the posting does: platform reliability, owning success rate, latency and availability as primary indicators, driving structural fixes rather than patches, defining service level objectives per bank corridor, and building observability frameworks, with AI driven anomaly detection and LLM assisted root cause analysis to reduce mean time to recovery. Banking ecosystem and partner engineering, acting as primary technical counterpart to bank engineering teams, driving API design, architecture reviews and joint service level agreement sessions, standardising onboarding playbooks and identifying straight through processing opportunities. Platform strategy and architecture, building reusable bank agnostic integration layers rather than one off implementations, driving decisions on retry strategies, circuit breakers, idempotency and queue design, and owning the 12 to 24 month technical roadmap for the banking integration layer. Plus cross functional work with engineering, banking partnerships, operations, finance, compliance and merchant success.
Location is Bengaluru. No office day count and no interview process are published.
Fit note: the posting says explicitly that this is a hands on IC role, which resolves the usual ambiguity around architect titles.
Apply on company site
Opens job-boards.greenhouse.io, the employer's own application page. Applying is always free.