Principal Product Manager – Technical, AWS Security
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists,
for prose
3. Do NOT repeat job title as heading
4. Do NOT put Job ID/requisition numbers as headings - fold into short
or drop
5. Preserve ALL substantive information
6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions)
7. Include section ONLY when posting has real, specific content - never emit heading followed by filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless posting actually states them
9. Prefer few substantive sections over many thin ones
10. Output ONLY HTML fragment - no /, no markdown code fences
Let me identify the sections from the posting:
- "Description" - this is the "About the role" section
- "Key job responsibilities" - this is "Responsibilities"
- "About The Team" - this has subsections: "Diverse Experiences", "Why Amazon Security?", "Inclusive Team Culture", "Training & Career Growth", "Work/Life Balance" - these are more about company culture, could be part of "About the team" or "Benefits"
- "Basic Qualifications" - this is "Requirements" or "Qualifications"
- "Preferred Qualifications" - this is "Preferred Qualifications" or part of "Qualifications"
- Salary information at the end - this is "Pay"
- Company and Job ID at the end - metadata
I need to be careful about what to include. The "About The Team" section has some substantive content about culture, DEI, training, work-life balance. The salary ranges are specific. The job ID should be folded into a short
or dropped.
Let me structure:
1. About the role (from Description)
2. Responsibilities (from Key job responsibilities)
3. Qualifications (combining Basic and Preferred)
4. About the team (from About The Team - but only substantive parts)
5. Pay (from salary ranges)
6. Maybe a brief metadata line for company/location
I should not create a "Benefits" section unless the posting actually states specific benefits. The posting does mention "comprehensive benefits including health insurance..." but it's generic Amazon benefits, not specific to this role. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state pay ranges specifically for this role in specific locations. It mentions benefits but generically. I'll include Pay since specific ranges are given. For Benefits, it's generic Amazon benefits - I could include a brief mention in About the team or skip. The rule says prefer few substantive sections. I'll include Pay.
For Schedule - not mentioned, so no Schedule section.
Now, let me write the HTML.
I'll use
for headings. For lists, - . For prose,
.
I need to preserve all substantive information. So I'll include all the bullet points from responsibilities, qualifications, etc.
Let me draft:
About the role
At Amazon Web Services (AWS), Security is our highest priority. We are building a set of AI-native security products that change how AWS prevents, finds, and responds to security risk. One product evaluates code as builders write it and fixes issues automatically. Another finds and remediates vulnerabilities across the AWS fleet, from host and container operating systems to third-party software. A third automates investigation and triage for security operations teams. We are looking for a Principal Product Manager – Technical to own the product strategy across this suite.
The products solve the same basic problem at different points in the security lifecycle: work out what is affected, judge how serious it is, and act on it. Nobody owns the product decisions that cut across them today. You will decide which capabilities should be shared and which should stay product-specific, what each product promises its customers, and where to build new, extend what exists, or retire overlap.
Your customers are technical. Software builders want security that doesn't slow them down. Security engineers need coverage they can trust. Security operations teams need investigation and response that scales. You will represent all three, decide which need wins when they conflict, and drive the engineering, science, and program teams to deliver the right products. The strategy that ties the suite together has not been defined yet, and you will be trusted to define it with complete independence.
Responsibilities
- Define a multi-year vision and long-term roadmap for a suite of security products, and drive teams to deliver it
- Decide where products converge on shared capabilities and where they stay separate; make the invent, extend, or retire calls
- Serve as the voice of the customer for software builders, security engineers, and security operations teams, grounded in customer research and data
- Write PR/FAQs, decision narratives, and investment proposals that make the case for the suite's direction to senior leadership
- Build the measurement, intake, and reporting mechanisms that keep each product aligned with its customers over the long term
- Partner with technical program managers who own multi-team delivery, and with engineering and science leaders on architecture and priorities
- Take point on customer-impacting product issues and executive-level escalations
- Mentor product managers and contribute to hiring and promotion assessments
Qualifications
Basic Qualifications
- 10+ years of technical product or program management experience
- Experience owning/driving roadmap strategy and definition
- Experience leading cross-organizational programs and setting and holding teams and individuals to timelines and deliverables without explicit authority
- Experience technical product management
- Experience leading engineering discussions around technology decisions and strategy related to a product
Preferred Qualifications
- Experience in project management methodologies, business analysis, or process improvement
- Experience in any combination of the following: application security frameworks, security code reviews, incident response, secure infrastructure, penetration testing, mobile security, cloud security, AI security, identity and access controls, threat modeling, cryptography, threat intelligence, or secure software development
- Experience with AI/ML technologies
- Experience coordinating between technical teams, peers and business stakeholders
About the team
Amazon Security values diverse experiences. Even if you do not meet all of the qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn't followed a traditional path, or includes alternative experiences, don't let it stop you from applying.
At Amazon, security is central to maintaining customer trust and delivering delightful customer experiences. Our organization is responsible for creating and maintaining a high bar for security across all of Amazon's products and services. We offer talented security professionals the chance to accelerate their careers with opportunities to build experience in a wide variety of areas including cloud, devices, retail, entertainment, healthcare, operations, and physical stores.
In Amazon Security, it's in our nature to learn and be curious. Ongoing DEI events and learning experiences inspire us to continue learning and to embrace our uniqueness. Addressing the toughest security challenges requires that we seek out and celebrate a diversity of ideas, perspectives, and voices.
We're continuously raising our performance bar as we strive to become Earth's Best Employer. That's why you'll find endless knowledge-sharing, training, and other career-advancing resources here to help you develop into a better-rounded professional.
We value work-life harmony. Achieving success at work should never come at the expense of sacrifices at home, which is why flexible work hours and arrangements are part of our culture. When we feel supported in the workplace and at home, there's nothing we can't achieve.
Pay
The base salary range for this position varies by location:
- USA, TX, Austin: $179,900 - $243,400 annually
- USA, VA, Arlington: $179,900 - $243,400 annually
- USA, WA, Seattle: $179,900 - $243,400 annually
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. 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.
Company: Amazon.com Services LLC | Job ID: A10583503
Wait, the rule says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." So I'll fold into a short
at the end.
Also, I used
for Basic/Preferred Qualifications subheadings. The rule says use for section headings. It doesn't forbid for subsections, but to be safe, maybe I should keep only for main sections and use
or for subsections. But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say not to use other heading levels. However, to keep it simple, I could make Basic and Preferred as separate sections, but they are subsections of Qualifications. I think using is fine for subsections. But the instruction says "use for section headings" - it might imply only should be used. To be safe, I'll make them separate sections: "Basic Qualifications" and "Preferred Qualifications". But that might create too many thin sections. The rule says "Prefer a few substantive sections over many thin ones." So combining under one "Qualifications" section with subheadings is better. I'll use for subsections.
Alternatively, I could use for the subheadings. But is semantic. I'll keep .
Now, check for boilerplate removal: The posting includes EEO statement: "Amazon is an equal opportunity employer and does not discriminate..." and accommodation link. That's boilerplate, should be removed. Also "Learn more about our benefits at https://amazon.jobs/en/benefits." - that's a link, boilerplate. I'll remove those.
Also "If you have a disability and need a workplace accommodation..." - boilerplate.
I'll remove those.
Now, the "About the team" section includes "Why Amazon Security?", "Inclusive Team Culture", "Training & Career Growth", "Work/Life Balance". I've incorporated them as paragraphs.
The "Diverse Experiences" is also included.
Now, the Pay section: I included the salary ranges and the benefits mention. The benefits are generic but the posting does state them. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states pay ranges specifically, and mentions benefits. So Pay section is appropriate. I included benefits in the Pay section as part of
for prose 3. Do NOT repeat job title as heading 4. Do NOT put Job ID/requisition numbers as headings - fold into short
or drop 5. Preserve ALL substantive information 6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) 7. Include section ONLY when posting has real, specific content - never emit heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless posting actually states them 9. Prefer few substantive sections over many thin ones 10. Output ONLY HTML fragment - no /, no markdown code fences Let me identify the sections from the posting: - "Description" - this is the "About the role" section - "Key job responsibilities" - this is "Responsibilities" - "About The Team" - this has subsections: "Diverse Experiences", "Why Amazon Security?", "Inclusive Team Culture", "Training & Career Growth", "Work/Life Balance" - these are more about company culture, could be part of "About the team" or "Benefits" - "Basic Qualifications" - this is "Requirements" or "Qualifications" - "Preferred Qualifications" - this is "Preferred Qualifications" or part of "Qualifications" - Salary information at the end - this is "Pay" - Company and Job ID at the end - metadata I need to be careful about what to include. The "About The Team" section has some substantive content about culture, DEI, training, work-life balance. The salary ranges are specific. The job ID should be folded into a short
or dropped. Let me structure: 1. About the role (from Description) 2. Responsibilities (from Key job responsibilities) 3. Qualifications (combining Basic and Preferred) 4. About the team (from About The Team - but only substantive parts) 5. Pay (from salary ranges) 6. Maybe a brief metadata line for company/location I should not create a "Benefits" section unless the posting actually states specific benefits. The posting does mention "comprehensive benefits including health insurance..." but it's generic Amazon benefits, not specific to this role. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state pay ranges specifically for this role in specific locations. It mentions benefits but generically. I'll include Pay since specific ranges are given. For Benefits, it's generic Amazon benefits - I could include a brief mention in About the team or skip. The rule says prefer few substantive sections. I'll include Pay. For Schedule - not mentioned, so no Schedule section. Now, let me write the HTML. I'll use
for headings. For lists, - . For prose,
.
I need to preserve all substantive information. So I'll include all the bullet points from responsibilities, qualifications, etc.
Let me draft:
About the role
At Amazon Web Services (AWS), Security is our highest priority. We are building a set of AI-native security products that change how AWS prevents, finds, and responds to security risk. One product evaluates code as builders write it and fixes issues automatically. Another finds and remediates vulnerabilities across the AWS fleet, from host and container operating systems to third-party software. A third automates investigation and triage for security operations teams. We are looking for a Principal Product Manager – Technical to own the product strategy across this suite.
The products solve the same basic problem at different points in the security lifecycle: work out what is affected, judge how serious it is, and act on it. Nobody owns the product decisions that cut across them today. You will decide which capabilities should be shared and which should stay product-specific, what each product promises its customers, and where to build new, extend what exists, or retire overlap.
Your customers are technical. Software builders want security that doesn't slow them down. Security engineers need coverage they can trust. Security operations teams need investigation and response that scales. You will represent all three, decide which need wins when they conflict, and drive the engineering, science, and program teams to deliver the right products. The strategy that ties the suite together has not been defined yet, and you will be trusted to define it with complete independence.
Responsibilities
- Define a multi-year vision and long-term roadmap for a suite of security products, and drive teams to deliver it
- Decide where products converge on shared capabilities and where they stay separate; make the invent, extend, or retire calls
- Serve as the voice of the customer for software builders, security engineers, and security operations teams, grounded in customer research and data
- Write PR/FAQs, decision narratives, and investment proposals that make the case for the suite's direction to senior leadership
- Build the measurement, intake, and reporting mechanisms that keep each product aligned with its customers over the long term
- Partner with technical program managers who own multi-team delivery, and with engineering and science leaders on architecture and priorities
- Take point on customer-impacting product issues and executive-level escalations
- Mentor product managers and contribute to hiring and promotion assessments
Qualifications
Basic Qualifications
- 10+ years of technical product or program management experience
- Experience owning/driving roadmap strategy and definition
- Experience leading cross-organizational programs and setting and holding teams and individuals to timelines and deliverables without explicit authority
- Experience technical product management
- Experience leading engineering discussions around technology decisions and strategy related to a product
Preferred Qualifications
- Experience in project management methodologies, business analysis, or process improvement
- Experience in any combination of the following: application security frameworks, security code reviews, incident response, secure infrastructure, penetration testing, mobile security, cloud security, AI security, identity and access controls, threat modeling, cryptography, threat intelligence, or secure software development
- Experience with AI/ML technologies
- Experience coordinating between technical teams, peers and business stakeholders
About the team
Amazon Security values diverse experiences. Even if you do not meet all of the qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn't followed a traditional path, or includes alternative experiences, don't let it stop you from applying.
At Amazon, security is central to maintaining customer trust and delivering delightful customer experiences. Our organization is responsible for creating and maintaining a high bar for security across all of Amazon's products and services. We offer talented security professionals the chance to accelerate their careers with opportunities to build experience in a wide variety of areas including cloud, devices, retail, entertainment, healthcare, operations, and physical stores.
In Amazon Security, it's in our nature to learn and be curious. Ongoing DEI events and learning experiences inspire us to continue learning and to embrace our uniqueness. Addressing the toughest security challenges requires that we seek out and celebrate a diversity of ideas, perspectives, and voices.
We're continuously raising our performance bar as we strive to become Earth's Best Employer. That's why you'll find endless knowledge-sharing, training, and other career-advancing resources here to help you develop into a better-rounded professional.
We value work-life harmony. Achieving success at work should never come at the expense of sacrifices at home, which is why flexible work hours and arrangements are part of our culture. When we feel supported in the workplace and at home, there's nothing we can't achieve.
Pay
The base salary range for this position varies by location:
- USA, TX, Austin: $179,900 - $243,400 annually
- USA, VA, Arlington: $179,900 - $243,400 annually
- USA, WA, Seattle: $179,900 - $243,400 annually
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. 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.
Company: Amazon.com Services LLC | Job ID: A10583503
Wait, the rule says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." So I'll fold into a short
at the end.
Also, I used
for Basic/Preferred Qualifications subheadings. The rule says use for section headings. It doesn't forbid for subsections, but to be safe, maybe I should keep only for main sections and use
or for subsections. But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say not to use other heading levels. However, to keep it simple, I could make Basic and Preferred as separate sections, but they are subsections of Qualifications. I think using is fine for subsections. But the instruction says "use for section headings" - it might imply only should be used. To be safe, I'll make them separate sections: "Basic Qualifications" and "Preferred Qualifications". But that might create too many thin sections. The rule says "Prefer a few substantive sections over many thin ones." So combining under one "Qualifications" section with subheadings is better. I'll use for subsections.
Alternatively, I could use for the subheadings. But is semantic. I'll keep .
Now, check for boilerplate removal: The posting includes EEO statement: "Amazon is an equal opportunity employer and does not discriminate..." and accommodation link. That's boilerplate, should be removed. Also "Learn more about our benefits at https://amazon.jobs/en/benefits." - that's a link, boilerplate. I'll remove those.
Also "If you have a disability and need a workplace accommodation..." - boilerplate.
I'll remove those.
Now, the "About the team" section includes "Why Amazon Security?", "Inclusive Team Culture", "Training & Career Growth", "Work/Life Balance". I've incorporated them as paragraphs.
The "Diverse Experiences" is also included.
Now, the Pay section: I included the salary ranges and the benefits mention. The benefits are generic but the posting does state them. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states pay ranges specifically, and mentions benefits. So Pay section is appropriate. I included benefits in the Pay section as part of
. I need to preserve all substantive information. So I'll include all the bullet points from responsibilities, qualifications, etc. Let me draft:
About the role
At Amazon Web Services (AWS), Security is our highest priority. We are building a set of AI-native security products that change how AWS prevents, finds, and responds to security risk. One product evaluates code as builders write it and fixes issues automatically. Another finds and remediates vulnerabilities across the AWS fleet, from host and container operating systems to third-party software. A third automates investigation and triage for security operations teams. We are looking for a Principal Product Manager – Technical to own the product strategy across this suite.
The products solve the same basic problem at different points in the security lifecycle: work out what is affected, judge how serious it is, and act on it. Nobody owns the product decisions that cut across them today. You will decide which capabilities should be shared and which should stay product-specific, what each product promises its customers, and where to build new, extend what exists, or retire overlap.
Your customers are technical. Software builders want security that doesn't slow them down. Security engineers need coverage they can trust. Security operations teams need investigation and response that scales. You will represent all three, decide which need wins when they conflict, and drive the engineering, science, and program teams to deliver the right products. The strategy that ties the suite together has not been defined yet, and you will be trusted to define it with complete independence.
Responsibilities
- Define a multi-year vision and long-term roadmap for a suite of security products, and drive teams to deliver it
- Decide where products converge on shared capabilities and where they stay separate; make the invent, extend, or retire calls
- Serve as the voice of the customer for software builders, security engineers, and security operations teams, grounded in customer research and data
- Write PR/FAQs, decision narratives, and investment proposals that make the case for the suite's direction to senior leadership
- Build the measurement, intake, and reporting mechanisms that keep each product aligned with its customers over the long term
- Partner with technical program managers who own multi-team delivery, and with engineering and science leaders on architecture and priorities
- Take point on customer-impacting product issues and executive-level escalations
- Mentor product managers and contribute to hiring and promotion assessments
Qualifications
Basic Qualifications
- 10+ years of technical product or program management experience
- Experience owning/driving roadmap strategy and definition
- Experience leading cross-organizational programs and setting and holding teams and individuals to timelines and deliverables without explicit authority
- Experience technical product management
- Experience leading engineering discussions around technology decisions and strategy related to a product
Preferred Qualifications
- Experience in project management methodologies, business analysis, or process improvement
- Experience in any combination of the following: application security frameworks, security code reviews, incident response, secure infrastructure, penetration testing, mobile security, cloud security, AI security, identity and access controls, threat modeling, cryptography, threat intelligence, or secure software development
- Experience with AI/ML technologies
- Experience coordinating between technical teams, peers and business stakeholders
About the team
Amazon Security values diverse experiences. Even if you do not meet all of the qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn't followed a traditional path, or includes alternative experiences, don't let it stop you from applying.
At Amazon, security is central to maintaining customer trust and delivering delightful customer experiences. Our organization is responsible for creating and maintaining a high bar for security across all of Amazon's products and services. We offer talented security professionals the chance to accelerate their careers with opportunities to build experience in a wide variety of areas including cloud, devices, retail, entertainment, healthcare, operations, and physical stores.
In Amazon Security, it's in our nature to learn and be curious. Ongoing DEI events and learning experiences inspire us to continue learning and to embrace our uniqueness. Addressing the toughest security challenges requires that we seek out and celebrate a diversity of ideas, perspectives, and voices.
We're continuously raising our performance bar as we strive to become Earth's Best Employer. That's why you'll find endless knowledge-sharing, training, and other career-advancing resources here to help you develop into a better-rounded professional.
We value work-life harmony. Achieving success at work should never come at the expense of sacrifices at home, which is why flexible work hours and arrangements are part of our culture. When we feel supported in the workplace and at home, there's nothing we can't achieve.
Pay
The base salary range for this position varies by location:
- USA, TX, Austin: $179,900 - $243,400 annually
- USA, VA, Arlington: $179,900 - $243,400 annually
- USA, WA, Seattle: $179,900 - $243,400 annually
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. 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.
Company: Amazon.com Services LLC | Job ID: A10583503
Wait, the rule says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." So I'll fold into a short
at the end. Also, I used
for Basic/Preferred Qualifications subheadings. The rule says use for section headings. It doesn't forbid for subsections, but to be safe, maybe I should keep only for main sections and use
for subsections, but to be safe, maybe I should keep only for main sections and use
or for subsections. But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say not to use other heading levels. However, to keep it simple, I could make Basic and Preferred as separate
sections, but they are subsections of Qualifications. I think using
is fine for subsections. But the instruction says "use
for section headings" - it might imply only
should be used. To be safe, I'll make them separate
sections: "Basic Qualifications" and "Preferred Qualifications". But that might create too many thin sections. The rule says "Prefer a few substantive sections over many thin ones." So combining under one "Qualifications" section with subheadings is better. I'll use
for subsections.
Alternatively, I could use for the subheadings. But
is semantic. I'll keep
.
Now, check for boilerplate removal: The posting includes EEO statement: "Amazon is an equal opportunity employer and does not discriminate..." and accommodation link. That's boilerplate, should be removed. Also "Learn more about our benefits at https://amazon.jobs/en/benefits." - that's a link, boilerplate. I'll remove those.
Also "If you have a disability and need a workplace accommodation..." - boilerplate.
I'll remove those.
Now, the "About the team" section includes "Why Amazon Security?", "Inclusive Team Culture", "Training & Career Growth", "Work/Life Balance". I've incorporated them as paragraphs.
The "Diverse Experiences" is also included.
Now, the Pay section: I included the salary ranges and the benefits mention. The benefits are generic but the posting does state them. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states pay ranges specifically, and mentions benefits. So Pay section is appropriate. I included benefits in the Pay section as part of