Mainframe Software Engineering Manager

We need to output HTML fragment with sections only when there is real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also remove "Company Vehicle" maybe? It's a benefit? It's a specific benefit: company vehicle evaluation program. Should we include under Benefits? The posting mentions "Company Vehicle: Upon successful completion...". That is a benefit. Also "This job may be eligible for relocation benefits." That's also a benefit. Also "Benefits Overview" generic but no specifics. We should include specific benefits: company vehicle program, relocation benefits eligibility. Also maybe "Benefits Overview" is generic; we can include a short paragraph summarizing that GM offers benefits, but we should not invent details. The instruction: Prefer a few substantive sections over many thin ones. So we can combine some. We need sections: About the role (description of role, what Mainframe Factory does, what the role will do). Responsibilities (list of duties). Requirements (maybe required qualifications). Qualifications (maybe preferred qualifications). Skills (maybe skills & abilities). Benefits (company vehicle, relocation). Pay and Schedule only if present. Pay not mentioned. Schedule: hybrid work arrangement: expected to report to Warren, MI or Austin, TX three times per week at minimum or other frequency dictated by business. Also selected candidate will be required to travel

for any list of duties/requirements/benefits. Use

for prose. We must not repeat job title. No markdown. Let's extract content. About the role: The Mainframe Factory supports... It directly provides... The Mainframe Software Engineering Manager will lead a team... It will help establish... Additionally, this role combines day-to-day people leadership with hands-on technical guidance... You will work closely... supporting GM’s vision of Zero Crashes, Zero Emissions, and Zero Congestion. We can put that as prose under About the role. Responsibilities: The "What You’ll Do" bullet list. Each bullet is a duty. We'll make

• . Required Qualifications: "Your Skills & Abilities (Required Qualifications)" list. We'll treat as Requirements. Preferred Qualifications: "What Will Give You a Competitive Edge (Preferred Qualifications)" list. We'll treat as Qualifications. Skills & Abilities maybe overlapping with required qualifications; but we already used that as Requirements. Could also have Skills section for things like "Strong written and verbal communication skills..." but that's already in required qualifications. We could combine. But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can put Skills as maybe a short paragraph summarizing key skills not covered elsewhere? But we already have required qualifications includes many skills. Could still have Skills section for things like "Strong written and verbal communication skills..." but that's duplicate. Perhaps we can omit Skills if no distinct content beyond what's already in Requirements. However instruction: include a section ONLY when the posting has real, specific content for it. If we put Skills but it's just repeating, maybe still specific content? Might be considered duplicate. Safer to omit Skills if not distinct. Benefits: company vehicle program, relocation benefits eligibility. Also maybe "Benefits Overview" generic but we can include a short paragraph that GM offers benefits, but that's generic. Better to list specific benefits. Schedule: hybrid work arrangement (report to Warren, MI or Austin, TX three times per week minimum) and travel About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Benefits

• ...
...

Schedule

...

Make sure to preserve all substantive info. Let's extract details. About the role prose: "The Mainframe Factory supports a broad portfolio of GM business functions such as Global Purchasing and Supply Chain, Manufacturing, Dealer and Channel Operations, and Global Finance. It directly provides and develops innovative solutions for business value streams including Design to Launch, Source to Deliver, Make to Ship, Vehicle Order to Deliver, Use to Service, Record to Report, and Brazil business operations. The Mainframe Software Engineering Manager will lead a team of engineers responsible for the design, build, and ongoing evolution of GM’s core mainframe applications that power GM’s global business operations. It will help establish consistent engineering practices across these value streams while enabling each product team to deliver secure, reliable, and modernized mainframe solutions aligned to its business needs. Additionally, this role combines day-to-day people leadership with hands-on technical guidance: you will be accountable for driving engineering excellence, delivering high quality solutions, and for moving our mainframe ecosystem toward a modern, automated, and AI-enabled software factory. You will work closely with business partners, architects, and platform teams to ensure that our mainframe applications are stable today and ready for the future, supporting GM’s vision of Zero Crashes, Zero Emissions, and Zero Congestion." That's the about. Responsibilities list from "What You’ll Do": - Lead, mentor, and grow a team of mainframe software engineers, creating a culture of inclusion, accountability, and continuous improvement. - Own end-to-end delivery for a portfolio of mainframe applications across the Design to Launch, Source to Deliver, Make to Ship, Vehicle Order to Deliver, Use to Service, and Record to Report value streams. - Translate business priorities into a clear engineering roadmap and a well-maintained backlog, balancing new features, technical debt, and modernization work. - Provide technical direction on mainframe design patterns, data models, performance tuning, and integration with surrounding systems. - Drive consistent adoption of modern engineering practices on the mainframe, including: - Git-based workflows (GitHub), branching and code review standards - CI/CD automation (e.g., GitHub Actions) for build, test, and deploy - Test automation and repeatable validation of changes - Champion the thoughtful use of AI in the engineering lifecycle (e.g., code assist, test generation, defect analysis) to automate workflows and improve quality and speed. - Partner with platform, SRE, and security teams to ensure availability, observability, compliance, and operational excellence for production systems. - Use metrics (lead time, deployment frequency, change-failure rate, escaped defects, availability) to guide decisions and continuously improve how the team works. - Represent the team in forums with product, business, and leadership stakeholders, clearly communicating status, risks, and trade-offs. Note the sub-bullets under "Drive consistent adoption...". We could flatten them into separate

items or keep as sublist? The instruction: use

• for any list of duties/requirements/benefits. Could nest but better to keep flat list; we can break sub-items into separate
• . We'll keep them as separate items. Thus responsibilities items: 1. Lead, mentor, and grow a team of mainframe software engineers, creating a culture of inclusion, accountability, and continuous improvement. 2. Own end-to-end delivery for a portfolio of mainframe applications across the Design to Launch, Source to Deliver, Make to Ship, Vehicle Order to Deliver, Use to Service, and Record to Report value streams. 3. Translate business priorities into a clear engineering roadmap and a well-maintained backlog, balancing new features, technical debt, and modernization work. 4. Provide technical direction on mainframe design patterns, data models, performance tuning, and integration with surrounding systems. 5. Drive consistent adoption of modern engineering practices on the mainframe, including: - Git-based workflows (GitHub), branching and code review standards - CI/CD automation (e.g., GitHub Actions) for build, test, and deploy - Test automation and repeatable validation of changes - Champion the thoughtful use of AI in the engineering lifecycle (e.g., code assist, test generation, defect analysis) to automate workflows and improve quality and speed. But we need to flatten: maybe separate items for each subpoint. Let's create separate items: - Drive consistent adoption of modern engineering practices on the mainframe, including Git-based workflows (GitHub), branching and code review standards. - Drive consistent adoption of modern engineering practices on the mainframe, including CI/CD automation (e.g., GitHub Actions) for build, test, and deploy. - Drive consistent adoption of modern engineering practices on the mainframe, including test automation and repeatable validation of changes. - Drive consistent adoption of modern engineering practices on the mainframe, including championing the thoughtful use of AI in the engineering lifecycle (e.g., code assist, test generation, defect analysis) to automate workflows and improve quality and speed. But that repeats phrase. Could combine: "Drive consistent adoption of modern engineering practices on the mainframe, including Git-based workflows (GitHub), branching and code review standards; CI/CD automation (e.g., GitHub Actions) for build, test, and deploy; test automation and repeatable validation of changes; and championing the thoughtful use of AI in the engineering lifecycle (e.g., code assist, test generation, defect analysis) to automate workflows and improve quality and speed." That's one item. We'll keep as one item with semicolons. - Partner with platform, SRE, and security teams to ensure availability, observability, compliance, and operational excellence for production systems. - Use metrics (lead time, deployment frequency, change-failure rate, escaped defects, availability) to guide decisions and continuously improve how the team works. - Represent the team in forums with product, business, and leadership stakeholders, clearly communicating status, risks, and trade-offs. Now Requirements list from "Your Skills & Abilities (Required Qualifications)": - 10+ years of experience delivering and supporting mainframe solutions in a large enterprise environment. - Strong technical background with mainframe technologies such as PL/I and/or COBOL, JCL, IMS (TM/DB), Db2 (or similar), and Scheduling solutions such as IWS and CA7. - Demonstrated people leadership experience as a software engineering manager (2+ years) and/or technical lead (7+ years), including coaching, performance management, and team building. - Proven track record leading cross-functional delivery efforts with multiple stakeholders (business, architecture, operations, vendors). - Hands-on experience with modern software engineering practices: Agile delivery (Scrum or Kanban), incremental releases, code review, and automated testing. - Practical experience with Git-based source control (preferably GitHub) and CI/CD tooling (e.g., GitHub Actions, Azure DevOps, or similar). - Ability to operate in a hybrid environment where mainframe, distributed, and cloud applications must work together. - Strong written and verbal communication skills with the ability to influence and align diverse stakeholders. - Bachelor’s degree in Computer Science, Engineering, Mathematics, or related field, or equivalent work experience. Now Qualifications list from "What Will Give You a Competitive Edge (Preferred Qualifications)": - Ability to develop, inspire, and motivate team. - Fosters collaboration and teamwork - Direct experience leading mainframe modernization programs (API enablement, refactoring, re-platforming, or decomposing legacy systems) in hybrid environment. - Experience with test automation frameworks and practices in mainframe and/or distributed environments. - Experience applying AI/ML or GenAI tools within software engineering workflows in a secure, compliant way. - Background in automotive industry including supply chain, manufacturing, logistics, finance, or aftersales systems