A fintech company in Vijay Nagar, Indore, is hiring a part-time Fintech Software Engineer (on-site), paying up to 41,000 INR a month. The role sits on a small team building and maintaining payment and lending features, so the code you write here touches actual money movement rather than internal tooling. It's a lean team by design, and a new hire is expected to read and write real feature code within the first couple of weeks rather than spending a full month on onboarding tasks alone.
Financial software carries a different weight than most application work. A rounding error in a display component is annoying; the same error in a fee calculation is a reconciliation problem that someone in finance has to explain later. That distinction shapes how the team reviews code and how much testing a change goes through before it ships, even when it looks small on the surface. The company processes payments and short-term loans for a client base that's grown quickly over the past year, so the volume moving through the systems this engineer touches is meaningfully larger than it was even twelve months ago.
- Write and maintain application code across the platform's core payment and account features
- Collaborate with product, design, and QA on new features from early planning through release
- Fix bugs surfaced during testing, prioritizing anything touching transaction accuracy or account balances
- Build and consume internal and third-party APIs used for payment processing and account data
None of these responsibilities exist in isolation. A bug fix in a fee calculation often means touching the same API another feature depends on, so a change that looks contained on paper can ripple across two or three other parts of the system by the time it's actually tested and shipped.
Background the team is looking for
A four-year degree is the baseline requirement, most commonly in a computing discipline, though the team pays closer attention to whether a candidate has actually shipped production code than to what the degree itself is called. Forty-two months of hands-on development experience is expected, ideally with at least some of that time spent on a system where correctness mattered as much as it does here. Candidates coming from consumer apps or internal tools sometimes need a beat to adjust to how much slower and more deliberate financial code review can be than what they're used to.
Java or Python is the core language requirement. Beyond that, the role needs someone comfortable designing and working with APIs, along with a working grasp of security basics: how sensitive data should be handled, why certain endpoints need stricter validation than others, and what a reasonable authentication flow looks like. Direct financial systems knowledge helps candidates get productive here faster than almost anything else on the list, since a good developer without fintech context will still need time to learn why certain business rules exist before they can safely change the code around them. That said, plenty of strong engineers have joined this kind of team from adjacent domains and picked up the financial specifics within their first couple of months.
A few things aren't required but move an application up the pile: prior work at a bank, NBFC, or payments company, familiarity with a specific compliance framework like PCI-DSS, or experience integrating a payment gateway end to end rather than just consuming its documentation. None of these are dealbreakers, but they cut down on the ramp-up time a new hire otherwise needs before touching anything customer-facing.
Schedule, pay, and benefits
The role is part-time with flexible in-office scheduling, and pay tops out at 41,000 INR per month. That figure sits comfortably above what Naukri Mitra typically sees for part-time fintech software engineer jobs in Indore, which tend to compress pay more aggressively than full-time roles in the same category. Factor in the gap if you're comparing multiple part-time offers side by side, since a lower headline number can hide a schedule that's less flexible than it first appears.
- Pro-rated paid leave, calculated against actual scheduled hours
- Performance-based incentives tied to release quality and delivery timelines
- Relocation assistance and accommodation support for candidates moving to the area
What the work is actually like
A typical week splits between building new functionality and responding to whatever testing or production monitoring turns up. Release cycles are shorter here than at a larger fintech company, which means changes get in front of users faster but also means less time to catch an edge case before it's live. The team compensates by keeping test coverage tight around anything that touches balances or transaction records, so a change that looks minor in the code review can still take a few extra hours if it needs a corresponding test.
Vijay Nagar has grown into a reasonably active pocket for IT and financial services firms over the past few years, and the office is close enough to the main commercial stretch that lunch options and transit access aren't a real day-to-day concern. Part-time engineers here typically work a fixed core block with some flexibility built in around the edges, which tends to suit people balancing this role against a second commitment like a degree program or a smaller side project. The team has hired part-time engineers into full-time roles before when both sides wanted to make that shift, though it isn't a guaranteed path and depends entirely on headcount at the time.
Applying
Send a resume along with a short description of the most complex API integration or payment-adjacent feature you've built, including roughly how large the user base or transaction volume was. Candidates who advance past the initial screen go through a technical interview involving a realistic bug in a small financial calculation, not a generic algorithm question. Most candidates hear back within ten days of applying, and the team is upfront during interviews about which parts of the schedule are fixed versus negotiable. Anyone relocating for the role should raise it early, since the accommodation support process typically needs a couple of weeks' lead time to arrange properly.
