(USA) Principal, Technical Program Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes Position Summary, What you'll do, About the Team, What You'll Do (duplicate?), What You'll Bring, Minimum Qualifications, Preferred Qualifications, Benefits, Pay (salary range), maybe Schedule not present. We must not repeat job title heading. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also remove repeated sections like "Minimum Qualifications..." repeated twice. Also remove "Primary Location..." maybe location is substantive? It's location info; we can include as a paragraph maybe under a heading? There's no heading for location; but we could include as a

  after some section. The instruction: include a section ONLY when posting has real, specific content for it. So we can have sections: About the Team, What You'll Do, What You'll Bring, Minimum Qualifications, Preferred Qualifications, Benefits, Pay. Possibly also About the role? There's Position Summary at start; we could treat that as a summary paragraph before sections. Not required to have heading. We must not create Pay/Schedule/Benefits unless posting actually states them. Pay is stated: salary range $110,000 - $220,000 plus bonuses. Benefits are described. So include Benefits and Pay sections. Schedule not present, so omit. We need to remove duplicated lines like "Minimum Qualifications... Outlined below are the required minimum qualifications for this position." appears twice; we keep one. Also remove "If none are listed, there are no minimum qualifications." etc. Also remove "Preferred Qualifications... Outlined below are the optional preferred qualifications for this position." etc. Also remove "Live Better U..." etc but that's part of benefits; we keep benefits details. We must not include application instructions, like "For information about PTO, see https://..." maybe that's part of benefits; we can keep as part of benefits paragraph. We need to format lists: duties, requirements, benefits as

  • . For prose use

    . We need to decide what constitutes a list. The "What You'll Do" section has many bullet-like sentences but not explicitly bulleted. We could turn each sentence into

  • under a
    . Similarly "What You'll Bring" could be list. Minimum Qualifications could be list (two options). Preferred Qualifications list. Benefits list. We need to avoid creating headings with filler text. Ensure each heading has substantive content. Let's extract content. Position Summary paragraph: "The Principal, Technical Program Manager leads complex, large-scale technology and security programs that span multiple teams, platforms, and organizational boundaries. This role is responsible for defining program strategy, establishing goals and success measures, managing cross-functional dependencies, and driving end-to-end execution of high-impact initiatives. The Principal Technical Program Manager will partner closely with Engineering, Product, Security, Infrastructure, Architecture, Cloud, Risk, Compliance, and Business teams to translate strategic objectives into executable roadmaps and measurable outcomes. This role requires strong technical acumen, program and risk management expertise, executive-level communication, and the ability to influence decisions across organizations without direct authority. The successful candidate will operate effectively in ambiguous and highly complex environments, proactively identify and mitigate risks, drive technical and operational decisions, establish scalable governance frameworks, and continuously improve program execution. This role will also contribute to developing talent and raising the standard of technical program management across the organization." We can keep that as a

    maybe under no heading or under a heading like "Position Summary"? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't forbid other headings? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings. But we can also have other headings? Safer to stick to those headings. However we have content like About the Team, What You'll Do, What You'll Bring, Minimum Qualifications, Preferred Qualifications, Benefits, Pay. Those map to: About the role (maybe About the Team?), Responsibilities (What You'll Do), Requirements (What You'll Bring?), Qualifications (Minimum/Preferred), Skills (maybe part of What You'll Bring), Benefits, Pay. We could map: - About the role: could be Position Summary + About the Team? Or we could have About the Team as separate heading? The instruction list includes About the role as example. We'll use About the role for the Position Summary paragraph. - Responsibilities: What You'll Do. - Requirements: What You'll Bring (skills/experience). - Qualifications: Minimum Qualifications and Preferred Qualifications maybe separate? Could combine under Qualifications with subheadings? But we only allowed

    for section headings; we could have multiple

    sections: Minimum Qualifications, Preferred Qualifications. - Benefits: Benefits. - Pay: Pay. - Schedule: not present. We also have About the Team content; could be part of About the role or separate section like About the Team (not in list). Might be okay to add About the Team as a 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 says use

    for section headings (e.g. ...). Likely they expect only those headings. Safer to incorporate About the Team into About the role or Responsibilities? Probably About the role includes summary and team description. Thus we will have sections:

    About the role

    with paragraph combining Position Summary and About the Team.

    Responsibilities

    with
    • items from What You'll Do.

      Requirements

      with
      • items from What You'll Bring.

        Minimum Qualifications

        with
        • items (two options).

          Preferred Qualifications

          with
          • items.

            Benefits

            with
            • items (health, financial, PTO, etc).

              Pay

              with

              containing salary range and bonus info. We must not repeat job title heading. We must remove duplicated lines like "Minimum Qualifications... Outlined below are the required minimum qualifications for this position." We'll keep just the list. We need to ensure we don't include boilerplate like "Live Better U is a Walmart-paid education benefit program..." that's part of benefits; we keep. We must remove "For Information About Benefits And Eligibility, See One.Walmart." maybe keep as part of benefits? It's a reference; could keep as a sentence. We must remove "Primary Location..." maybe we could include as a paragraph under About the role? Not required but location is substantive. Could add a

              after About the role? But we have no heading for location; maybe we can include as a

              under About the role. However the instruction says include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid adding a paragraph without heading. So we can add a

              for location after About the role before Responsibilities. But we need to ensure we don't include duplicated lines like "Primary Location... 805 Se Moberly Ln., Bentonville, AR 72712, United States of America". That's fine. Also remove "Walmart and its subsidiaries are committed to maintaining a drug-free workplace..." that's boilerplate legal; remove. Now craft content. Let's extract responsibilities sentences from "What You'll Do". The text repeats some content from earlier but we need to capture all unique duties. What You'll Do paragraph: "Lead complex, enterprise-scale technical and security programs involving multiple engineering organizations, technology platforms, and cross-functional dependencies. Define program strategy, objectives, scope, stage gates, critical paths, milestones, success metrics, and key deliverables. Build and maintain multi-year program roadmaps aligned with security strategy, technology priorities, and business objectives. Secure commitments for scope, timelines, resources, and technical deliverables while proactively managing dependencies and competing priorities. Partner with Engineering and Architecture leaders to evaluate technical solutions, system architecture, scalability, security, reliability, and operational readiness. Drive security and technology transformation initiatives across cloud, infrastructure, platforms, risk management, resilience, and related enterprise capabilities. Identify program, technical, operational, and organizational risks; develop mitigation strategies; and drive issues to resolution. Establish governance mechanisms, operating rhythms, decision frameworks, and reporting structures that provide transparency into program health and business impact. Develop KPIs, OKRs, and other measurable outcomes to track delivery, risk reduction, operational resilience, security posture, and program effectiveness. Influence senior leaders and stakeholders across Engineering, Security, Product, Infrastructure, Risk, Compliance, and Business organizations to drive alignment and timely decisions. Communicate program status, risks, dependencies, trade-offs, and strategic recommendations to senior leadership and executive stakeholders. Drive continuous improvement through standardized processes, automation, data-driven insights, and scalable program management frameworks. Identify opportunities to leverage automation, analytics, and emerging technologies to improve security operations, governance, and program execution. Lead through ambiguity by creating clarity around priorities, ownership, dependencies, decisions, and expected outcomes. Mentor and develop Technical Program Managers and other team members while promoting best practices in technical program management and execution. Ensure programs maintain a strong focus on operational excellence, quality, scalability, security, and long-term sustainability." We'll turn each line into

            • . Now Requirements from "What You'll Bring": "Extensive experience leading large-scale technical programs across multiple teams, organizations, or technology domains. Proven experience managing complex technology, cybersecurity, cloud, infrastructure, risk, resilience, or enterprise transformation programs. Strong technical acumen with the ability to engage deeply with engineering and architecture teams on system design, cloud infrastructure, security architecture, scalability, reliability, and operational readiness. Demonstrated ability to develop and execute strategic roadmaps while managing complex dependencies, resource constraints, risks, and competing priorities. Strong executive presence and communication skills, with the ability to influence senior leaders and drive decisions across organizations without direct authority. Experience operating in highly ambiguous environments and converting complex business and technical challenges into clear strategies and executable plans. Strong analytical and problem-solving skills with experience using data, metrics, and business insights to drive decisions and measure program outcomes. Experience establishing governance frameworks, operating mechanisms, KPIs, and reporting structures for large-scale programs. Demonstrated ability to identify opportunities for process improvement, automation, and operational excellence. Strong stakeholder management skills with the ability to build trusted partnerships across Engineering, Security, Product, Infrastructure, Risk, Compliance, and Business teams. Experience mentoring Technical Program Managers and contributing to a culture of continuous improvement and high performance." Make each a
            • . Minimum Qualifications: two options. Option 1: Bachelor's degree in Computer Science, Information Technology, Engineering, or related area and 6 years' experience in engineering, engineering program management, technical program management, product management, or related area. Option 2: 8 years' experience in engineering, engineering program management, technical program management, product management, or related area. We'll make each
            • . Preferred Qualifications: list from text: "Experience leading enterprise cybersecurity, cloud security, infrastructure, risk, compliance, or resilience programs. Experience working with senior executives and leading highly visible, enterprise-wide strategic initiatives. Experience with cloud platforms, distributed systems, infrastructure, security architecture, or large-scale technology transformation. Experience developing enterprise governance models, operating frameworks, and program management standards. Project Management Professional (PMP) or similar program/project management certification. Master's degree in Business Administration, Computer Science, Information Technology, Engineering, or