Sr. Partner Marketing Manager, NAMER Strategic Customer and Partner Marketing
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule).
- Use `- ` for lists of duties/requirements/benefits.
- Use `
` for prose.
- Do NOT repeat the job title as a heading (already shown).
- Do NOT put Job ID / requisition numbers as headings - fold minor metadata into a short `
` or drop it.
- Preserve ALL substantive information; do NOT invent or summarize away detail.
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
- IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them.
- Prefer a few substantive sections over many thin ones.
- Output ONLY the HTML fragment — no `/`, no markdown code fences.
2. **Analyze the Input Text:**
Let me carefully go through the posting and extract relevant sections, removing boilerplate.
**Job Title:** Already mentioned as "Senior Partner Marketing Manager" but rules say don't repeat as heading. The page already shows it, so I should not include a heading for it. I might mention it in a meta way but not as an `
`. Actually, the rule says "Do NOT repeat the job title as a heading (the page already shows it)". So I'll just skip any job title heading.
**Sections to consider:**
- About the role / Role description
- Responsibilities
- Requirements/Qualifications
- Skills
- Benefits
- Pay/Salary
- Schedule
Let's parse the content:
**Role description/context:**
"Amazon Web Services (AWS) is seeking an experienced Senior Partner Marketing Manager to build awareness, create demand and drive revenue with Global System Integrator (GSI) and Multi-national SI/Consulting Partners in North America. This is a unique opportunity to play a key role in an exciting, fast growing business. This position will be managing the strategic marketing plans for 4-6 large System Integrator, Reseller or Consulting partners. The ideal candidate needs to be able to drive strategic, comprehensive, marketing plans at the highest levels of the organization. Marketing experience with a breadth of channel partners is a must. The goals for this position are to collaborate with the dedicated sales team to design, develop, implement, and measure successful marketing programs that help meet the account objectives. They need to drive partner generated leads, maximize marketing funds, and acquire new customers."
**Responsibilities (Key job responsibilities section):**
"Work closely with global Partner Marketing, Field Marketing and Partner Business Development (PDM) sales teams to align priorities and develop partner marketing initiatives.
Define annual joint marketing strategies, objectives and measures of success with the SI partner's marketing team
Develop and execute best-in-class partner co-marketing plans that effectively drive awareness and adoption of AWS compute services
Manage annual partner marketing budget- generating partner-led opportunities, tracking accruals, marketing spend and reimbursement claims"
**About The Team:**
"The North America Partner Marketing team works with top AWS Consulting Partners to develop and execute marketing strategies that align to the partner sales objectives and generate AWS partner-led opportunities. The Sr. PMM will work across many stakeholders to include the partner in appropriate AWS-led marketing motions and amplify the partners’ unique value-add. The Sr. PMM will plan and execute marketing campaigns and measure ROI. This role requires tight alignment with regional partner development managers (PDMs) and global counterparts."
**Basic Qualifications:**
"7+ years of developing and managing acquisition marketing or channel programs experience
Experience using data and metrics to drive improvements
Experience building, executing and scaling cross-functional marketing programs
Experience developing and executing campaigns across a multitude of timezones and languages
+6 years partner marketing experience with large regional and global system integrator partners"
**Preferred Qualifications:**
"Experience driving direction and alignment with large cross-functional teams and agency partners
Experience designing and executing joint marketing plans with strategic alliance partners with global footprint
Experience marketing Cloud services"
**Boilerplate to remove:**
- "Amazon is an equal opportunity employer and does not discriminate..." etc.
- "Los Angeles County applicants: ..." etc.
- "Criminal history may have a direct, adverse, and negative relationship..." etc.
- "Pursuant to the Los Angeles County Fair Chance Ordinance..." etc.
- "Pursuant to the San Francisco Fair Chance Ordinance..." etc.
- "Our inclusive culture empowers Amazonians..." etc.
- "If you have a disability and need a workplace accommodation..." etc.
- "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner."
- "Company - Amazon Web Services, Inc."
- "Job ID: A10537931"
- Salary information is present but structured per location. Need to handle Pay section carefully. The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It also says: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The posting does state salary ranges per location. I should include a Pay section with the actual salary data, but carefully. The rule also says "Prefer a few substantive sections over many thin ones." I need to decide if Pay is worth including given the strict rules. It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state them. But it also says "do NOT repeat the job title as heading" and "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." I'll fold Job ID and company into a short
maybe at the end or beginning, but not as a heading.
Let's re-read the Pay/Benefits part: "In addition, they will also be required to manage outside vendors to execute programs and achieve goals, including not limited to, managing Account Based Marketing programs, broad-scale partner programs, etc." That's responsibility, not benefit.
The posting has this at the end: "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. 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." Then it lists locations and salary ranges.
Rules: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. But also: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them." So I can create Pay and Benefits sections if I have real content. However, the rule also says: "Prefer a few substantive sections over many thin ones." and "Output ONLY the HTML fragment — no /, no markdown code fences."
I need to be careful not to create thin sections. The posting has specific salary ranges per location, and specific benefits list. I should include them but structured properly.
Let's outline the HTML structure based on rules:
- Use `
` for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But only include if there's real content.
- "About the role" - I have role description.
- "Responsibilities" - I have key responsibilities and about the team. Might combine or have two sections. Rule says use `` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I'll map accordingly.
- "Requirements" - Basic Qualifications.
- "Qualifications" - Maybe merge Basic and Preferred? Or have Requirements as one, Qualifications as another? The list includes Basic Qualifications and Preferred Qualifications. I'll make "Requirements" for Basic, and maybe "Qualifications" for Preferred? Or combine? Rule: "Prefer a few substantive sections over many thin ones." I'll likely have one section for qualifications covering both, or separate if there's enough. I'll see.
- "Skills" - maybe not explicitly separate, but I can infer from description. The posting mentions skills implicitly. I'll maybe include under Qualifications or skip if thin.
- "Benefits" - posting has comprehensive benefits list.
- "Pay" - posting has salary ranges per location.
- "Schedule" - not mentioned. So I should NOT create a Schedule section.
Let's decide on sections to include:
1. About the role (or Role description) - has content.
2. Responsibilities - has content (Key job responsibilities + About The Team could be part of it or separate. I'll combine or have Responsibilities and maybe Team as part of About the role. Rule says use headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay". I'll stick to those labels or similar, but must have real content.)
3. Requirements - Basic Qualifications.
4. Qualifications - Preferred Qualifications. Or merge. I'll make "Requirements" for Basic, and maybe not separate "Qualifications" if it becomes thin. But Preferred Qualifications is substantial. I'll create "Requirements" and "Qualifications" as two sections, but ensure they're not thin. Or I could combine into one "Qualifications" section with basic and preferred listed. Rule: "use - for any list of duties/requirements/benefits". I'll do that.
5. Benefits - has content.
6. Pay - has content (salary ranges per location). I'll include but format concisely.
7. Schedule - not mentioned, skip.
Now, Job ID and company: "fold minor metadata into a short
or drop it." I'll fold them into a short
at the end or beginning, not as a heading.
Remove all boilerplate: EEO, LA County, SF Fair Chance, disability accommodations, recruiting partner, etc.
Let's extract and structure:
**About the role** (I'll use `
About the role
`)
Content: AWS seeking experienced Senior Partner Marketing Manager to build awareness, create demand and drive revenue with GSI and multi-national SI/Consulting Partners in North America. This is a unique opportunity to play a key role in an exciting, fast growing business. This position will be managing the strategic marketing plans for 4-6 large System Integrator, Reseller or Consulting partners. The ideal candidate needs to be able to drive strategic, comprehensive, marketing plans at the highest levels of the organization. Marketing experience with a breadth of channel partners is a must. The goals for this position are to collaborate with the dedicated sales team to design,
` for prose. - Do NOT repeat the job title as a heading (already shown). - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into a short `
` or drop it. - Preserve ALL substantive information; do NOT invent or summarize away detail. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. - Prefer a few substantive sections over many thin ones. - Output ONLY the HTML fragment — no `/`, no markdown code fences. 2. **Analyze the Input Text:** Let me carefully go through the posting and extract relevant sections, removing boilerplate. **Job Title:** Already mentioned as "Senior Partner Marketing Manager" but rules say don't repeat as heading. The page already shows it, so I should not include a heading for it. I might mention it in a meta way but not as an `
`. Actually, the rule says "Do NOT repeat the job title as a heading (the page already shows it)". So I'll just skip any job title heading. **Sections to consider:** - About the role / Role description - Responsibilities - Requirements/Qualifications - Skills - Benefits - Pay/Salary - Schedule Let's parse the content: **Role description/context:** "Amazon Web Services (AWS) is seeking an experienced Senior Partner Marketing Manager to build awareness, create demand and drive revenue with Global System Integrator (GSI) and Multi-national SI/Consulting Partners in North America. This is a unique opportunity to play a key role in an exciting, fast growing business. This position will be managing the strategic marketing plans for 4-6 large System Integrator, Reseller or Consulting partners. The ideal candidate needs to be able to drive strategic, comprehensive, marketing plans at the highest levels of the organization. Marketing experience with a breadth of channel partners is a must. The goals for this position are to collaborate with the dedicated sales team to design, develop, implement, and measure successful marketing programs that help meet the account objectives. They need to drive partner generated leads, maximize marketing funds, and acquire new customers." **Responsibilities (Key job responsibilities section):** "Work closely with global Partner Marketing, Field Marketing and Partner Business Development (PDM) sales teams to align priorities and develop partner marketing initiatives. Define annual joint marketing strategies, objectives and measures of success with the SI partner's marketing team Develop and execute best-in-class partner co-marketing plans that effectively drive awareness and adoption of AWS compute services Manage annual partner marketing budget- generating partner-led opportunities, tracking accruals, marketing spend and reimbursement claims" **About The Team:** "The North America Partner Marketing team works with top AWS Consulting Partners to develop and execute marketing strategies that align to the partner sales objectives and generate AWS partner-led opportunities. The Sr. PMM will work across many stakeholders to include the partner in appropriate AWS-led marketing motions and amplify the partners’ unique value-add. The Sr. PMM will plan and execute marketing campaigns and measure ROI. This role requires tight alignment with regional partner development managers (PDMs) and global counterparts." **Basic Qualifications:** "7+ years of developing and managing acquisition marketing or channel programs experience Experience using data and metrics to drive improvements Experience building, executing and scaling cross-functional marketing programs Experience developing and executing campaigns across a multitude of timezones and languages +6 years partner marketing experience with large regional and global system integrator partners" **Preferred Qualifications:** "Experience driving direction and alignment with large cross-functional teams and agency partners Experience designing and executing joint marketing plans with strategic alliance partners with global footprint Experience marketing Cloud services" **Boilerplate to remove:** - "Amazon is an equal opportunity employer and does not discriminate..." etc. - "Los Angeles County applicants: ..." etc. - "Criminal history may have a direct, adverse, and negative relationship..." etc. - "Pursuant to the Los Angeles County Fair Chance Ordinance..." etc. - "Pursuant to the San Francisco Fair Chance Ordinance..." etc. - "Our inclusive culture empowers Amazonians..." etc. - "If you have a disability and need a workplace accommodation..." etc. - "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." - "Company - Amazon Web Services, Inc." - "Job ID: A10537931" - Salary information is present but structured per location. Need to handle Pay section carefully. The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It also says: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The posting does state salary ranges per location. I should include a Pay section with the actual salary data, but carefully. The rule also says "Prefer a few substantive sections over many thin ones." I need to decide if Pay is worth including given the strict rules. It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state them. But it also says "do NOT repeat the job title as heading" and "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." I'll fold Job ID and company into a short
maybe at the end or beginning, but not as a heading. Let's re-read the Pay/Benefits part: "In addition, they will also be required to manage outside vendors to execute programs and achieve goals, including not limited to, managing Account Based Marketing programs, broad-scale partner programs, etc." That's responsibility, not benefit. The posting has this at the end: "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. 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." Then it lists locations and salary ranges. Rules: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. But also: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them." So I can create Pay and Benefits sections if I have real content. However, the rule also says: "Prefer a few substantive sections over many thin ones." and "Output ONLY the HTML fragment — no /, no markdown code fences." I need to be careful not to create thin sections. The posting has specific salary ranges per location, and specific benefits list. I should include them but structured properly. Let's outline the HTML structure based on rules: - Use `
` for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But only include if there's real content.
- "About the role" - I have role description.
- "Responsibilities" - I have key responsibilities and about the team. Might combine or have two sections. Rule says use `` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I'll map accordingly.
- "Requirements" - Basic Qualifications.
- "Qualifications" - Maybe merge Basic and Preferred? Or have Requirements as one, Qualifications as another? The list includes Basic Qualifications and Preferred Qualifications. I'll make "Requirements" for Basic, and maybe "Qualifications" for Preferred? Or combine? Rule: "Prefer a few substantive sections over many thin ones." I'll likely have one section for qualifications covering both, or separate if there's enough. I'll see.
- "Skills" - maybe not explicitly separate, but I can infer from description. The posting mentions skills implicitly. I'll maybe include under Qualifications or skip if thin.
- "Benefits" - posting has comprehensive benefits list.
- "Pay" - posting has salary ranges per location.
- "Schedule" - not mentioned. So I should NOT create a Schedule section.
Let's decide on sections to include:
1. About the role (or Role description) - has content.
2. Responsibilities - has content (Key job responsibilities + About The Team could be part of it or separate. I'll combine or have Responsibilities and maybe Team as part of About the role. Rule says use headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay". I'll stick to those labels or similar, but must have real content.)
3. Requirements - Basic Qualifications.
4. Qualifications - Preferred Qualifications. Or merge. I'll make "Requirements" for Basic, and maybe not separate "Qualifications" if it becomes thin. But Preferred Qualifications is substantial. I'll create "Requirements" and "Qualifications" as two sections, but ensure they're not thin. Or I could combine into one "Qualifications" section with basic and preferred listed. Rule: "use - for any list of duties/requirements/benefits". I'll do that.
5. Benefits - has content.
6. Pay - has content (salary ranges per location). I'll include but format concisely.
7. Schedule - not mentioned, skip.
Now, Job ID and company: "fold minor metadata into a short
or drop it." I'll fold them into a short
at the end or beginning, not as a heading.
Remove all boilerplate: EEO, LA County, SF Fair Chance, disability accommodations, recruiting partner, etc.
Let's extract and structure:
**About the role** (I'll use `
About the role
`)
Content: AWS seeking experienced Senior Partner Marketing Manager to build awareness, create demand and drive revenue with GSI and multi-national SI/Consulting Partners in North America. This is a unique opportunity to play a key role in an exciting, fast growing business. This position will be managing the strategic marketing plans for 4-6 large System Integrator, Reseller or Consulting partners. The ideal candidate needs to be able to drive strategic, comprehensive, marketing plans at the highest levels of the organization. Marketing experience with a breadth of channel partners is a must. The goals for this position are to collaborate with the dedicated sales team to design,
- for any list of duties/requirements/benefits". I'll do that.
5. Benefits - has content.
6. Pay - has content (salary ranges per location). I'll include but format concisely.
7. Schedule - not mentioned, skip.
Now, Job ID and company: "fold minor metadata into a short
or drop it." I'll fold them into a short
at the end or beginning, not as a heading. Remove all boilerplate: EEO, LA County, SF Fair Chance, disability accommodations, recruiting partner, etc. Let's extract and structure: **About the role** (I'll use `
About the role
`) Content: AWS seeking experienced Senior Partner Marketing Manager to build awareness, create demand and drive revenue with GSI and multi-national SI/Consulting Partners in North America. This is a unique opportunity to play a key role in an exciting, fast growing business. This position will be managing the strategic marketing plans for 4-6 large System Integrator, Reseller or Consulting partners. The ideal candidate needs to be able to drive strategic, comprehensive, marketing plans at the highest levels of the organization. Marketing experience with a breadth of channel partners is a must. The goals for this position are to collaborate with the dedicated sales team to design,