IT Program Supervisor

We need to output HTML fragment with sections: About the role? Actually the posting includes Company Information, Division Information, Requisition Summary, Job Responsibilities, Required Skills, Physical Requirements, Education Required, Preferred, Competencies, PACCAR Benefits, Additional Job Board Information (which includes EEO etc). We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Additional Job Board Information" if it's just EEO etc. The "PACCAR Benefits" section is present with details; we should keep that as Benefits section. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content to these headings appropriately. The instructions: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings when we have content. We should include a section only when posting has real, specific content for it. So we need to decide which sections we have content for. We have: - About the role: could be the Requisition Summary (description). That's a summary of role. So we can put that under

About the role

with a

. - Responsibilities: Job Responsibilities section. - Requirements: Could be Required Skills? Or Education Required? The instructions list Requirements and Qualifications separate. We need to decide. Usually Requirements = required skills/experience; Qualifications = education/experience. But we can map. We have Required Skills (list), Physical Requirements (list), Education Required (list), Preferred (list), Competencies (list). Also we have Company Information and Division Information maybe not needed? Could be part of About the role? Might be considered background but not required. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep company/division info? It's substantive but maybe not required for job posting? It's about the company. Could be placed under About the role? But About the role is supposed to be about the role, not company. However we could include a brief paragraph about company/division as part of About the role? The instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include company info as a paragraph maybe under About the role? But About the role heading expects role description. Might be better to create a section like "About the company" but not in allowed headings list. The allowed headings list is examples; we could still use other headings? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings; but we could also use other headings if needed? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings; we should stick to them. So we need to map all content into those categories. Thus we need to decide what goes where: - About the role: could include a brief summary of the role (Requisition Summary) plus maybe company/division info as context. - Responsibilities: Job Responsibilities. - Requirements: Required Skills? Or maybe Required Skills + Physical Requirements? But Physical Requirements is more about ability to perform job; could be under Requirements. - Qualifications: Education Required + Preferred? Or Education Required as Qualifications, Preferred as maybe also Qualifications. - Skills: Could be Required Skills (but we already used). Hmm. We have overlapping categories. Perhaps we should treat: - About the role: Requisition Summary (role description). - Responsibilities: Job Responsibilities. - Requirements: Required Skills (list) + Physical Requirements (list) maybe combined. - Qualifications: Education Required (list) + Preferred (list) (maybe as separate subpoints). - Skills: Could be Required Skills again? That seems duplicate. Maybe we should put Required Skills under Skills, and Requirements under Requirements (like years of experience, supervisory experience). Let's parse the content: Under "Required Skills" heading there are bullet points: Leadership & Team Development, Program & Project Management, Enterprise Application Development, Business Relationship Management, Communication & Presentation Skills, Continuous Improvement, Financial & Resource Management, Technical Skills. That's a list of skill categories. Under "Physical Requirements" separate list. Under "Education Required" heading: Bachelor's Degree ... Minimum of seven (7) years ... Minimum of two (2) years supervisory ... Experience with enterprise business applications... Under "Preferred": Master's Degree, PMP certification, Agile/Scrum certification, Experience supporting SAP... Under "Competencies": list of competencies (like Act with Integrity, etc.) Thus we can map: - About the role: Requisition Summary (role description) plus maybe company/division info as context. - Responsibilities: Job Responsibilities. - Requirements: Required Skills (list) + Physical Requirements (list) maybe as separate sub-sections? But we need to use

• for any list. - Qualifications: Education Required (list) + Preferred (list) maybe. - Skills: Could be Competencies? Or maybe we treat Required Skills as Skills, and Requirements as something else like "Experience". But the instruction list includes Skills as a heading. So we should have a Skills section. Thus we need to decide distribution: Option: - About the role: Requisition Summary (role description) + Company/Division info (maybe as a short paragraph). - Responsibilities: Job Responsibilities. - Requirements: Education Required + Preferred (i.e., qualifications). But we already have Qualifications heading. - Qualifications: Required Skills? Hmm. Let's look at typical job posting: About the role (summary), Responsibilities (duties), Requirements (minimum qualifications), Qualifications (preferred qualifications), Skills (maybe technical skills), Benefits, Pay, Schedule. Thus we can map: - About the role: Requisition Summary (role description) + maybe company/division info as brief context. - Responsibilities: Job Responsibilities. - Requirements: Education Required (Bachelor's + 7 years + 2 years supervisory) maybe also Physical Requirements? Physical requirements could be under Requirements as well. - Qualifications: Preferred (Master's, PMP, Agile, SAP experience) maybe also Required Skills list? But Required Skills is more like skill categories; could be under Skills. - Skills: Required Skills list (leadership, program management, etc.) plus Technical Skills sublist. - Benefits: PACCAR Benefits. - Pay: Not provided, so we should NOT include Pay section. - Schedule: Not provided (only mentions on-site, not remote). No schedule details, so we should NOT include Schedule. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We must not include empty sections. Now we need to format content. We need to preserve all substantive information, not invent or summarize away detail. So we need to keep the bullet points exactly as given, but we can rephrase? We should not invent or summarize away detail; we can keep them as list items. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Additional Job Board Information" includes EEO etc; we should drop that entirely. Also "PACCAR is an Equal Opportunity Employer..." etc. Remove. Also remove "Additional Job Board Information" heading and its content. We must not include "Job ID / requisition numbers". There's none visible. Now we need to produce HTML fragment: only the HTML, no /, no markdown fences. We'll produce something like:

  About the role

  Company Information PACCAR is a Fortune 500 company established in 1905. PACCAR Inc is recognized as a global leader in the commercial vehicle, financial, and customer service fields with internationally recognized brands such as Kenworth, Peterbilt, and DAF trucks. PACCAR is a global technology leader in the design, manufacture and customer support of premium light-, medium- and heavy-duty trucks under the Kenworth, Peterbilt and DAF nameplates and also provides customized financial services, information technology and truck parts related to its principal business. Whether you want to design the transportation technology of tomorrow, support the staff functions of a dynamic, international leader, or build our excellent products and services, you can develop the career you desire with PACCAR. Get started! Division Information Dynacraft, a PACCAR Company, is headquartered in McKinney, TX. Dynacraft is a diversified global manufacturer of PACCAR medium and heavy-duty truck parts sold under the Kenworth, Peterbilt, and DAF nameplates. For more than forty years, Dynacraft has provided the company’s truck manufacturing divisions and PACCAR Parts service parts division with high quality components, subassemblies and specialized services. Dynacraft’s manufacturing facilities are located in Louisville, KY, and McKinney, TX.

  The IT Program Supervisor is responsible for supervising the planning, execution, support, and continuous improvement of Dynacraft's information technology programs, enterprise applications, and technology initiatives. This role provides leadership to application developers, analysts, and technical staff while ensuring technology solutions align with business objectives and operational requirements. The position oversees multiple IT projects, application development activities, system enhancements, technology support initiatives, and cross-functional technology programs. The IT Program Supervisor works closely with business leaders, PACCAR IT teams, vendors, and stakeholders to deliver reliable, scalable, and secure technology solutions. The successful candidate will promote operational excellence, innovation, continuous improvement, and employee development while supporting Dynacraft's strategic business goals. This position is not a remote opportunity. This will be an on-site role.

  But we need to avoid duplication: The company info appears twice? Actually we have Company Information and Division Information paragraphs; we can combine them into a single

  maybe. We'll keep all info. Now Responsibilities: we need to list each responsibility as

  • . The responsibilities are grouped under headings: Leadership & Team Development, Program & Project Management, Enterprise Applications & Technical Oversight, Business Partnership & Stakeholder Management, Operational Excellence & Continuous Improvement, Strategic Initiatives. Each has multiple bullet points (some are sentences). We need to preserve all detail. We'll create a
    with each bullet as
    • . We'll need to split the sentences appropriately. Let's extract responsibilities: Leadership & Team Development: - Lead, coach, and develop technical teams including application developers, analysts, and support personnel. - Establish clear performance expectations, goals, and accountability measures. - Foster a collaborative, innovative, and customer-focused work environment. - Facilitate team development initiatives and promote continuous learning and technical growth. - Support workforce planning, succession planning, and employee development activities. Program & Project Management: - Supervise multiple technology programs, projects, and application initiatives. - Prioritize project workloads, resources, and timelines to meet business requirements. - Manage project portfolios supporting operational improvements, new products, and business initiatives. - Monitor project performance and communicate status, risks, and mitigation plans to leadership. - Establish and report on key performance indicators (KPIs) related to program performance and service delivery. Enterprise Applications & Technical Oversight: - Oversee development, implementation, testing, and support of enterprise business applications. - Support application environments utilizing Microsoft .NET, SQL Server, SAP, and related technologies. - Ensure compliance with IT governance, cybersecurity, architecture, and development standards. - Promote Agile development practices and continuous improvement methodologies. - Support issue resolution, system enhancements, and technology modernization initiatives. Business Partnership & Stakeholder Management: - Build and maintain strong relationships with business stakeholders, suppliers, vendors, and PACCAR technology