A Gujarat-based technology employer is hiring a Senior Mainframe Developer for an on-site role in Thaltej, on SG Highway in Ahmedabad. The position is full-time and sits within the software development function, working on systems that still run a large share of the company's core transaction processing.
The developer joining this team will spend most days close to production code that has been in service for years and still carries real weight. New feature work gets planned against existing batch cycles, so timing and sequencing matter as much as the logic itself. When something breaks at 2 a.m. because an overnight job failed, someone on this team gets the page, traces the failure back through the JCL, and fixes it before the business day starts. That kind of pressure is routine here, not an exception worth flagging separately.
Companies still hiring for COBOL and JCL work in a market this size tend to be banks, insurers, and larger manufacturing or logistics firms that built their core systems decades ago and never fully migrated off them. That's the general profile of the employer behind this listing too, though the exact company name isn't disclosed at the posting stage. What matters more for a candidate deciding whether to apply is the nature of the work itself: maintaining and extending a system that can't afford downtime, using tools that have fallen out of fashion in newer software roles but remain critical wherever they're still running.
What the role covers
Day-to-day, the responsibilities are concrete rather than abstract:
- Write new COBOL functionality against requirements handed down from the project team
- Trace production and batch failures back through JCL and DB2 until the root cause is found
- Keep documentation current so the next engineer isn't starting from scratch
- Review teammates' code changes and submit work for review in turn
- Coordinate feature timing with existing batch processing windows to avoid conflicts
Skills the team needs
Applicants should be comfortable with COBOL, JCL, DB2, and general mainframe systems work, along with hands-on experience running and troubleshooting batch processing jobs. These aren't nice extras; a candidate without solid footing in most of them will struggle in the first month.
On top of that, a few things aren't required but do strengthen an application: exposure to CICS transaction processing, familiarity with VSAM file structures, some background with a source control and deployment tool like Endevor or ChangeMan, and any prior work writing DB2 stored procedures. None of these are dealbreakers on their own.
Education and experience
The education bar for this role is a completed bachelor's degree, with computer science or information technology being the most common route into mainframe work. Naukri Mitra has seen employers in Ahmedabad occasionally waive this for candidates with an unusually strong project portfolio, though that's the exception rather than the norm at senior levels.
On the experience side, the employer is looking for at least 90 months of hands-on mainframe development work. That generally means someone who has already carried production support responsibilities, not just built features in a sandboxed test environment. Given the seniority bar, this posting is really aimed at mainframe developer jobs for experienced professionals in Ahmedabad rather than early-career applicants.
Recruiters for this role usually want to see progression, not just years logged. A candidate who spent seven years maintaining the same three programs without ever touching a new system will get more scrutiny in the interview than one who moved across two or three different mainframe environments in less time. It's not a strict rule, but it does shape how the technical interview questions get framed.
Compensation and benefits
The role pays up to ₹126,000 per month, reflecting the seniority and the specialized skill set involved. A mainframe developer salary in Ahmedabad at this level typically sits well above the city's general software development pay, given how few engineers still maintain deep fluency in COBOL and JCL.
Beyond salary, the package includes:
- Cab or commute support for the daily trip in and out
- On-site cafeteria facilities at the Thaltej office
- Performance-linked annual bonuses
- Health coverage
- Paid leave
Working on-site in Thaltej
This is an on-site position, not a hybrid or remote arrangement. The office sits on SG Highway in Thaltej, a part of Ahmedabad with a fairly dense concentration of IT employers, which makes the commute manageable for most candidates already based in the western part of the city. Anyone weighing a move to Ahmedabad specifically for this job should factor that location into their housing search.
The engineering group here is small enough that a new hire's changes get noticed quickly, for better or worse. Reviews tend to be direct, and there isn't much bureaucracy standing between writing a fix and getting it into the next release cycle. Mainframe teams of this size often run leaner than their web or mobile counterparts, partly because the systems themselves demand fewer moving parts to manage well.
Release cycles on mainframe systems don't move at the pace of a typical web sprint. Changes go through a formal change control process before they touch production, which can feel slow to anyone coming from a faster-moving stack. Most developers who stay in mainframe work long-term end up preferring it once they get used to it; the deliberate pace means fewer surprises and a lower tolerance for shipping half-tested code, which suits people who'd rather get something right the first time than patch it repeatedly afterward.
How to apply
Candidates who meet the education and experience bar above should submit a resume that clearly lists mainframe project history, including the specific systems and batch environments worked on. Applications without at least some verifiable COBOL or JCL project experience are unlikely to move forward, given how specialized the skill requirement is. Interviews for this role typically include a technical round focused on debugging scenarios rather than open-ended trivia, so candidates should be ready to walk through how they've traced a real production failure in the past.
It also helps to mention specific job control statements or utilities you work with regularly, since a resume that only says "mainframe experience" without naming tools makes screening harder for both sides. Anyone relocating to Ahmedabad for this position should plan for a short-notice discussion during the offer stage, since on-site roles at this seniority level tend to move through final approvals faster than remote postings.
