Z/OS Mainframe Systems Engineer
TEKsystems · Cedar Rapids, IA · 3 wk ago
RemoteRemoteInformation Technology$45/hrFull-time
We need to output only HTML fragment, no /, no markdown fences. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. Let's parse.
Job description: "We are seeking an experienced Mainframe Systems Programmer/Engineer to support and maintain core mainframe infrastructure in a z/OS Sysplex environment. This role is responsible for the installation, testing, maintenance, documentation, monitoring, and support of mainframe software and components, as well as support for the BMC Control-D output management platform."
That's about the role. So we can have
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. Let's parse.
Job description: "We are seeking an experienced Mainframe Systems Programmer/Engineer to support and maintain core mainframe infrastructure in a z/OS Sysplex environment. This role is responsible for the installation, testing, maintenance, documentation, monitoring, and support of mainframe software and components, as well as support for the BMC Control-D output management platform."
That's about the role. So we can have About the role
with paragraph(s) containing that.
Responsibilities: list of bullet points after "Responsibilities". We need to extract each bullet. The text after "Responsibilities" includes many sentences separated by periods but not bullet list. We need to treat each as a list item. We'll create - for each duty.
Let's list them:
- Provide primary support coverage during U.S. business hours (8:00 AM to 4:30 PM Central Time).
- Participate in an on-call rotation, including after-hours and weekend support.
- Perform daily monitoring and support of mainframe systems and software to ensure overall platform health and stability.
- Troubleshoot and resolve infrastructure and software issues through root cause analysis.
- Support and maintain the BMC Control-D output management environment, including report definitions, mission and decollation processes, and web-based access tools.
- Work with software vendors to troubleshoot issues, gather diagnostics, and implement fixes.
- Monitor key system metrics and proactively identify performance, stability, and optimization opportunities.
- Review system and software information regularly to identify potential defects, maintenance needs, and preventative actions.
- Respond to customer support requests and operational incidents.
- Participate in disaster recovery testing and related preparedness activities.
- Support infrastructure and business-driven projects.
- Install, configure, and maintain third-party mainframe software and software fixes.
- Design and adapt platform solutions to meet business and operational requirements.
- Continuously drive improvements in system availability, operational efficiency, and cost optimization.
That seems all.
Now Required Skills & Experience: list of bullet points after that heading. We'll treat as Requirements or Skills? The instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include. The posting has "Required Skills & Experience" and "Preferred Technical Experience". Could map to Requirements (maybe required) and Skills (maybe preferred). Or we could combine into Requirements and Skills. Let's see: The posting includes "Required Skills & Experience" bullet list (moderate knowledge of IBM z/OS, experience supporting enterprise mainframe environments, strong understanding of IT infrastructure concepts, working knowledge of one or more programming languages such as Assembler, COBOL, REXX, or SAS, experience with JCL, TSO/ISPF, and SDSF, knowledge of BMC Control-D output management systems, experience following structured testing and implementation procedures, understanding of disaster recovery concepts and processes, strong troubleshooting, analytical, and problem-solving skills, strong verbal and written communication skills, high attention to detail and commitment to quality, ability to collaborate effectively with cross-functional teams and stakeholders.)
Then "Preferred Technical Experience" bullet list: IBM z/OS Operating Systems, IBM Mainframe Platforms, Systems Engineering, JCL Development and Administration, BMC Control-D, Sysplex Environments, Mainframe Monitoring and Performance Analysis.
We could put Required Skills & Experience under
Requirements
(or Skills). And Preferred Technical Experience under Skills
(or Qualifications). The instruction says we can have sections like Requirements, Qualifications, Skills. We need to avoid filler. We'll include both.
Pay And Benefits: includes pay range and benefits list. So we need Pay and Benefits sections. Pay: The pay range for this position is $45.00 - $45.00/hr. That's a specific value (same min and max). It's still specific; we should include Pay section. Benefits: list of benefits. So Benefits section.
Schedule: The posting mentions "Workplace Type This is a fully remote position." and "Job Type & Location This is a Contract position based out of Cedar Rapids, IA." Also "Application Deadline This position is anticipated to close on Oct 7, 2026." Not schedule. There's no explicit schedule like shift times besides the support coverage hours (8:00 AM to 4:30 PM Central Time) which is in responsibilities. No separate schedule section. So we should not create Schedule section because no specific schedule info beyond that. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we skip Schedule.
We also have "Job Type & Location" which could be considered metadata; we could fold into a short maybe under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short paragraph for Job Type & Location maybe under About the role or separate
but not as heading. Probably better to include a short
after About the role: "Job Type: Contract. Location: Cedar Rapids, IA (fully remote)." Also include Application Deadline maybe as metadata.
But we must preserve ALL substantive information; do not invent or summarize away detail. So we need to include the job type, location, remote note, application deadline. We'll embed them in a
after About the role.
Now Benefits: list includes many items. We'll create
- for each.
Pay: we can put
The pay range for this position is $45.00 - $45.00/hr.
under Pay
.
Now ensure we don't include boilerplate like EEO, equal opportunity, scam warning, cookie/navigation/legal, duplicated lines. The posting includes a lot of boilerplate about TEKsystems, equal opportunity, etc. We must remove those. Also remove "About TEKsystems" sections, "About TEKsystems And TEKsystems Global Services", etc. Also remove "San Francisco Fair Chance Ordinance", "Massachusetts Lie Detector", "Use of Artificial Intelligence (AI)". All that is boilerplate; we must remove.
Thus final HTML fragment will contain sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Possibly also Qualifications? Not needed.
We need to ensure we don't repeat the job title as a heading. The job title is Mainframe Systems Programmer/Engineer; we must not use that as heading.
Now produce HTML.
Let's craft:
About the role
We are seeking an experienced Mainframe Systems Programmer/Engineer to support and maintain core mainframe infrastructure in a z/OS Sysplex environment. This role is responsible for the installation, testing, maintenance, documentation, monitoring, and support of mainframe software and components, as well as support for the BMC Control-D output management platform.
Job Type: Contract. Location: Cedar Rapids, IA (fully remote). Application Deadline: Oct 7, 2026.
Then Responsibilities:
Responsibilities
- Provide primary support coverage during U.S. business hours (8:00 AM to 4:30 PM Central Time).
- Participate in an on-call rotation, including after-hours and weekend support.
- Perform daily monitoring and support of mainframe systems and software to ensure overall platform health and stability.
- Troubleshoot and resolve infrastructure and software issues through root cause analysis.
- Support and maintain the BMC Control-D output management environment, including report definitions, mission and decollation processes, and web-based access tools.
- Work with software vendors to troubleshoot issues, gather diagnostics, and implement fixes.
- Monitor key system metrics and proactively identify performance, stability, and optimization opportunities.
- Review system and software information regularly to identify potential defects, maintenance needs, and preventative actions.
- Respond to customer support requests and operational incidents.
- Participate in disaster recovery testing and related preparedness activities.
- Support infrastructure and business-driven projects.
- Install, configure, and maintain third-party mainframe software and software fixes.
- Design and adapt platform solutions to meet business and operational requirements.
- Continuously drive improvements in system availability, operational efficiency, and cost optimization.
Then Requirements:
Requirements
- Moderate knowledge of IBM z/OS and mainframe architecture.
- Experience supporting enterprise mainframe environments.
- Strong understanding of IT infrastructure concepts and system operations.
- Working knowledge of one or more programming languages such as Assembler, COBOL, REXX, or SAS.
- Experience with JCL, TSO/ISPF, and SDSF.
- Knowledge of BMC Control-D output management systems and related components.
- Experience following structured testing and implementation procedures.
- Understanding of disaster recovery concepts and processes.
- Strong troubleshooting, analytical, and problem-solving skills.
- Strong verbal and written communication skills.
- High attention to detail and commitment to quality.
- Ability to collaborate effectively with cross-functional teams and stakeholders.
Then Skills (Preferred Technical Experience):
Skills
- IBM z/OS Operating Systems
- IBM Mainframe Platforms
- Systems Engineering
- JCL Development and Administration
- BMC Control-D
- Sysplex Environments
- Mainframe Monitoring and Performance Analysis
Then Benefits:
Benefits
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)
Then Pay:
Pay
The pay range for this position is $45.00 - $45.00/hr.
We should not include Schedule.
Check for any leftover boilerplate: we removed all TEKsystems description, EEO, etc.
Check for duplicate lines: none.
Check for any content we missed: The "Workplace Type This is a fully remote position." we included in location note. Good.
Check for "Job Type & Location This is a Contract position based out of Cedar Rapids, IA." we included.
Check for "Application Deadline This position is anticipated to close on Oct 7, 2026." we included.
Check for "Pay And Benefits The pay range for this position is $45.00 - $45.00/hr." we captured pay and benefits.
Check for "Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following:" we captured list.
Check for "Workplace Type This is a fully remote position." we captured.
Check for "About TEKsystems" etc removed.
Now ensure we didn't inadvertently
Requirements
(or Skills). And Preferred Technical Experience underSkills
(or Qualifications). The instruction says we can have sections like Requirements, Qualifications, Skills. We need to avoid filler. We'll include both. Pay And Benefits: includes pay range and benefits list. So we need Pay and Benefits sections. Pay: The pay range for this position is $45.00 - $45.00/hr. That's a specific value (same min and max). It's still specific; we should include Pay section. Benefits: list of benefits. So Benefits section. Schedule: The posting mentions "Workplace Type This is a fully remote position." and "Job Type & Location This is a Contract position based out of Cedar Rapids, IA." Also "Application Deadline This position is anticipated to close on Oct 7, 2026." Not schedule. There's no explicit schedule like shift times besides the support coverage hours (8:00 AM to 4:30 PM Central Time) which is in responsibilities. No separate schedule section. So we should not create Schedule section because no specific schedule info beyond that. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we skip Schedule. We also have "Job Type & Location" which could be considered metadata; we could fold into a shortmaybe under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short paragraph for Job Type & Location maybe under About the role or separate
but not as heading. Probably better to include a short
after About the role: "Job Type: Contract. Location: Cedar Rapids, IA (fully remote)." Also include Application Deadline maybe as metadata. But we must preserve ALL substantive information; do not invent or summarize away detail. So we need to include the job type, location, remote note, application deadline. We'll embed them in a
after About the role. Now Benefits: list includes many items. We'll create
- for each.
Pay: we can put
The pay range for this position is $45.00 - $45.00/hr.
underPay
. Now ensure we don't include boilerplate like EEO, equal opportunity, scam warning, cookie/navigation/legal, duplicated lines. The posting includes a lot of boilerplate about TEKsystems, equal opportunity, etc. We must remove those. Also remove "About TEKsystems" sections, "About TEKsystems And TEKsystems Global Services", etc. Also remove "San Francisco Fair Chance Ordinance", "Massachusetts Lie Detector", "Use of Artificial Intelligence (AI)". All that is boilerplate; we must remove. Thus final HTML fragment will contain sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Possibly also Qualifications? Not needed. We need to ensure we don't repeat the job title as a heading. The job title is Mainframe Systems Programmer/Engineer; we must not use that as heading. Now produce HTML. Let's craft:About the role
We are seeking an experienced Mainframe Systems Programmer/Engineer to support and maintain core mainframe infrastructure in a z/OS Sysplex environment. This role is responsible for the installation, testing, maintenance, documentation, monitoring, and support of mainframe software and components, as well as support for the BMC Control-D output management platform.
Job Type: Contract. Location: Cedar Rapids, IA (fully remote). Application Deadline: Oct 7, 2026.
Then Responsibilities:Responsibilities
- Provide primary support coverage during U.S. business hours (8:00 AM to 4:30 PM Central Time).
- Participate in an on-call rotation, including after-hours and weekend support.
- Perform daily monitoring and support of mainframe systems and software to ensure overall platform health and stability.
- Troubleshoot and resolve infrastructure and software issues through root cause analysis.
- Support and maintain the BMC Control-D output management environment, including report definitions, mission and decollation processes, and web-based access tools.
- Work with software vendors to troubleshoot issues, gather diagnostics, and implement fixes.
- Monitor key system metrics and proactively identify performance, stability, and optimization opportunities.
- Review system and software information regularly to identify potential defects, maintenance needs, and preventative actions.
- Respond to customer support requests and operational incidents.
- Participate in disaster recovery testing and related preparedness activities.
- Support infrastructure and business-driven projects.
- Install, configure, and maintain third-party mainframe software and software fixes.
- Design and adapt platform solutions to meet business and operational requirements.
- Continuously drive improvements in system availability, operational efficiency, and cost optimization.
Requirements
- Moderate knowledge of IBM z/OS and mainframe architecture.
- Experience supporting enterprise mainframe environments.
- Strong understanding of IT infrastructure concepts and system operations.
- Working knowledge of one or more programming languages such as Assembler, COBOL, REXX, or SAS.
- Experience with JCL, TSO/ISPF, and SDSF.
- Knowledge of BMC Control-D output management systems and related components.
- Experience following structured testing and implementation procedures.
- Understanding of disaster recovery concepts and processes.
- Strong troubleshooting, analytical, and problem-solving skills.
- Strong verbal and written communication skills.
- High attention to detail and commitment to quality.
- Ability to collaborate effectively with cross-functional teams and stakeholders.
Skills
- IBM z/OS Operating Systems
- IBM Mainframe Platforms
- Systems Engineering
- JCL Development and Administration
- BMC Control-D
- Sysplex Environments
- Mainframe Monitoring and Performance Analysis
Benefits
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)
Pay
The pay range for this position is $45.00 - $45.00/hr.
We should not include Schedule. Check for any leftover boilerplate: we removed all TEKsystems description, EEO, etc. Check for duplicate lines: none. Check for any content we missed: The "Workplace Type This is a fully remote position." we included in location note. Good. Check for "Job Type & Location This is a Contract position based out of Cedar Rapids, IA." we included. Check for "Application Deadline This position is anticipated to close on Oct 7, 2026." we included. Check for "Pay And Benefits The pay range for this position is $45.00 - $45.00/hr." we captured pay and benefits. Check for "Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following:" we captured list. Check for "Workplace Type This is a fully remote position." we captured. Check for "About TEKsystems" etc removed. Now ensure we didn't inadvertently