Sr. Technical Program Manager, Infrastructure, Amazon Leo

We need to produce HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: EEO, equal-opportunity, scam warning, application instructions, cookie/navigation/legal. Also remove duplicated lines. We need to parse the description. Key parts: - Description: Amazon Leo is Amazon’s low Earth orbit satellite broadband network... (mission). Export Control: This position requires that the candidate selected be a U.S. Citizen... (that's a requirement). We are seeking a highly experienced technical program manager to drive the development and deployment of critical enterprise infrastructure across our rapidly scaling operations. This role will be instrumental in establishing standardized infrastructure deployment practices, managing complex cross-functional programs, and ensuring operational readiness across multiple facilities and technical environments. A successful candidate is a self-starter who thrives in a start-up environment, has a passion for scaling operations, and possesses a strong background in technology infrastructure program management, network systems, telecommunications, security systems, and communications distribution design and delivery. This role requires 10-15% travel. - Key job responsibilities: list bullet points under headings: Program Management & Strategy, Technical Leadership, Stakeholder Management, Continuous Improvement. - A day in the life: paragraph. - About The Team: paragraph. - Basic Qualifications: bullet list? Actually they are lines: "5+ years of program management or technical project management experience", "Experience using data and metrics to determine and drive improvements", "Experience owning program strategy, end to end delivery, and communicating results to senior leadership". Those are basic qualifications. - Preferred Qualifications: bullet list: "5+ years of project management disciplines including scope, schedule, budget, quality, along with risk and critical path management experience", "Experience managing projects across cross functional teams, building sustainable processes and coordinating release schedules". - Benefits: paragraph: "Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits." - Pay: "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location." Then location-specific salary ranges: "USA, VA, Arlington - 148,700.00 - 201,200.00 USD annually", "USA, WA, Bellevue - 148,700.00 - 201,200.00 USD annually". Also "Company - Amazon Kuiper Manufacturing Enterprises LLC". That's metadata. - Schedule: Not explicitly given besides travel 10-15% maybe? Not schedule. No explicit schedule like full-time, part-time. Not given. So we should not create Schedule section unless posting actually states them. It does not state schedule like "Full-time" etc. So we omit Schedule. - Skills: Not explicitly listed as a separate section; but we could infer from responsibilities. However we should only include a section if posting has real specific content for it. There's no explicit "Skills" heading. We could combine skills into Requirements/Qualifications. Probably better to not create a Skills section unless there is explicit list. So we omit Skills. - About the role: we have description at start. Could be "About the role" section containing the mission description, export control, role overview, travel requirement. That seems appropriate. - Responsibilities: we have the bullet points under Program Management & Strategy etc. We'll combine into a

• list. - Requirements: could include Export Control (US Citizen), travel 10-15%, maybe also basic qualifications? Actually basic qualifications are separate. We could put Requirements as the mandatory items: US Citizen, travel 10-15%, maybe also basic qualifications? But the spec says use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We need to decide what goes into Requirements vs Qualifications. Typically Requirements are mandatory (basic qualifications). Qualifications could be preferred qualifications. But we have both Basic Qualifications and Preferred Qualifications. We'll put Basic Qualifications under Requirements (since they are required). Preferred Qualifications under Qualifications (or maybe Skills). But we have no Skills section. We'll put Preferred Qualifications under Qualifications. Benefits: we have paragraph. Pay: we have salary ranges and sign-on payments, RSUs. Schedule: none. We must not include placeholder text like "commensurate with experience". We have actual numbers. We must not repeat job title. We must not include Job ID etc. We must not include boilerplate like EEO, accommodations, etc. Remove those lines. We must preserve all substantive information: mission description, export control, role overview, travel, responsibilities (list), day in the life, about the team, basic qualifications, preferred qualifications, benefits, pay, location salary ranges, company name maybe? The company name is "Amazon Kuiper Manufacturing Enterprises LLC". That's substantive? Might be considered metadata but could be kept. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Company name maybe minor metadata but could be included in a short p. We'll include it in a paragraph under About the role maybe. We need to output only HTML fragment, no /, no markdown. We'll structure:

  About the role

  Amazon Leo is Amazon’s low Earth orbit satellite broadband network. Its mission is to deliver fast, reliable internet to customers and communities around the world, and we’ve designed the system with the capacity, flexibility, and performance to serve a wide range of customers, from individual households to schools, hospitals, businesses, government agencies, and other organizations operating in locations without reliable connectivity. Export Control: This position requires that the candidate selected be a U.S. Citizen in order to comply with U.S. government-imposed requirements related to the nature of the work and/or where it will be performed. We are seeking a highly experienced technical program manager to drive the development and deployment of critical enterprise infrastructure across our rapidly scaling operations. This role will be instrumental in establishing standardized infrastructure deployment practices, managing complex cross-functional programs, and ensuring operational readiness across multiple facilities and technical environments. A successful candidate is a self-starter who thrives in a start-up environment, has a passion for scaling operations, and possesses a strong background in technology infrastructure program management, network systems, telecommunications, security systems, and communications distribution design and delivery. This role requires 10-15% travel. Amazon Kuiper Manufacturing Enterprises LLC

  But we might want to separate company name into its own p? Could be minor metadata. We'll include as a short p after the role description. Better: after the role description paragraph, add

  Amazon Kuiper Manufacturing Enterprises LLC

  . Now Responsibilities:

  Responsibilities

  • Program Management & Strategy: Lead end-to-end infrastructure readiness programs across solution development and deployment initiatives; Develop and maintain comprehensive infrastructure deployment roadmaps aligned with business milestones; Drive standardization of infrastructure deployment processes and technical specifications; Create and manage integrated project schedules across multiple workstreams; Establish and track program KPIs, ensuring visibility and accountability
  • Technical Leadership: Provide feasibility assessment, scoping, and requirements definition across projects; Lead technical due diligence, risk assessment, and programming for infrastructure delivery; Manage WAN service feasibility studies, bid analysis, and last-mile construction; Drive network, server, and wireless infrastructure design, hardware planning, and commissioning; Oversee security systems deployment and integration; Ensure infrastructure requirements are met during facility design, permitting, and construction; Lead communications distribution design and low voltage integration efforts
  • Stakeholder Management: Act as technical liaison between internal engineering teams and project engineering vendors; Lead quarterly business reviews with engineering vendors; Partner with product managers and engineering teams on infrastructure systems development; Build and maintain strong relationships with cross-functional teams including facilities, networking, security, and operations
  • Continuous Improvement: Drive evolution of program management procedures and design standards; Implement best practices for infrastructure deployment and scaling; Develop and maintain documentation for deployment processes and technical standards; Lead operational readiness reviews and system acceptance testing; Establish metrics and reporting frameworks for infrastructure programs
  But we need to preserve the bullet points as separate items? The original had headings under responsibilities. We could make each heading as a
• with sub-bullets? But spec says use
  • for any list of duties/requirements/benefits. It didn't forbid nested lists. Could do nested
    inside
    • . Simpler: each bullet point as a
    • containing the heading and its details. We'll do that. Now Requirements:

      Requirements

      • 5+ years of program management or technical project management experience
      • Experience using data and metrics to determine and drive improvements
      • Experience owning program strategy, end to end delivery, and communicating results to senior leadership
      • U.S. Citizenship (required for export control compliance)
      • Ability to travel 10-15% of the time
      Now Qualifications (Preferred):

      Qualifications

      • 5+ years of project management disciplines including scope, schedule, budget, quality, along with risk and critical path management experience
      • Experience managing projects across cross-functional teams, building sustainable processes and coordinating release schedules
      Now Benefits:

      Benefits

      Amazon offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits.

      But spec says use

      for prose,

      • for list. Benefits is prose, okay. Should we include the link? It's part of the content. We'll include as inside

        . That's fine. Now Pay:

        Pay

        The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location.

        • USA, VA, Arlington: $148,700.00 - $201,200.00 USD annually
        • USA, WA, Bellevue: $148,700.00 - $201,200.00 USD annually
        ? Actually we need
        • . We'll put salary ranges as list items. We should not include "Company - Amazon Kuiper Manufacturing Enterprises LLC" as a separate heading; we already included company name in About the role paragraph. Could also add a short p after About the role. We'll keep it. We must not include any boilerplate like EEO, accommodations, etc. We removed. Check for duplicated lines: we have not duplicated. Check for any placeholder text like "commensurate with experience" - none. Check for any mention of "not specified" - none. Now ensure we didn't miss any substantive info: day in the life, about the team. We haven