Our journey so far

Jupiter was founded in 2019 by Jitendra Gupta. Best known as Citrus Pay’s founder, Jiten found himself wondering why personal finance experiences were not customer-centric when everything else like food ordering and entertainment were. That’s how our journey began in 2019, with a simple, powerful idea: to create a modern, customer-centric experience that empowers individuals when it comes to their money.

From our humble beginnings, we've strived relentlessly to make managing money easier. In 2021 when we launched we had a waitlist with over 100,000 people eager to experience the world of Jupiter - and within 10 months we crossed 1 million users. Today, we have 2.8 million+ happy users on Jupiter

Our Insights feature today tells how much and where you’ve been spending automatically, even on your other savings accounts! Our Edge CSB Bank RuPay credit card is getting a lot of love for it’s head-turning transparent design, not to mention it being a rewarding experience. Our No-Penalty SIP and Daily SIP at Rs 10/- has helped scale our investments business and we have over 100,000 users investing on our platform to fulfill their money aspirations.

We've embraced cutting-edge technology, harnessed the power of data analytics, and assembled a diverse team of creative thinkers and industry experts who share our vision for a more accessible, transparent, and inclusive financial ecosystem. We’re now looking for like-minded folks to join the crew.

About the Role

Risk Tech is the engine room of Jupiter's lending business. Every rupee we disburse passes through systems this team owns: underwriting, eligibility, KYC, pre-disbursal checks, fraud prevention, and pricing while decisioning in real time across our Loans and Cards ecosystems, within the regulatory guardrails of our banking and NBFC partners.

As an SDE-3 on this team, you won't just build features on the risk platform, you'll own the architecture of the systems that decide who gets credit, how much, and at what price. You'll set the technical direction for real-time decisioning at scale, make the design calls that others build on, and raise the bar for reliability in a domain where a bad deploy has both a financial and a regulatory cost.This is a high-ownership, high-leverage role for someone who wants their engineering decisions to move the business, not just the codebase. This role will be owning larger swathes of the risk platform and setting technical direction across the team.

What you'll do

- Own risk decisioning systems end-to-end — architect and evolve the platform combining bureau, income,fraud, and third-party signals into real-time underwriting and pricing decisions.
- Lead the rule-engine architecture that lets risk and policy teams configure and roll out strategies dynamically,



shrinking the time from policy idea to production decision.
- Design for co-lending and multi-lender models — build pricing and underwriting flows that support per-entity policy, co-lending splits, and fast partner onboarding as we scale our lending partners.
- Build fraud-prevention infrastructure — cross-product systems (e.g. negative databases, identifier-blocking,velocity and device signals) that protect the Loans and Cards ecosystems without adding friction for good users.
- Set the standard for scale and reliability — own latency, throughput, and correctness for systems processing tens of thousands of decisions a day, where downtime and defects carry real financial and compliance risk.
- Drive experimentation infrastructure for pricing and risk policies, enabling controlled rollouts and measurable yield improvements.
- Make the hard architecture calls in ambiguous, cross-team problems — data models, event-driven contracts, service boundaries — and bring the rest of engineering along with you.
- Mentor SDE-1s and SDE-2s, review designs and code, and raise the overall engineering bar of the team.
- Partner deeply with Risk, Analytics, Product, and Compliance — translate credit policy, regulatory requirements (RBI, partner bank/NBFC guardrails), and fraud strategy into robust, auditable systems.

What we're looking for

- 6+ years of backend engineering experience, with a track record of owning complex, high-scale systems end-to-end.
- Strong command of Java and Spring Boot and clean, production-grade system design on the JVM.
- Deep, hands-on PostgreSQL expertise — advanced query design and tuning, indexing strategy, execution-plan analysis, transactions and isolation, schema design, and diagnosing performance under real production load. This is a core, non-negotiable strength for the role.
- Deep experience with event-driven and distributed architectures — Kafka, queues/streams (SQS, SNS, EventBridge or similar), idempotency, eventual consistency.
- Breadth across the wider data layer beyond PostgreSQL — NoSQL (DynamoDB) and analytical/search stores (ClickHouse, ElasticSearch) — and sound judgment on which store fits which access pattern at scale.
- Advanced working experience with a public cloud (AWS preferred) and the Kubernetes ecosystem —deploying, scaling, and operating containerized services in production, not just consuming managed services.




- Experience building low-latency, high-reliability real-time systems — caching (Redis/ElastiCache) and a solid instinct for failure modes under load.
- Hands-on with a monitoring and alerting stack — Prometheus, Grafana, and alerting/on-call systems — with the instinct to instrument systems so problems surface before users feel them.
- Demonstrated technical leadership — you've owned architecture for a significant system, influenced peers,and driven decisions across teams, not just within your own scope.
- Comfort operating in ambiguity — you can take a fuzzy business problem and turn it into a clear technical plan.

Strong plus

- Scala preferred, but not required — strong functional-programming fundamentals in a modern JVM language are what matter most. Solid Kotlin, or idiomatic Java 17+/21 (records, sealed types, pattern matching, streams), is a strong signal you'll pick up our Scala quickly.
- Experience in fintech, lending, or risk/underwriting systems — bureau data, FOIR/eligibility logic, KYC, pre-disbursal checks, or credit pricing.
- Familiarity with co-lending / multi-lender architectures and partner integrations.
- Exposure to fraud prevention systems and signals.
- Rule-engine or policy-configuration platforms.
- Delivery tooling: Docker, CI/CD (GitHub Actions, Spinnaker), and workflow orchestration (Airflow).

What sets an SDE-3 apart here — and the path to SDE-4

We hire SDE-3s for judgment and leverage, not just throughput. At this level we expect you to:

- Own outcomes, not tickets — you're accountable for whether a system works in production and moves the business, end-to-end.
- Design what others build on — your architecture decisions define the constraints and interfaces for the rest of the team.
- Reduce ambiguity for everyone else — you turn unclear, cross-functional problems into clear technical direction.
- Multiply the team — through mentorship, design review, and the standards you set and defend.
- Balance speed with rigor — in a regulated, money-moving domain, you know when to move fast and when correctness and auditability come first.

The path for risk tech person is about widening that scope: from owning a system to owning a domain, from influencing your team to setting technical direction across Risk Tech, and from solving hard problems to shaping which problems we take on. We want someone who's ready to grow into that.

Why Risk Tech at Jupiter

You'll work at the intersection of engineering, credit risk, fraud, and regulation—where the problems are genuinely hard, and the impact is measurable in disbursals, approval rates, loss rates, and yield. The systems you build directly shape Jupiter's lending business, and you'll have the ownership to build them right

📌 Software Development Engineer III — Risk Tech (Karnataka)
🏢 Jupiter
📍 Karnataka