Engineering · Role 02 of 03

Engineering Lead — Lending Platform

Eight years of fintech-grade engineering. Build the infrastructure that lends to India's small businesses, run the team that ships it.

Experience: 8+ years Education: IIT / NIT / BITS / IIIT or equivalent Location: Hybrid Reports to: CTO

You have spent the last eight or more years writing the kind of code that touches money. Origination. Underwriting. KYC. Credit bureaux. Disbursal. Collections. These are not new words to you. You have shipped under regulators, debugged race conditions in payment flows at 3 a.m., and been on the rough side of an integration that did not behave like the documentation said it would.

At Nexo you will own the lending platform. The architecture, the integrations with partner banks (HDFC and others moving), the credit-decisioning models, and the engineering culture of a small but serious team. You will lead 4–6 engineers, mentor the 2026 Fellowship cohort, and work directly with the founder. We are looking for someone from a premier engineering programme — IIT, NIT, BITS, IIIT, or genuinely equivalent — with deep fintech tenure and a working command of the RBI digital lending framework.

What you will do

•Own the lending platform architecture end-to-end.
•Lead a team of 4–6 senior engineers; hire the next two.
•Drive integrations with partner banks and bureau / GST / AA stacks.
•Set technical direction for AI-driven underwriting and signal layers.
•Mentor the 2026 Fellowship cohort and shape the engineering bar.

What you bring

•8+ years of engineering experience.
•A premier engineering programme — or a body of work that reads like one.
•Deep fintech / lending domain — origination through collections.
•Production-scale system design — distributed, transactional, regulated.
•Working knowledge of RBI digital lending, co-lending, TSP/LSP frameworks.

What you do not need

· A management title at your current company. We care about what you have built, not what was on your business card.
· Specific language preferences. We run a polyglot stack and will not interrogate your Python vs Go opinions.
· An ML PhD. Pragmatic ML is fine; we have the data, you have the systems sense.

The written application

Apply for this role.

Nine questions. Most should be answered in 150–400 words each. We will read every word.

Full name *

Email *

Phone (with country code) *

LinkedIn URL *

GitHub or portfolio URL *

Required. Must be reviewable, not just a profile shell.

Engineering programme + graduation year *

Q01 · Career arc

Companies, roles, tenure each — chronological. *

One line per role: company, title, dates, what you owned. We are looking at the shape of the path, not just the names.

Q02 · The deepest fintech / lending system you have owned

Pick one system you owned end-to-end. Walk us through it. *

Architecture (diagram-in-words is fine), scale numbers (TPS, volumes, account count), the hardest correctness problem you had to solve, and what you would do differently today. Don't expose anything confidential.

Q03 · Bug or refactor — your choice

Either: the most subtle production bug you have debugged. Or: the most ambitious refactor you have led. Pick one. *

We want to see how your mind moves under pressure. Show us the trail — symptom, hypothesis, dead ends, real cause, fix.

Q04 · RBI digital lending fluency

How deeply have you worked under RBI's digital lending guidelines? *

Self-rate 1–5 (1: read once; 5: have lived with TSP/LSP, FLDG, KFS, AA, co-lending end-to-end). Then justify the rating with a specific example — a control you implemented, an audit you survived, a clause you argued with legal.

Q05 · Team leadership

Have you led an engineering team? Size, duration, what got better under you. *

If you have not formally managed, tell us about being the senior IC who set the bar — same shape of answer.

Q06 · AI tooling in your workflow

How do you use Claude Code, Cursor, or other agentic tools today? *

Honest answers. Where they save you time, where they fail, what you have stopped using. We are running a fellowship around this; we want to know how you think about it.

Q07 · Why leave / why Nexo

Why are you considering leaving your current role, and why Nexo specifically? *

Read the materials before answering. Tell us what's right, what's not yet right, and what you would push us on technically.

Q08 · One opinion you hold strongly

One opinion you hold about engineering for regulated systems that most engineers would push back on. *

Not a hot take for the sake of it. The thing you actually believe.

Q09 · The basics

Notice period, earliest start, current compensation band (cash + equity if any), expected band, location flexibility. *

Direct answers please.

Optional · Resume / CV

Resume link (Drive / Dropbox / Notion / personal site)

By submitting, you agree that we may store your responses for the purpose of evaluating this application. We will not share them outside Nexo.

Trouble with the form? Email your responses directly to hello@nexo.money.