Manager, Engineering, Managed Services - Mainframe

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job posting. First, there is a description of role: "The Managed Services Engineering Manager demonstrates focus..." That's about the role. Could be "About the role". Then there is "What You Will Do" which enumerates duties: Customer Satisfaction, Leadership and Management, Process Management, Communication, Financial. That's responsibilities. Then "What We Expect Of You" lists qualifications: Bachelor's degree and 5 years experience OR 9 years related consulting or IT services delivery experience; previous consulting leadership experience required; process management and improvement; experience in ITIL; experience managing mainframe environments; understanding of mainframe capacity planning; ability to lead teams; ability to communicate; ability to balance multiple priorities; proven ability to proactively collaborate; proven negotiation skills; knowledge of IBM, Cisco, Microsoft, HP, or Dell products; experience working with vendors; ability to lead and manage to ensure attainment of critical results; ability to compute, analyze and interpret complex statistical data; ability to act as a trusted advisor; able and willing to travel up to 25%; ability to multi-task, organize and prioritize; experience managing IBM z/OS, z/VM, ISV, RACF, is a plus; ability to multi-task, organize and prioritize (duplicate). Also "Ability to travel as needed" (duplicate). So we can put these under Requirements or Qualifications. The instruction says we can have sections like Requirements, Qualifications, Skills. We need to decide which to use. Probably combine qualifications and skills. But we need to avoid thin sections. We could have one "Requirements" section that includes education/experience and skills. Or separate "Qualifications" for education/experience and "Skills" for abilities. However we must only include sections when posting has real specific content. It does have both. We also have Pay range: $126,500 - $177,100 depending on experience and skill set; Annual bonus target of 20% subject to terms and conditions of plan. Benefits overview: link. Salary ranges may be subject to geographic differentials. So we have Pay and Benefits sections. Schedule: Not mentioned explicitly. There's travel up to 25% but not schedule. So we should not create Schedule section. We also have "About Us" and "CDW is an equal opportunity employer" etc which are boilerplate to remove. Also "As a leader, you will champion..." about AI-fluent organization. That's not boilerplate? It's part of the posting but maybe considered fluff but it's substantive? It's about expectations. Could be part of "What We Expect Of You" or "About the role". It mentions AI-fluent organization, champion vision, model curiosity, encourage responsible AI adoption, foster culture of continuous learning, guide others in building confidence with AI tools, etc. That's substantive. Should we include? It's not under a heading but appears after "Pay range:" etc. It's part of the posting. We should preserve all substantive information. So we need to incorporate that content somewhere, maybe under "About the role" or "What We Expect Of You". Since it's about leadership expectations, could be part of "What We Expect Of You". We'll incorporate as a paragraph. We also have "About Us" describing CDW. That's boilerplate? It's generic company description; could be considered boilerplate but it's substantive about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" is not explicitly listed as boilerplate to remove, but it's generic marketing. Might be considered boilerplate? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It does not say to remove "About Us". However earlier they said "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep About Us if it's substantive. But it's generic fluff; still it's part of posting. I'd keep it maybe under a section "About the company"? But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About Us". So we cannot add a heading not in list. We could fold About Us content into "About the role" maybe? But that seems odd. Better to omit About Us because it's not required heading and we cannot create arbitrary headings. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we must only use those headings. So we cannot add a heading like "About Us". Therefore we should not include that content unless we can fold it into one of the allowed headings. Could we put it under "About the role"? That section is about the role, not company. But maybe we can incorporate company description into "About the role" as context. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid adding extra content under About the role beyond role description. So we could put the About Us paragraph under About the role as a brief description of the company. That might be acceptable. Similarly, the EEO statement is boilerplate to remove. So we drop that. Also the duplicated lines: "Ability to multi-task, organize and prioritize." appears twice; we should deduplicate. Now we need to output HTML fragment only, no /, no markdown fences. We'll structure:

About the role

... (role description + maybe About Us)

Responsibilities

• ... each duty

We need to break down responsibilities from "What You Will Do". It has headings: Customer Satisfaction, Leadership and Management, Process Management, Communication, Financial. We can make each as

items, maybe with sub-bullets? But we only need

• for any list. We can embed the headings inside li text. We'll produce list items: - Customer Satisfaction: Understand customer environments and business needs. Meet periodically with customers through sales opportunities, quarterly reviews, and especially during support issues. Track, monitor and report Customer Satisfaction Performance Measures, including Customer Satisfaction Surveys. - Leadership and Management: Managing workload; prioritizing and assigning resources. Includes review Service Desk queues and related reports. Serve as a primary point of contact for the collaboration of strategic and tactical plans for the current and future development of the technologies assigned to their specific technology. Time reporting and related analysis. Hiring staff. Building and motivating effective teams. Delegating responsibilities to appropriate team members. Performance management: Consistent feedback, both positive and negative. Assessment, both subjective and objective coaching/mentoring. Individual Development Planning (career path, improvement opportunities, training). Maintaining the On-call schedule. Work closely with peers to achieve company, department and personal goals. Willing to take calculated risks to meet customer needs and department goals. - Process Management: Oversee the development, maintenance, and performance of the problem, change and work order processes. Deliver Operational Framework and Standard Operating Procedures to staff and ensure adherence through Quality Assurance process. Review Operational Framework and Standard Operating Procedures on an on-going basis to identify process and organizational structure gaps. Continuous Service Improvement utilizing key metrics. - Communication: Regular staff interaction, both written and face-to-face. Customer interaction, both written and face-to-face. Work collaboratively with other groups and managers to successfully manage customer expectations and environments. - Financial: Manage operational costs, plan, and budget. Now "What We Expect Of You" includes education/experience and skills. We'll split maybe into Requirements (education/experience) and Skills (abilities). But we have also Qualifications section allowed. Let's decide: Use "Requirements" for education/experience, "Skills" for abilities. Or combine into "Qualifications". The instruction says we can use those headings; we need to avoid thin sections. If we split, each will have substantive content. That's fine. Thus:

  Requirements

  • Bachelor’s Degree and 5 years of relevant experience OR 9 years of related consulting or IT services delivery experience
  • Previous consulting leadership experience required
  • Process management and improvement experience
  • Experience in ITIL
  • Experience managing mainframe environments, including IBM CICS, DB2, MQ, IDMS and related tools
  • Understanding of mainframe capacity planning, performance tuning, and workload automation

  Skills

  • Ability to lead teams; gain consensus
  • Ability to communicate effectively and concisely both orally and written using a variety of styles and techniques appropriate to the audience
  • Ability to balance multiple priorities simultaneously and adapt to the changing needs of the business while meeting deadlines
  • Proven ability to proactively collaborate and build relationships, take initiative, and creatively problem solve
  • Ability to identify and creatively resolve client, project and people issues
  • Proven negotiation skills
  • Knowledge of IBM, Cisco, Microsoft, HP, or Dell products and services
  • Experience working with vendors and business partners
  • Ability to lead and manage to ensure attainment of critical results
  • Ability to compute, analyze and interpret complex statistical data for reporting purposes and/or to develop forecasts
  • Ability to act as a trusted advisor in a strategic partnership
  • Able and willing to travel up to 25% or as needed to other CDW locations, meetings or client sites
  • Ability to multi-task, organize and prioritize
  • Experience managing IBM z/OS, z/VM, ISV, RACF, is a plus
  Note: deduplicate "Ability to multi-task, organize and prioritize." only once. Now Pay and Benefits:

  Pay

  Pay range: $126,500 - $177,100 depending on experience and skill set. Annual bonus target of 20% subject to terms and conditions of plan. Salary ranges may be subject to geographic differentials.

  Benefits

  Benefits overview: https://cdw.benefit-info.com/

  We should not include the AI-fluent organization content? It's under "As a leader, you will champion..." after Pay range. That's substantive about expectations. Could incorporate into Skills or Requirements? It's about leadership expectations regarding AI. Could add a bullet under Skills: "Ability to champion and be accountable for vision of becoming an AI-fluent organization; model curiosity, encourage responsible AI adoption, foster a culture of continuous learning; guide others in building confidence and capability with AI tools and practices; promote openness to experimentation and shared learning." That seems appropriate. Also there is a paragraph about "We expect leaders to model curiosity..." etc. We'll incorporate as a skill. Also there is a paragraph about "Additionally, CDW is committed to fostering an equitable, transparent, and respectful hiring process..." That's EEO boilerplate, remove. Also "As an AI forward company..." etc. That's also fluff but maybe part of expectations. We'll incorporate some. We need to ensure we don't include duplicated lines. Now About the role section: we need to include the initial description: "The Managed Services Engineering Manager demonstrates focus in leading