MIHAN in Nagpur is the base for this Associate Fintech Software Engineer role. It's full-time and on-site, with pay up to INR 60,500 per month.
The skills this role runs on
Financial systems knowledge sits at the heart of this one, since the codebase deals with money moving between accounts, not just generic business logic. Java or Python covers the programming side, alongside solid API work and a working grasp of security basics. That last piece matters more here than in a typical software role, given how much of fintech work touches sensitive financial data.
A candidate doesn't need deep specialization in all four areas from day one. Someone strong in Java with a genuine interest in how financial systems actually work, but lighter on formal security training, can still be a good fit if they're willing to build that piece up on the job.
Nice to have
- Exposure to payment gateway integrations, whether from a course, internship, or personal project
- Some familiarity with regulatory frameworks like PCI-DSS or RBI compliance guidelines
- Comfortable working with SQL and relational databases beyond the basics
- Understanding of microservices architecture, even at a conceptual level
What you'd actually be doing
- Implement new features based on project requirements handed off from the product and compliance teams
- Debug and resolve technical issues, particularly the kind that surface only once real transaction volume hits a feature
- Document work clearly enough that a teammate can trace a decision back months later, which matters a lot in a regulated environment
- Participate in code reviews, since a mistake in financial logic tends to be far more costly than one in a typical consumer app
Imagine a reconciliation feature that's supposed to match incoming payments against pending invoices. If it starts mismatching a small percentage of transactions after a schema change, tracking that down means comparing the old and new data formats line by line until the discrepancy surfaces, then writing a fix that also accounts for whatever already got mismatched before the bug was caught. That kind of careful, methodical debugging comes up more often here than flashy feature work does.
Feature work still makes up a solid chunk of the role. A new API endpoint for a partner integration or a dashboard view that pulls together transaction history for internal ops teams are the kinds of builds that come through regularly. The difference from a general software job is that almost everything eventually touches money somewhere in the chain, which changes how carefully a feature gets tested before it ships.
Getting in the door
The degree requirement points to computer science, information technology, or a closely related field. Eighteen months of relevant experience is what the role calls for beyond that, which puts this squarely in associate territory rather than fresher territory. Someone who's spent their first job or two building general software without fintech-specific exposure is still worth considering if their fundamentals are strong and they show real curiosity about how financial systems work.
Naukri Mitra has noticed that fintech roles at this experience level in smaller cities like Nagpur draw candidates who might otherwise be competing for the same jobs in Pune or Mumbai, simply because the cost of living and relocation package here make the offer more attractive overall.
Eighteen months is enough time to ship a few real features and deal with at least one production incident, without needing years of specialized fintech experience. The hiring team is generally looking for someone who's past the pure-learning phase of a first job but still early enough in their career to grow into the security and compliance side of the work over time.
Pay and what comes with it
- Health insurance
- Paid time off
- Provident fund contributions
- Relocation assistance
- Accommodation support during the transition
The relocation and accommodation pieces are worth taking seriously if you're not already based in Nagpur, since MIHAN sits a fair distance from the older parts of the city and getting settled nearby makes the daily commute a lot easier.
Working out of MIHAN
MIHAN is Nagpur's dedicated economic zone built around aviation, logistics, and IT, and it's grown into a real hub for tech and fintech companies over the past several years. It's quieter than a place like Hinjewadi in Pune, with fewer restaurants and less nightlife in the immediate area, but also less traffic and a shorter, more predictable commute once you're settled in.
Working on-site in a fintech environment specifically means a lot of quick, informal check-ins with compliance and product people who sit nearby, rather than routing every question through a ticket. For engineers early in their fintech careers, that proximity tends to accelerate learning about how the regulatory side actually shapes technical decisions, which is hard to pick up from documentation alone.
Nagpur's broader IT scene is still young compared to the established hubs, which means fewer fintech-specific employers to choose between if this particular role doesn't work out. That's worth weighing for anyone treating this as a stepping stone rather than a long-term base, since switching employers within the same city and specialization is a narrower path here than it would be in Bengaluru or Pune.
How to move forward
Applications that mention any exposure to real financial systems, even a class project involving payment processing or ledger logic, tend to get noticed faster than a general software resume. The interview includes a technical round centered on a realistic debugging scenario, plus a conversation about how the candidate thinks through edge cases where a bug could result in incorrect financial data rather than just a broken feature.
Candidates should come prepared to discuss at least one instance in which they caught a mistake before it shipped or fixed one that got through. Interviewers weigh that kind of concrete story more heavily than a long list of frameworks and languages on a resume.
