Remote COBOL Developer - z/OS & Banking Systems

CAI

City of Albany (NY)

Remote

USD 96,000 - 102,000

Full time

2 days ago

Be an early applicant

Get a reply from this employer

Your resume and cover letter, tailored to exactly what they’re hiring for.

Get past ATS filters

Benefits offered by this job

Medical, dental, and vision insurance

401k retirement plan

Job summary

CAI is seeking a Cobol Developer to build a new pooled-account structure inside a running z/OS core, with remote work options. This contract role requires strong COBOL, JCL, VSAM/Adabas, and financial systems experience.

You will analyze, design, and implement end-to-end changes, document processes, and support the first production cycles while ensuring controls and audit trails are in place. The ideal candidate has 5+ years of Enterprise COBOL on z/OS, experience with NaturalOne, and a track

Qualifications

5+ years of Enterprise COBOL development in a z/OS environment (batch & online).
5+ years of Experience with NaturalOne; developing, debugging, and deploying.
Experience with Natural programs, subprograms, and maps.
3+ years of JCL development and production support.
3+ years of experience with financial/accounting systems development or support including double-entry posting, balance/accrual maintenance, value dating, reconciliation, and month-end closeouts in a regulated environment.
3+ years of experience with VSAM and Adabas including file design and performance behavior.
3+ years of experience with tracing undocumented logic through copybooks, call chains, and job streams.

Responsibilities

Analyze the current account master, posting, and balance-maintenance programs to establish where composite reservoir accounts must be recognized, and document what you find.
Design and code the new account type end to end: master file and table structures, account opening and closing, participant linkage, sweep and reverse-sweep logic, allocation and interest apportionment, and closing balance derivation.
Modify batch COBOL programs and JCL and extend the nightly and month-end cycles to include the new processing without lengthening the batch window beyond agreed limits.
Add new CRAs to the audit trail, exception reporting, and reconciliation controls the new function requires, working with accounting stakeholders on what must be evidenced.
Produce test data, unit and regression test packs, and parallel-run comparisons against current production output; investigate every difference until it is explained.
Support implementation, conversion of any in-scope existing accounts, and early-life production runs, including on-call cover during the first cycles.
Leave behind program documentation, data-flow notes, and runbook updates that the support team can work from