Sr. Marketing Operations Manager, AWS Marketing Strategy, Operations, and Enablement
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
Thus for each section we need to decide if content is list or prose.
About the role: prose paragraph(s). Could be one
.
Responsibilities: The responsibilities paragraph includes multiple sentences; could be a list? It's not explicitly bullet list but we could treat as prose. However instruction: use
- for any list of duties/requirements/benefits. Since it's not a list but prose, we can use
. But we could also split into bullet points? Better to keep as prose to preserve detail.
Requirements: Basic Qualifications list items. Use
- .
Qualifications: Preferred Qualifications list items. Use
- .
Benefits: list of benefits items. Use
- .
Pay: list of location salary ranges. Could be a list.
We must not include boilerplate like "Learn more about our benefits at https://..." maybe we can keep as part of benefits? It's a link; but it's still substantive? It's a reference. Might be considered boilerplate? It's not EEO etc. It's a link to benefits page. Might be okay to keep as part of benefits paragraph. But we could incorporate as a
after list.
Similarly for Pay: we have sentence about base salary range etc. Could include as prose before list.
We must not include duplicated lines.
Let's extract exact text.
About the role: "The Sr. Marketing Operations Manager role serves as a critical bridge between AWS Marketing Strategy, Operations, and Enablement (MSOE) to Senior Leaders throughout AWS Marketing. In this role, you will work closely across AWS Marketing to continuously improve processes, drive execution excellence, and deliver marketing results. You will be aligned to an AWS Marketing Team and have direct responsibility for annual planning, budget management, headcount management, rhythms of the business, ad hoc reporting, and enablement. This will be done through your ability to orchestrate the right people and teams to deliver against a defined request, project, or program. This is a data-driven role that has the opportunity to influence marketing programs and the type of data the team looks at to make strategic decisions. This role also has the ability to improve AWS Marketing performance by developing policies, programs, training, and processes to increase team productivity, return on investment, and execution quality."
That's the first paragraph.
Responsibilities: The paragraph after "Key job responsibilities". Let's capture exactly:
"Team player comfortable and motivated working in a collaborative environment with the ability to build relationships with key stakeholders at levels of seniority Establish structured collaboration mechanisms: Build and maintain interlocks with teams such as AWS Marketing, AWS Sales Operations, AWS Sales, and AWS MSOE —ensuring seamless information flow between teams whether joining existing processes or establishing new ones. Enable understanding of marketing strategy and measurement: Translate global marketing strategy into clear narratives explaining marketing measurement framework, measurement methodologies, investment allocation logic, and the rationale behind coverage decisions—providing content and materials that Marketing Leaders can use to ensure their audience whether sellers, partners, or other marketers understands what marketing does, how it's measured, and why. Deliver performance reporting and insights at various altitudes (geo, channel, or segment) and formats (written narrative, power point presentation, oral presentation) like : Deliver comprehensive performance commentary and actionable insights to the AWS Marketing Leaders that make marketing's full impact visible, including pipeline results, and key trends in activity."
There is some odd formatting: missing periods, but we keep as is.
We could split into sentences for readability but must preserve all info. We'll keep as a single
with the text.
Requirements (Basic Qualifications): list:
- 6+ years of professional non-internship marketing experience
- Experience using data and metrics to drive improvements
- Experience with Excel or Tableau (data manipulation, macros, charts and pivot tables)
- Experience driving direction and alignment with large cross-functional teams and agency partners
- Experience using data and metrics to measure impact and determine improvements
- Experience presenting metrics and progress to goal to senior leadership
- Experience in a business-to-business (B2B) environment, high-tech products/services
We'll output each as
- .
Qualifications (Preferred Qualifications): list:
- 5+ years of post Master's, full-time relevant industry (professional or military) experience
That's it.
Benefits: The 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."
We could make list items for each benefit: health insurance (with subdetails), 401(k) matching, paid time off, parental leave. The link maybe separate
. But we can include as part of list? Might be okay to keep as prose after list.
Pay: The pay info: "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 list of locations with ranges:
USA, CA, Mountain View - 130,000.00 - 185,000.00 USD annually
USA, CA, San Francisco - 130,000.00 - 185,000.00 USD annually
USA, NY, New York - 130,000.00 - 185,000.00 USD annually
USA, TX, Austin - 118,200.00 - 160,000.00 USD annually
USA, VA, Arlington - 118,200.00 - 160,000.00 USD annually
USA, WA, Seattle - 118,200.00 - 160,000.00 USD annually
We could make each as
- .
We should not include "Company - Amazon Web Services, Inc. Job ID: A10552605". That's metadata to drop.
Now construct HTML.
We'll have:
About the role
...
Responsibilities
...
Requirements
- ...
...
Qualifications
- ...
Benefits
- 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
- parental leave
Learn more about our benefits at https://amazon.jobs/en/benefits
Pay
for prose. Thus for each section we need to decide if content is list or prose. About the role: prose paragraph(s). Could be one
. Responsibilities: The responsibilities paragraph includes multiple sentences; could be a list? It's not explicitly bullet list but we could treat as prose. However instruction: use
- for any list of duties/requirements/benefits. Since it's not a list but prose, we can use
. But we could also split into bullet points? Better to keep as prose to preserve detail. Requirements: Basic Qualifications list items. Use
- .
Qualifications: Preferred Qualifications list items. Use
- .
Benefits: list of benefits items. Use
- .
Pay: list of location salary ranges. Could be a list.
We must not include boilerplate like "Learn more about our benefits at https://..." maybe we can keep as part of benefits? It's a link; but it's still substantive? It's a reference. Might be considered boilerplate? It's not EEO etc. It's a link to benefits page. Might be okay to keep as part of benefits paragraph. But we could incorporate as a
after list. Similarly for Pay: we have sentence about base salary range etc. Could include as prose before list. We must not include duplicated lines. Let's extract exact text. About the role: "The Sr. Marketing Operations Manager role serves as a critical bridge between AWS Marketing Strategy, Operations, and Enablement (MSOE) to Senior Leaders throughout AWS Marketing. In this role, you will work closely across AWS Marketing to continuously improve processes, drive execution excellence, and deliver marketing results. You will be aligned to an AWS Marketing Team and have direct responsibility for annual planning, budget management, headcount management, rhythms of the business, ad hoc reporting, and enablement. This will be done through your ability to orchestrate the right people and teams to deliver against a defined request, project, or program. This is a data-driven role that has the opportunity to influence marketing programs and the type of data the team looks at to make strategic decisions. This role also has the ability to improve AWS Marketing performance by developing policies, programs, training, and processes to increase team productivity, return on investment, and execution quality." That's the first paragraph. Responsibilities: The paragraph after "Key job responsibilities". Let's capture exactly: "Team player comfortable and motivated working in a collaborative environment with the ability to build relationships with key stakeholders at levels of seniority Establish structured collaboration mechanisms: Build and maintain interlocks with teams such as AWS Marketing, AWS Sales Operations, AWS Sales, and AWS MSOE —ensuring seamless information flow between teams whether joining existing processes or establishing new ones. Enable understanding of marketing strategy and measurement: Translate global marketing strategy into clear narratives explaining marketing measurement framework, measurement methodologies, investment allocation logic, and the rationale behind coverage decisions—providing content and materials that Marketing Leaders can use to ensure their audience whether sellers, partners, or other marketers understands what marketing does, how it's measured, and why. Deliver performance reporting and insights at various altitudes (geo, channel, or segment) and formats (written narrative, power point presentation, oral presentation) like : Deliver comprehensive performance commentary and actionable insights to the AWS Marketing Leaders that make marketing's full impact visible, including pipeline results, and key trends in activity." There is some odd formatting: missing periods, but we keep as is. We could split into sentences for readability but must preserve all info. We'll keep as a single
with the text. Requirements (Basic Qualifications): list: - 6+ years of professional non-internship marketing experience - Experience using data and metrics to drive improvements - Experience with Excel or Tableau (data manipulation, macros, charts and pivot tables) - Experience driving direction and alignment with large cross-functional teams and agency partners - Experience using data and metrics to measure impact and determine improvements - Experience presenting metrics and progress to goal to senior leadership - Experience in a business-to-business (B2B) environment, high-tech products/services We'll output each as
- .
Qualifications (Preferred Qualifications): list:
- 5+ years of post Master's, full-time relevant industry (professional or military) experience
That's it.
Benefits: The 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."
We could make list items for each benefit: health insurance (with subdetails), 401(k) matching, paid time off, parental leave. The link maybe separate
. But we can include as part of list? Might be okay to keep as prose after list. Pay: The pay info: "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 list of locations with ranges: USA, CA, Mountain View - 130,000.00 - 185,000.00 USD annually USA, CA, San Francisco - 130,000.00 - 185,000.00 USD annually USA, NY, New York - 130,000.00 - 185,000.00 USD annually USA, TX, Austin - 118,200.00 - 160,000.00 USD annually USA, VA, Arlington - 118,200.00 - 160,000.00 USD annually USA, WA, Seattle - 118,200.00 - 160,000.00 USD annually We could make each as
- .
We should not include "Company - Amazon Web Services, Inc. Job ID: A10552605". That's metadata to drop.
Now construct HTML.
We'll have:
About the role
...
Responsibilities
...
Requirements
- ... ...
Qualifications
- ...
Benefits
- 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
- parental leave
Learn more about our benefits at https://amazon.jobs/en/benefits
Pay
- .
Pay: list of location salary ranges. Could be a list.
We must not include boilerplate like "Learn more about our benefits at https://..." maybe we can keep as part of benefits? It's a link; but it's still substantive? It's a reference. Might be considered boilerplate? It's not EEO etc. It's a link to benefits page. Might be okay to keep as part of benefits paragraph. But we could incorporate as a
- .
Benefits: list of benefits items. Use
- .
Qualifications: Preferred Qualifications list items. Use