Start Your Career on Software That Real Lenders Depend On
We are a small software company in Chennai, building for India's non-banking financial companies since 2010. We are hiring graduates — people in their first job, not their fifth — and putting them on production code with someone experienced sitting next to them.
What we actually do — in plain language
Most graduates have not heard of an NBFC, and the ones who have will not know what regulatory reporting involves. Do not skip this section; it is what makes the rest of the page make sense.
Who we build for. India has thousands of finance companies that lend money without being banks — for a shop's working capital, for a two-wheeler, against gold, to a self-help group in a village. They are called NBFCs, and they are regulated by the Reserve Bank of India.
The first problem we solve. Every one of those lenders has to file detailed returns with the RBI on a fixed schedule, in a machine-readable format called XBRL. Most of them still do it by hand, in spreadsheets, in the last week of the month. We are building software that does it from their own data instead.
The second problem we solve. Before lending, the lender has to work out whether the borrower can actually repay. For a salaried customer that is easy. For a shopkeeper who deals mostly in cash, it is not. So we read the borrower's bank statement — with their consent — and reconstruct what comes in, what goes out, and what they are already repaying to someone else. That product runs on a large language model, which is the interesting part engineering-wise, and we will come back to it below.
Neither problem is glamorous. Both are real, both are paid for, and in both cases the person on the other end has a genuine deadline. You will not spend your first year building an internal dashboard nobody opens.
You will ship to production in your first few weeks
We are small. There is no bench, no shadow project, no six-month training programme that ends in a certificate. Your code goes in front of users, which is uncomfortable at first and is the fastest way anyone has ever learned to write software.
You will work on LLMs in production, not in a tutorial
Our bank statement analyser calls a large language model to extract structured data from PDFs that arrive in a few hundred different layouts. Making that reliable — prompting, validating output, handling the cases where the model is confidently wrong — is real engineering, and it is a skill the market is paying a lot for right now.
You will learn a domain, not just a framework
Frameworks change. Knowing how Indian lending and RBI reporting actually work is knowledge that compounds, transfers across employers, and is scarce. Two years here and you will understand a regulated industry from the inside.
You will be able to see the whole system
In a large company you own one service and infer the rest. Here you can read the entire codebase, follow a request from the browser to the database, and know why every part of it exists.
You will talk to the people who use what you build
Not through three layers of product management. You will hear a compliance officer explain why a filing deadline matters, which is the only way to develop judgement about what to build.
We are not a services company staffing you out
You will not be placed at a client site to work on someone else's product under someone else's badge. We build our own software, and you build it with us.
And the honest part
We are a small company, not a large one, and that cuts both ways. There is no free lunch, no campus, no bus, no big-brand name to drop at a family wedding. Pay is competitive for a company our size, not competitive with a product-multinational's fresher package — and we would rather you know that now than find out in the offer conversation. There will be weeks when the work is unglamorous: reading a bank's PDF format, chasing why one figure in a return does not tie. If you want a large structured graduate programme with a cohort of two hundred, we are genuinely the wrong choice, and that is fine.
What you would work with
Backend — PHP and Symfony. Our APIs are built on Symfony. If you have never written PHP, that is not a problem and we do not expect it — the concepts transfer from any language you learned in college, and everyone here learned the framework on the job.
Frontend — React, built with Vite, and Bun. Our interfaces are React applications. Vite for the build, Bun for the runtime and package management — which means the toolchain you learn here is the current one, not one you will have to unlearn at your next job.
Large language models — Claude Opus, from Anthropic. The statement analyser sends documents to Claude and turns the response into structured, validated data. You would work on prompts, on the validation layer that catches bad extractions, and on the checks that make the output trustworthy enough for a lender to underwrite against. Not a side experiment — it is how the product works.
Data — MySQL and MariaDB. Real schemas, real data volumes, and the kind of query you have to think about before you write.
Testing — PHPUnit and Playwright. Unit tests on the backend, browser tests end to end. You will be expected to write them, and you will be shown how.
Infrastructure — Ubuntu, on DigitalOcean and AWS, with Git and Jenkins. Our own servers, our own pipeline, and Munin watching them. Nobody here is insulated from how the thing actually runs — which is uncommon in a first job and is how you learn what production means.
XBRL and regulatory data. Generating filings that pass the regulator's validation. Fiddly, exacting, and a genuinely uncommon specialisation.
Integrations. Credit bureaus, and the loan origination and core systems our clients already run. This is where you learn that real-world APIs are nothing like the ones in tutorials.
One thing we will tell you in the interview anyway, so here it is up front: part of our platform runs on an older major version of Symfony that is past its support window, and moving it forward is real work on our roadmap. If you join, you will likely be part of that. Upgrading a live production codebase without breaking the people using it teaches you more than any greenfield project will — and we would rather say so here than have you discover it in week two.
Open roles
Two graduate roles. Freshers welcome.
Take a look at the openings below, then apply with a CV. That is all we need to start.
What the first year looks like
Month 1 — You get a real task in your first fortnight, small and low-risk, with someone reviewing every line you write. You spend the rest of the time learning what an NBFC is and why any of this exists.
Months 2–3 — You own a feature end to end, still reviewed. You sit in on a client conversation and hear the problem in the user's own words.
Months 4–12 — You take on a part of a product and become the person who knows it best. You will have shipped things that people at regulated lenders use in their working week.
Throughout — Every piece of code you write is reviewed by someone more experienced, and asking a question is never treated as a cost.
How our hiring process works
- Apply — the form below. A CV is enough; a cover letter is optional and we do not weigh it heavily.
- A short call (20 minutes) — we tell you about the work, you tell us what you are looking for. Not a test.
- A practical exercise — a small, realistic problem, done in your own time.
- A technical conversation — we go through your exercise together, and talk through how you would approach a problem. No trick puzzles, no whiteboard algorithms you would never use here.
- A conversation about the offer — role, pay, and what your first three months look like.
Our commitment: you will hear back from us at every stage, including when the answer is no. If we are not moving forward we will tell you, rather than leaving you to guess.
Apply for a role
Tell us which role, and attach your CV. That is all we need to start.
The practical questions
Every one of these gets asked. Answering them here means we are not hiding anything.
Do you offer internships? We don't offer internships.
When do I start? Start after you receive your final results.
I applied before and did not hear back. Apply again. Small teams miss things, and we would rather see your name twice than not at all.
-
No. These are graduate roles. If the posting says graduate, we mean it.
-
Any. We have no institution filter and no CGPA cut-off.
-
No.
-
The position is based in Chennai.