Senior Systems Operations Engineer
or drop it. Probably we can include a short paragraph for Job Expectations? Actually Job Expectations is a heading we could use if content present. It has specific content: monitoring overall Mainframe/Midrange infrastructure, responding to alerts, resolving routine production, application and system problems according to operating instructions or with guidance to ensure data center service commitments are met. That's substantive. Also we have Visa sponsorship, relocation assistance note - maybe we can include as a short paragraph under a generic "Additional Information" but we are limited to headings list. We could put under "Job Expectations" the monitoring responsibility, and maybe add a note about visa/relocation as a short p after that section? 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 p for visa/relocation etc. Probably after the sections we can add a
with that info. We must not create Pay/Schedule/Benefits sections unless posting actually states them. No pay, schedule, benefits mentioned. So we omit those sections. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, maybe Job Expectations. But we must avoid duplication. The posting already has "About This Role", "In This Role, You Will" (responsibilities), "Required Qualifications", "Desired Qualifications", "Job Expectations". Also there are some skill statements within qualifications. We could map: - About the role: the initial paragraph. - Responsibilities: the bullet list from "In This Role, You Will". - Requirements: maybe combine Required Qualifications and Desired Qualifications? But we have separate headings for Requirements and Qualifications. The instruction says use headings like Requirements, Qualifications, Skills. We need to decide what goes where. Typically Requirements = mandatory qualifications, Qualifications = desired qualifications, Skills = specific technical skills. But we can also put Required Qualifications under Requirements, Desired Qualifications under Qualifications, and maybe extract skills like "Strong mainframe technical skills in z/OS, JES2, VTAM, CICS, IMS, DB2, HMC, console commands, and IPL", "Experience with Automation using Ansible/Python tools", etc. However we must not invent or summarize away detail; we must preserve all substantive information. So we need to include all content; we can duplicate across sections? Probably better to keep as given: Required Qualifications under Requirements, Desired Qualifications under Qualifications, and maybe Skills under Skills (like list of specific technical skills). But we risk duplication. However we can still include all info; duplication is okay as long as we preserve all info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not summarizing away; it's okay but maybe redundant. But we could avoid duplication by splitting: Required -> Requirements, Desired -> Qualifications, and then maybe Skills could be empty? But we must not emit a heading followed by filler/placeholder text. So we cannot create a Skills section if there's no specific content beyond what we already placed. So we should omit Skills section if we have no unique content. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Job Expectations (maybe). Also we could include a short p for visa/relocation and posting end date. Let's craft. About the role: combine the first paragraph(s). We'll put in
. Responsibilities:
- each bullet.
Requirements: Required Qualifications bullet list.
Qualifications: Desired Qualifications bullet list.
Job Expectations: the paragraph about monitoring overall Mainframe/Midrange infrastructure etc.
After that, a short
for visa/relocation, posting end date, note about Ansible/Python highly preferred. We must not include boilerplate like EEO, etc. Let's extract bullet points precisely. From "In This Role, You Will": 1. Constantly monitor Mainframe MVS operation system LPARs activity via console messages, logs and network management system and report system abnormalities and issues are resolved or escalated properly and/or out of balances to management immediately 2. Develops and reviews Knowledge Management documentation for accuracy, may participate in training peers on all operational functions with the direction of supervision 3. Work as key participant in large scale planning of computer systems and network infrastructure for Systems Operations functional area 4. Contribute to increasing system efficiencies and lowering the human intervention time on related tasks 5. Review and analyze moderately complex operational support systems, application software, and system management tools to ensure the highest levels of systems and infrastructure availability 6. Build Automation Strategy from functional to Automation using Python and Ansible or any automation 7. Consult with engineering team on change design requiring solid understanding of technical process controls or standards that influence and drive new initiatives 8. Collaborate with vendors and other technical personnel to resolve technical issues and achieve highest levels of systems and infrastructure availability. We'll keep as is. Required Qualifications bullet list: - 4+ years of Systems Engineering, Technology Architecture experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education - 4+ years of experience with Automation using Ansible/Python tools or other Java expertise - Deep understanding of SRE principles and practices - Experience with enterprise monitoring and observability platforms (e.g., Splunk, Prometheus, Grafana) and Strong expertise in BigPanda/ServiceNow - Strong mainframe technical skills in z/OS, JES2, VTAM, CICS, IMS, DB2, HMC, console commands, and IPL - Strong technical expertise, communication, and stakeholder engagement skills. Desired Qualifications bullet list: - Experience in Mainframe console operations - Experience in mainframe console operations and enterprise production support - Proficient in incident tracking and ITSM tools such as ServiceNow for incident, problem, change, and availability management - Monitor Mainframe/Midrange environments, respond to alerts, and resolve routine production, application, and system issues to meet service commitments - Apply best practices in Mainframe Operations, process development, and quality management - Execute scripts and update operational procedures/documentation for application processing and backup activities - Provide operational support and management for enterprise systems and infrastructure within the Systems Operations environment - Drive operational efficiency by reducing manual effort through process improvement and automation - Review and analyze operational support systems, applications, and system management tools to maintain high availability - Understand business cycles and assess the impact of technology events on business operations and support teams - Work closely with vendors, technical teams, and management to troubleshoot issues and restore services quickly - Support team deliverables while ensuring compliance with established technical standards, operational controls, and procedures - Provide guidance, mentoring, and day-to-day support to team members - Hands-on knowledge of JCL, system utilities, operating systems, tape processing, scheduling tools, and incident/change management principles - Strong analytical and troubleshooting skills across system, network, application, and hardware support - Self-motivated, able to multitask, and effective under pressure in a high-performance, geographically distributed team environment. Job Expectations: "Responsible for monitoring the overall Mainframe/Midrange infrastructure, responding to alert messages and resolving routine production, application and system problems according to operating instructions or with guidance to ensure that the data center service commitments