โšก New

Staff Engineer

Moneyview

Bangalore BazaarFull-timeMid LevelOn-site

Job Description

Job: Staff Engineer / SDE-4 โ€” Backend (Lending Systems)

Experience: 9โ€“12 Years

Location: Bangalore

Function: Lending Systems


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

Posted Today

Related Jobs

Related Searches

Apply Now