Mainframe Developer, Saravanampatti, Coimbatore (Part-Time)
A team in Saravanampatti is hiring a part-time Mainframe Developer on-site, paying up to ₹41,500 per month. This is a legacy systems role in the truest sense: COBOL, JCL, DB2, and batch jobs that have been running reliably for years and need someone who actually understands how they hold together.
Part-time here doesn't mean light on responsibility. The systems this role touches process real transactions, and a batch job that fails overnight becomes someone else's problem by morning if it isn't caught. The schedule is flexible, but the standard of work isn't lower for it.
Companies still running mainframe infrastructure tend to have a real problem finding people to maintain it, since fewer developers are trained in COBOL and JCL each year, while the systems themselves aren't going anywhere soon. That's part of why this particular role pays reasonably well for a part-time position; the skill set is genuinely scarce locally.
What you'd be doing
- Write and modify COBOL programs to implement new business logic or fix defects in existing code
- Develop and maintain JCL scripts for batch job execution and scheduling
- Work with DB2 databases, including writing and tuning SQL used within mainframe applications
- Debug production issues in batch processing, tracing failures back through job logs and abend codes
- Document code changes and participate in peer reviews before anything moves toward production
A good chunk of the work is maintenance rather than new development, and that's normal for mainframe roles generally. The systems are old, but they're also the ones the business actually depends on, so changes get made carefully rather than quickly.
New feature work does come up, usually a business requirement that means adding a new field to a report, adjusting logic in an existing program, or writing a new batch job to handle something the current suite doesn't cover. It's rarely dramatic, but getting it wrong on a mainframe tends to be more consequential than on a smaller, newer system, since so much else is often built on top of it.
Who fits here
A four-year degree is the baseline, and it doesn't need to be a specific specialization as long as it's technical. What matters more is genuine hands-on time with COBOL and JCL, since mainframe skills aren't something most people pick up casually outside formal training or a job. Three years of relevant experience is expected, ideally including direct exposure to batch processing environments rather than mainframe coursework alone.
This kind of role tends to draw two different types of candidates: people who trained specifically in mainframe technology early in their career and stuck with it, and people transitioning back into mainframe work after time spent elsewhere. Both are welcome here, as long as the COBOL and JCL fundamentals are solid.
Experience level matters more than a specific certificate or training program name on a resume. Someone who spent three years maintaining a payroll or banking batch system will generally be evaluated the same way as someone with equivalent time on an insurance claims platform, since the underlying skills transfer well between industries in mainframe work.
Core skills required
- COBOL programming, comfortable reading and modifying existing codebases, not just writing from scratch
- JCL scripting for batch job control and scheduling
- DB2 database work, including SQL within a mainframe context
Useful beyond the basics
Familiarity with CICS transaction processing helps if the role expands into online systems later. Experience with VSAM file structures or mainframe utilities like SORT and IDCAMS speeds up ramp-up considerably. None of these are dealbreakers if the core COBOL and JCL skills are strong, since they're the kind of thing picked up on the job within the existing systems.
Schedule and pay
The role is part-time, with in-office hours worked out directly with the team rather than being locked to a rigid shift pattern. Pay tops out at ₹41,500 a month depending on experience. Leave scales down to match reduced hours rather than following a full-time allocation, and there's an output-based incentive component on top of the base rate. Naukri Mitra has flagged this listing as one of the few part-time mainframe roles currently open in Coimbatore, which is worth knowing given how rarely this specialty gets offered on a part-time basis at all.
For candidates relocating to Coimbatore specifically for this position, the employer covers moving costs and helps with finding accommodation during the transition.
Working in Saravanampatti
Saravanampatti sits on the northern edge of Coimbatore, away from the older textile-industry core of the city, and it's where a lot of the newer IT and electronics companies have set up over the last decade. Traffic on the main stretch gets heavy around shift-change hours, so factoring that into a commute is worth doing before accepting an offer.
The team here is small, and a part-time mainframe developer isn't an afterthought hire; it's a specific gap the team needs filled by someone who already knows this stack. That tends to mean real ownership over a defined set of systems rather than getting pulled into whatever's urgent that week.
Coordination with the rest of the team happens mostly through scheduled check-ins rather than constant meetings, which suits the part-time arrangement well. Nobody expects someone working reduced hours to be available for every ad hoc conversation, so the handoffs and updates are structured to work around that.
How to apply
Send a resume that specifies which mainframe environments and tools you've actually worked with, COBOL dialects, JCL experience, DB2 versions, rather than a generic list of legacy skills. The interview includes a technical discussion built around real code and job scenarios, since that's a far better test of mainframe ability than general programming questions.
If you've been out of mainframe work for a stretch but have a solid background in COBOL and JCL, it's still worth applying. The core logic doesn't change much even after a few years away, and most people find it comes back faster than they expect once they're looking at real code again.
