Sr. IT Program Manager

We need to output HTML fragment with sections: About Us? Actually the posting includes "About Us" but we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we need to map content to these headings. The posting includes "About Us" (company description) maybe not needed? The instruction says include a section ONLY when the posting has real, specific content for it. We have content for About Us (company description) but the allowed headings list does not include About Us; they list About the role. So we could treat "About Us" as "About the role"? Not exactly. The "About Us" is company overview, not role. Could we omit it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the company description somewhere. Perhaps we can put it under a

without a heading, or under a generic heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those for sections. Probably we should include a heading "About the role" and put the role description there, and maybe include company info under a

before that? The instruction: "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 have a

for company overview. Thus structure: maybe a

for About Us (company description). Then

About the role

with job summary? Actually "Job Summary" could be under About the role. Then

Responsibilities

with bullet list from Role Description. Then

Requirements

maybe combine Skill Level Requirements and Other Requirements? Or separate Qualifications and Skills. The instruction list includes Requirements, Qualifications, Skills. We need to decide where to put content. We have "Skill Level Requirements" with bullet points (Proficiency..., Experience..., Ability..., Ability...). Also "Other Requirements": Completed Bachelor’s Degree..., 7+ years experience..., Ability to travel..., Ability to travel 10%. Also "Behaviors and Competencies" list (Communication, Interpersonal Skills, Follow-Up, Collaboration, Problem-Solving, Time Management, Organization, Digital Acumen, Leadership). Those could be Skills. Thus we can map: - About the role: Job Summary (maybe also Role Description? Actually Role Description is more detailed responsibilities). But we can put Job Summary there. - Responsibilities: Role Description bullet list. - Qualifications: Education and experience (Bachelor's degree, 7+ years IT, 7+ years project/program manager, travel ability). Could also include Skill Level Requirements? But those are more like skills. - Skills: Skill Level Requirements (Proficiency..., Experience..., Ability..., Ability...) plus Behaviors and Competencies. - Benefits: Benefits may include medical, vision, dental, 401K, flexible spending. - Pay: The estimated annual pay range $130,000 - $180,000. - Schedule: Not provided, so we should NOT create Schedule section. Thus we will output sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. We need to use

• for any list of duties/requirements/benefits. For prose use

  . We must preserve all substantive information, not invent or summarize away detail. So we need to keep all bullet points exactly as given (maybe rephrase slightly? Must preserve meaning). We'll copy the bullet points. Let's extract: Job Summary: "The Sr. IT Program Manager will design, implement, and manage IT programs that support organizational goals, promoting best practices and acting as a change agent. This role involves leading initiatives for project delivery and process optimization, serving as the primary contact for project escalation, and developing communication strategies to align stakeholders. The manager will measure and analyze program processes for improvement, mentor team members, ensure integration with strategic initiatives, and collaborate with peer teams to incorporate best practices into Managed Services programs." That's prose. Role Description bullet list (looks like each line starts with a verb). We'll keep as list items. - Design, implement, and manage IT programs to support organizational goals across departments. - Promote the adoption of best practices and act as a change agent within the organization. - Lead initiatives related to IT project delivery, resource management, and process optimization. - Serve as the primary contact for project escalation, resolving complex project delivery issues. - Develop communication strategies to align stakeholders with program objectives and practices. - Measure and analyze program processes to identify and implement improvement solutions. - Mentor program team members, fostering continuous improvement and professional development. - Ensure integration with strategic initiatives like digital transformation and cybersecurity. - Implement and maintain a program improvement plan with performance metrics. - Collaborate with peer teams to incorporate best practices into Managed Services programs. Behaviors and Competencies list: each with description. - Communication: Can effectively communicate complex ideas and information to diverse audiences, facilitate effective communication between others, and mentor others in effective communication. - Interpersonal Skills: Can communicate effectively, build relationships, resolve conflicts, influence others, and support others in developing their interpersonal skills in major situations. - Follow-Up: Can take ownership of tasks, collaborate with others in managing follow-ups, and drive results through effective task completion. - Collaboration: Can take ownership of team initiatives, foster a collaborative environment, and ensure that all team members feel valued and heard. - Problem-Solving: Can proactively identify and take ownership of complex problem-solving initiatives, initiate preventative measures, collaborate with others to find solutions, and drive successful outcomes. - Time Management: Can manage time effectively, accurately estimate the time required for specific tasks, balance multiple tasks, and help others in improving their time management skills. - Organization: Can oversee complex projects with multiple moving parts, ensure team alignment with organizational systems, and adapt to changing priorities. - Digital Acumen: Can take ownership of complex digital initiatives, collaborate with others, and drive digital results. - Leadership: Can take ownership of complex team initiatives, collaborate with others in decision-making processes, and drive team performance. Skill Level Requirements list: - Proficiency in overseeing and coordinating multiple related projects, ensuring they align with organizational goals and deliver intended benefits on time and within budget - Expert - Experience in various project management frameworks such as Agile, Waterfall, and Scrum to effectively plan, execute, and close projects. - Expert - The ability to manage, drive, and adapt to organizational change while maintaining team morale and productivity. - Expert - Ability to simplify and effectively communicate complex problems to stakeholders across various functions and levels. - Expert Other Requirements: - Completed Bachelor’s Degree or relevant work experience required - 7+ years of experience in Information Technology - 7+ years of experience in a project or program manager role - Ability to travel to SHI, Partner, and Customer Events - Ability to travel 10% Benefits: "Benefits may include, but are not limited to, medical, vision, dental, 401K, and flexible spending." Pay: "The estimated annual pay range for this position is $130,000 - $180,000 which includes a base salary. The compensation for this position is dependent on job-related knowledge, skills, experience, and market location and, therefore, will vary from individual to individual." We need to keep that prose. Now produce HTML. We'll start with a

  for About Us company description? The instruction says we can fold minor metadata into a short

  or drop it. The About Us is not minor metadata; it's substantive. But we don't have a heading for About Us. Could we put it under a heading "About the role"? That would be mixing company overview with role summary, not ideal. Perhaps we can add a heading "About the company"? Not in list but maybe allowed? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those for sections. Safer to stick to those headings. We could treat the company description as part of "About the role" but that seems odd. However, we could include a

  before any heading for company overview, as it's not a heading. 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." It doesn't forbid other

  content. So we can have a

  for company overview. Thus output:

  About Us ...

  Then

  About the role

  with Job Summary

  . Then

  Responsibilities

  with
  list. Then

  Qualifications

  with
  list of Other Requirements (education, experience, travel). Then

  Skills

  with two
  maybe? Could combine Skill Level Requirements and Behaviors and Competencies into one list? But they are distinct categories. Could make two
  under same heading, or separate headings? The instruction says use

  for section headings; we can have multiple

  under same heading. We'll put both lists under Skills. Then

  Benefits

  with
  list (single items maybe just one
  • containing the sentence). Or we could keep as

    but instruction says use

    • for any list of duties/requirements/benefits. Benefits is a list, so we should use
      • . Even if it's one item, still okay. Then

        Pay

        with

        containing the pay range sentence. We must not include Schedule. Now ensure we preserve all info exactly. Let's copy text. Company description: "About Us Since 1989, SHI International Corp. has helped organizations change the world through technology. We’ve grown every year since, and today we’re proud to be a $16 billion global provider of IT solutions and services. Over 17,000 Organizations Worldwide Rely On SHI’s Concierge Approach To Help Them Solve What’s Next. But The Heartbeat Of SHI Is Our Employees – All 7,000 Of Them. If You Join Our Team, You’ll Enjoy Our commitment to diversity, as the largest minority- and woman-owned enterprise in the U.S.Continuous professional growth and leadership opportunities.Health, wellness, and financial benefits to offer peace of mind to you and your family.World-class facilities and the technology you need to thrive – in our offices or yours." Note there is missing punctuation and spaces; we should preserve as given. It's a bit messy but we keep. Job Summary: as above. Responsibilities list: as above. Qualifications list: Other Requirements items. Skills list: Skill Level Requirements and Behaviors and Competencies. Benefits list: "Benefits may include, but are not limited to, medical, vision, dental, 401K, and flexible spending." Pay: The estimated annual pay range for this position is $130,000 - $180,000 which includes a base salary. The compensation for this position is dependent on job-related knowledge, skills, experience, and market location and, therefore, will vary from individual to individual. Now produce HTML. Be careful to escape any HTML special characters? The text includes ampersand? Not really. It includes "U.S." with period; fine. We'll output: