Sr. Technical Program Manager, AWS Invoicing
Amazon Web Services (AWS) · Seattle, WA · 4 wk ago
Information TechnologyFull-time
We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate.
We need to extract content:
- About the role: description paragraph: "Join AWS Billing at a transformative moment as we revolutionize how we launch Sellers of Record (SoR) globally. You'll own the delivery of a critical set of SoR launches as part of a larger strategic initiative to accelerate AWS's ability to serve customers in 22 countries across multiple business lines—Cloud, Marketplace, Software as a Service (SAS), and Telecommunications. This is an opportunity to drive complex, cross-functional delivery that directly impacts AWS's compliance posture, regulatory risk mitigation, and revenue growth. You'll be part of a team of three TPMs collectively responsible for launching 36 SoRs and branches in 2026, with each TPM owning a portfolio of launches that will unlock incremental revenue while addressing critical tax exposure and regulatory requirements."
That's about the role.
- Responsibilities: list of duties. The posting includes "Key job responsibilities As a TPM III for SoR Launch Acceleration, you will own the end-to-end delivery of a portfolio of SoR launches within the broader 2026 program." Then bullet-like paragraphs: Program Ownership & Execution, Cross-Functional Coordination, Technical Program Management, Process Innovation & Efficiency, Stakeholder Management & Communication, A day in the life (maybe part of responsibilities). We need to extract bullet points. We'll create
- for each duty. We need to preserve all substantive info, not summarize away detail. So we need to list each bullet as separate
- with the content.
Let's parse responsibilities sections:
Program Ownership & Execution:
- Own a portfolio of SoR launches spanning multiple countries and business lines, managing the complete lifecycle from requirements gathering through production launch
- Drive delivery across multiple engineering teams including SoR development, billing systems, tax engines, payment processing, and regional infrastructure teams
- Coordinate complex dependencies between SoR configuration, billing system integration, tax compliance requirements, payment provider onboarding, and regulatory approvals
- Manage launch timelines balancing business urgency (compliance deadlines, revenue opportunities) with technical readiness and quality standards
- Accelerate delivery velocity by leveraging AI-native development approaches, identifying opportunities to use configs over custom code, and streamlining testing processes
Cross-Functional Coordination:
- Partner with regional teams to gather requirements for country-specific tax rules, regulatory compliance, payment methods, and business entity structures
- Work with legal and compliance teams to ensure SoR structures meet regulatory requirements (e.g., EECC for Telco, PCI for SAS, local tax laws)
- Coordinate with business development to understand revenue models, pricing structures, and go-to-market timing for each SoR
- Align with tax teams on PST (Provincial Sales Tax), VAT, GST, and other jurisdiction-specific tax requirements
- Engage payment providers for local payment method integration and compliance with regional payment regulations
Technical Program Management:
- Define clear requirements for each SoR launch, working backwards from customer and regulatory needs to technical specifications
- Drive architectural decisions on when to use configuration vs. custom code, ensuring solutions are maintainable and scalable
- Manage the AI-native development approach by coordinating with teams using the SoR coding agent, validating generated configs, and ensuring expert review loops are effective
- Establish testing strategies that enable 3-week UAT/PVT cycles through spec-driven testing and automation
- Identify and mitigate risks including regulatory approval delays, payment provider integration issues, tax engine configuration complexity, and cross-team dependencies
Process Innovation & Efficiency:
- Streamline launch processes by creating predictable paths for SoR development, testing, and deployment
- Identify bottlenecks in the current launch approach and work with teams to eliminate unnecessary steps or manual handoffs
- Drive adoption of AI-native methods by demonstrating value, addressing team concerns, and refining the approach based on learnings
- Create reusable patterns for common SoR configurations, testing scenarios, and launch checklists that accelerate future launches
- Establish metrics and visibility to track progress, identify issues early, and communicate status to stakeholders
Stakeholder Management & Communication:
- Communicate program status clearly and concisely to Senior Managers and Directors, highlighting progress, risks, and decisions needed
- Build consensus across diverse stakeholders with competing priorities—engineering teams focused on technical quality, business teams focused on launch dates, compliance teams focused on regulatory requirements
- Manage escalations effectively when blockers arise, knowing when to resolve issues directly vs. when to escalate to leadership
- Drive crisp decisions on scope, timeline, and resource trade-offs to keep launches on track
A day in the life: maybe we can treat as part of responsibilities but could be separate? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should put responsibilities under
Responsibilities
with a- list.
Now Requirements: The posting includes "Basic Qualifications" and "Preferred Qualifications". Those are qualifications. Also maybe "Skills" could be derived from qualifications? But we have separate sections for Requirements, Qualifications, Skills. We need to decide what goes where. The instruction: Use headings for those sections if posting has real specific content. We have Basic Qualifications and Preferred Qualifications. Those are qualifications. Requirements maybe could be the basic qualifications? But we have separate sections: Requirements and Qualifications. Usually Requirements are the mandatory qualifications; Qualifications could be preferred. But we can treat Basic Qualifications as Requirements, Preferred Qualifications as Qualifications. Skills maybe not explicitly listed; we could omit Skills section if no specific content. However there may be implied skills: technical product or program management experience, working with engineering teams, software development experience, managing cross-functional teams, etc. Those are qualifications. We could put them under Requirements (basic) and Qualifications (preferred). Skills maybe not needed.
Thus:
- Own a portfolio of SoR launches spanning multiple countries and business lines, managing the complete lifecycle from requirements gathering through production launch
- Drive delivery across multiple engineering teams including SoR development, billing systems, tax engines, payment processing, and regional infrastructure teams
- Coordinate complex dependencies between SoR configuration, billing system integration, tax compliance requirements, payment provider onboarding, and regulatory approvals
- Manage launch timelines balancing business urgency (compliance deadlines, revenue opportunities) with technical readiness and quality standards
- Accelerate delivery velocity by leveraging AI-native development approaches, identifying opportunities to use configs over custom code, and streamlining testing processes
- Partner with regional teams to gather requirements for country-specific tax rules, regulatory compliance, payment methods, and business entity structures
- Work with legal and compliance teams to ensure SoR structures meet regulatory requirements (e.g., EECC for Telco, PCI for SAS, local tax laws)
- Coordinate with business development to understand revenue models, pricing structures, and go-to-market timing for each SoR
- Align with tax teams on PST (Provincial Sales Tax), VAT, GST, and other jurisdiction-specific tax requirements
- Engage payment providers for local payment method integration and compliance with regional payment regulations
- Define clear requirements for each SoR launch, working backwards from customer and regulatory needs to technical specifications
- Drive architectural decisions on when to use configuration vs. custom code, ensuring solutions are maintainable and scalable
- Manage the AI-native development approach by coordinating with teams using the SoR coding agent, validating generated configs, and ensuring expert review loops are effective
- Establish testing strategies that enable 3-week UAT/PVT cycles through spec-driven testing and automation
- Identify and mitigate risks including regulatory approval delays, payment provider integration issues, tax engine configuration complexity, and cross-team dependencies
- Streamline launch processes by creating predictable paths for SoR development, testing, and deployment
- Identify bottlenecks in the current launch approach and work with teams to eliminate unnecessary steps or manual handoffs
- Drive adoption of AI-native methods by demonstrating value, addressing team concerns, and refining the approach based on learnings
- Create reusable patterns for common SoR configurations, testing scenarios, and launch checklists that accelerate future launches
- Establish metrics and visibility to track progress, identify issues early, and communicate status to stakeholders
- Communicate program status clearly and concisely to Senior Managers and Directors, highlighting progress, risks, and decisions needed
- Build consensus across diverse stakeholders with competing priorities—engineering teams focused on technical quality, business teams focused on launch dates, compliance teams focused on regulatory requirements
- Manage escalations effectively when blockers arise, knowing when to resolve issues directly vs. when to escalate to leadership
- Drive crisp decisions on scope, timeline
Requirements
with- list of basic qualifications:
- 5+ years of technical product or program management experience
- 7+ years of working directly with engineering teams experience
- 3+ years of software development experience
- 5+ years of technical program management working directly with software engineering teams experience
- Experience managing programs across cross functional teams, building processes and coordinating release schedules
Note: Some duplication: 5+ years technical product or program management experience and 5+ years of technical program management working directly with software engineering teams experience. Keep both as separate items.
Qualifications
with 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 - Experience defining KPI's/SLA's used to drive multi-million dollar businesses and reporting to senior leadership Now Benefits: The posting includes benefits description: "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." Also earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." Also "Learn more about our benefits at https://amazon.jobs/en/benefits." So we have benefits content. We'll put underBenefits
with a- list.
Pay: The posting includes salary range: "USA, WA, Seattle - 148,700.00 - 201,200.00 USD annually". Also mention sign-on payments and RSUs. So we have pay info. We'll put under
Pay
withmaybe. Schedule: No explicit schedule info (e.g., full-time, remote). Not present. So we omit Schedule section. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce:
About the role
Join AWS Billing at a transformative moment as we revolutionize how we launch Sellers of Record (SoR) globally. You'll own the delivery of a critical set of SoR launches as part of a larger strategic initiative to accelerate AWS's ability to serve customers in 22 countries across multiple business lines—Cloud, Marketplace, Software as a Service (SAS), and Telecommunications. This is an opportunity to drive complex, cross-functional delivery that directly impacts AWS's compliance posture, regulatory risk mitigation, and revenue growth. You'll be part of a team of three TPMs collectively responsible for launching 36 SoRs and branches in 2026, with each TPM owning a portfolio of launches that will unlock incremental revenue while addressing critical tax exposure and regulatory requirements.
Responsibilities