Mainframe Developer (FTE - Jersey City)
Capgemini · New Jersey, United States · 4 wk ago
On-siteFinance$61k–$104k/yrFull-time
We need to output HTML fragment with sections: h3 headings for sections present. We need to extract substantive info: About the role? The posting starts with a paragraph about choosing Capgemini, mission, etc. That could be "About the role" or maybe "About Capgemini". The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only if posting has real specific content.
We have:
- Intro paragraph: "Choosing Capgemini means choosing a company where you will be empowered to shape your career..." That's more about company culture. Could be "About the role" or "About Capgemini". Since they said "About the role" as example, we can use that.
- Job Description: list of duties/responsibilities. That's responsibilities.
- There's a compensation range: base compensation range $61087 to $104364. Also mention additional compensation variable incentives, bonuses, commissions. Also benefits description: comprehensive non-negotiable benefits package, list of benefits: PTO based on grade, holidays, personal days, sick leave, medical/dental/vision, retirement savings, life/disability insurance, employee assistance programs, other benefits.
- There's also location info: Onsite Location: Jersey City, New Jersey, Dallas, TX, Atlanta & Chicago. That could be part of "About the role" or maybe a separate "Location" but not in allowed headings. We could embed location in a paragraph under About the role or maybe under Responsibilities? Probably include in About the role.
- There's also mention of "The base compensation range for this role in the posted location is: $61087 to $104364". That's pay.
- Benefits: described.
- Schedule? Not mentioned. So we should not create Schedule section.
- Requirements/Qualifications/Skills: Not explicitly listed as separate bullet list; the responsibilities include required skills (COBOL, JCL, DB2, VSAM, Informatica, Python, Java/Spring Boot, Oracle, OBIEE, Snowflake, Azure, Confluence, job scheduling tools, version control, SQL). Could treat as Requirements or Skills. The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content. We have responsibilities (duties). We have pay. We have benefits. We have maybe skills/requirements embedded in responsibilities. Could create a "Skills" section listing the technologies. But we must not invent or summarize away detail; we must preserve all substantive information. If we extract skills into a separate list, we are not losing info, just reorganizing. That's allowed as long as we preserve all info. However we must not create sections with filler text. If we create Skills, we need to ensure we have specific content. We can list the technologies mentioned: COBOL, JCL, DB2, VSAM, Informatica, Python-based ETL, Java/Spring Boot APIs, Oracle data stores, OBIEE, Snowflake, Azure-based cloud platform, Confluence, job scheduling tools, version control, database management (SQL, stored procedures). That's specific.
We also have responsibilities list: many bullet-like sentences. We should convert to
- .
We also have location: could be in About the role paragraph.
We must not repeat job title as heading (not given). No Job ID.
We must remove boilerplate: EEO, legal, disclaimer, etc. Also remove "Important Notice", "Disclaimers", "Click the following link..." etc. Also remove "Capgemini is a global business..." paragraph at end (boilerplate). Also remove "This is a general description..." etc. Also remove "Physical, mental..." etc. Also remove "Please be aware that Capgemini may capture your image..." etc. Also remove "All qualified applicants..." etc. Also remove "Capgemini provides compensation range information..." etc? Actually that is part of pay transparency; but we already have pay range. The text after that about compensation may be considered boilerplate but it's still about compensation. However we might keep the pay range and maybe a short note about variable incentives. The rest about compensation being not earned etc is legal boilerplate; we should remove.
We must preserve all substantive information: the pay range, variable incentives eligibility, benefits details, responsibilities, skills, location, company intro.
Let's craft HTML:
About the role
Choosing Capgemini means choosing a company where you will be empowered to shape your career in the way you’d like, where you’ll be supported and inspired by a collaborative community of colleagues around the world, and where you’ll be able to reimagine what’s possible. Join us and help the world’s leading organizations unlock the value of technology and build a more sustainable, more inclusive world. Onsite locations: Jersey City, New Jersey; Dallas, TX; Atlanta; Chicago.
Responsibilities
- Provide hands-on development and support for IBM z/OS mainframe applications, including COBOL, JCL, DB2, and VSAM, ensuring high availability, performance, and reliability of critical business systems.
- Analyze and maintain large-scale legacy application portfolios, including batch and near-real-time processing, supporting production workloads, defect resolution, and performance tuning.
- Support enterprise data integration by enabling mainframe batch and near-real-time feeds into downstream systems and the Data Warehouse, collaborating with data and integration teams using Informatica and Python-based ETL processes.
- Partner with modernization and cloud teams to support mainframe-to-cloud migration initiatives, including application inventory, dependency analysis, data extraction, and coexistence strategies with Java/Spring Boot APIs and Oracle data stores.
- Work closely with reporting and analytics teams supporting OBIEE and Snowflake consumers of mainframe data, ensuring data accuracy, completeness, and timely data refreshes.
- Contribute to system documentation, operational readiness, and decommissioning planning, supporting the transition from on-premises mainframe systems toward a modernized Azure-based cloud platform.
- Analyze and modify system components (programs, jobs, procedures, databases) based on technical and functional requirements.
- Execute production deployments in alignment with release cycles and priority schedules.
- Monitor production jobs for successful execution and troubleshoot failures as they arise, ensuring quick resolution.
- Document analysis, modifications, and deployment processes using Confluence for team collaboration and future reference.
- Maintain proficiency in job scheduling tools, version control, and database management (SQL, stored procedures).
Skills
- COBOL, JCL, DB2, VSAM
- Informatica and Python-based ETL
- Java/Spring Boot APIs
- Oracle data stores
- OBIEE and Snowflake
- Azure-based cloud platform
- Confluence
- Job scheduling tools
- Version control
- SQL and stored procedures
Pay
The base compensation range for this role is $61,087 to $104,364. This role may be eligible for additional compensation such as variable incentives, bonuses, or commissions, depending on the position and applicable laws.
Benefits
- Paid time off based on employee grade (A‑F): vacation 12‑25 days, company paid holidays, personal days, sick leave
- Medical, dental, and vision coverage (or provincial healthcare coordination in Canada)
- Retirement savings plans (e.g., 401(k) in the U.S., RRSP in Canada)
- Life and disability insurance
- Employee assistance programs
- Other benefits as provided by local policy and eligibility