Staff Engineer

Moneyview; Bengaluru; On-site; INR 2,200,000 - 3,600,000; Full time

Job summary

Moneyview seeks a Staff Engineer to own the backend systems that run our lending operations end to end. You will set architecture across a large fleet of microservices, ensuring reliability, correctness, and auditable money movements while raising delivery speed through AI-assisted development.

You will mentor engineers, define cross-team standards, and partner with Operations, Risk and Credit to design scalable, compliant systems for RBI-regulated lending.

Qualifications

• 9–12 years building and operating backend systems at scale, including a track record as the technical owner of a business-critical domain.
• Strong hands‑on Java with Spring Boot or equivalent; fluent enough in a second language to pick the right tool.
• Real depth in microservices — you have designed, decomposed and operated a multi‑service estate in production, not merely contributed to one.

Responsibilities

• Own the architecture of the lending OPS platform end to end — workflow, KYC, calling, OPS etc.
• Be accountable for correctness of money movement and loan state: idempotency, reconciliation, retries, compensating flows, audit trails and eventual consistency across services.
• Drive both high-level and low-level design: service boundaries, APIs, schemas, data segregation, class and sequence design — with scalability, extensibility, maintainability and security as explicit acceptance criteria.
• Influence architecture beyond your own POD; review and shape peer-team designs wherever lending flows cross team boundaries.
• Define, instrument and monitor the key metrics of the systems you own — latency, error budgets, disbursement success rate, queue lag and cost per transaction.
• Cut through ambiguity on business problems: establish technical scope, boundaries, assumptions, limitations and a recommended solution, and create direction where none exists.
• Advocate for the simplest solution that holds, and for long-term flexibility without slowing delivery.
• Work across Dev, DevOps and QA boundaries; go deep and hands-on to unblock others rather than delegating the hard parts.
• Partner directly with Operations, Credit, Risk and Collections teams to understand pain points first-hand, and design working backwards from those needs.
• Articulate complex technical trade-offs to non-technical stakeholders and drive alignment.
• Mentor and coach engineers across PODs; be the recognised SME in your area and deliberately build depth in others.
• Introduce tools, processes and practices that raise software quality, and codify them as team standards.
• Participate actively in hiring and continuously improve the hiring bar and process.
• Be frugal with resources — engineering time, software, infrastructure and cloud spend.

Skills

Java with Spring Boot

Microservices

Relational DB design

NoSQL / caching

Kafka

Docker/Kubernetes

AWS

Observability/ SRE

AI coding tools

Technical communication

Tools

MySQL

PostgreSQL

Redis

MongoDB

DynamoDB

Kafka

Job description

Experience: 9–12 Years

Job Description

Moneyview is looking for a Staff Engineer to own the backend systems that run our lending

operations end to end till disbursal. You will be the senior-most technical voice in the OPS/LOS

team: setting architecture across a large fleet of microservices, holding the line on reliability and

correctness in a domain where a bug is a money or compliance event, and raising the bar on

how fast the team ships by making AI-assisted development the default way we work.

Key Responsibilities

• Own the architecture of the lending OPS platform end to end — workflow, KYC, calling, OPS etc. — not just the services your POD writes.
• Be accountable for correctness of money movement and loan state: idempotency, reconciliation, retries, compensating flows, audit trails and eventual consistency across services.
• Treat the regulatory reality of lending as a design constraint, not a retrofit — RBI and partner-bank obligations, PII handling, data retention and auditability.
• Drive both high-level and low-level design: service boundaries, APIs, schemas, data segregation, class and sequence design — with scalability, extensibility, maintainability and security as explicit acceptance criteria.
• Influence architecture beyond your own POD; review and shape peer-team designs wherever lending flows cross team boundaries.
• Define, instrument and monitor the key metrics of the systems you own — latency, error budgets, disbursement success rate, queue lag and cost per transaction.
• Cut through ambiguity on business problems: establish technical scope, boundaries, assumptions, limitations and a recommended solution, and create direction where none exists.
• Advocate for the simplest solution that holds, and for long-term flexibility without slowing delivery.
• Work across Dev, DevOps and QA boundaries; go deep and hands-on to unblock others rather than delegating the hard parts.
• Partner directly with Operations, Credit, Risk and Collections teams to understand pain points first-hand, and design working backwards from those needs.
• Articulate complex technical trade-offs to non-technical stakeholders and drive alignment.
• Mentor and coach engineers across PODs; be the recognised SME in your area and deliberately build depth in others.
• Introduce tools, processes and practices that raise software quality, and codify them as team standards.
• Participate actively in hiring and continuously improve the hiring bar and process.
• Be frugal with resources — engineering time, software, infrastructure and cloud spend.

Required Skills

• 9–12 years building and operating backend systems at scale, including a track record as the technical owner of a business-critical domain.
• Strong hands‑on Java with Spring Boot or equivalent; fluent enough in a second language to pick the right tool.
• Real depth in microservices — you have designed, decomposed and operated a multi‑service estate in production, not merely contributed to one.
• Strong data layer skills: relational schema design and query tuning (MySQL or PostgreSQL), plus practical use of a NoSQL or caching store such as Redis, MongoDB or DynamoDB.
• Event‑driven systems in production with Kafka or an equivalent broker — partitioning, ordering, consumer lag, replay and idempotent consumers.
• Containers and orchestration (Docker, Kubernetes or equivalent) with hands‑on CI/CD ownership; comfortable on AWS or an equivalent cloud.
• Production observability and on‑call experience — you have owned an SLO and led an incident to resolution.
• Solid understanding of distributed systems design and trade‑offs, with strong command of data structures, algorithms and design patterns.
• Demonstrated daily use of AI coding tools such as Claude and Cursor to ship production software, with clear judgement about where not to rely on them.
• Clear written communication — design documents, RFCs and post‑mortems that others