Senior Product Manager, eCommerce
AutoTune · Greater Boston · 1 mo ago
RemoteRemoteMarketingFull-time
We need to output HTML fragment with sections: About the role? The posting includes "Location: 100% Remote..." then "Position We are seeking..." then responsibilities, preferred experience, About Us, Compensation & Benefits. We need headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use for each heading. Only include sections that have real specific content. We have location info (remote) - could be part of About the role? Probably include a short paragraph about location. The "Position" paragraph is about role description; could be About the role.
Responsibilities: we have a big block.
Preferred Experience And Qualifications: includes qualifications, experience, skills. Could split into Requirements/Qualifications/Skills but we can combine into one section maybe "Requirements". The instruction: prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements, About Us, Compensation & Benefits. Pay: they mention compensation ranges based on experience, but not specific numbers. That's vague; we should not create Pay section if only generic "based on candidate experience" and "Compensation ranges are established using national benchmarking data". That's still somewhat specific? It says compensation ranges are established using national benchmarking data and apply across all geographic locations within the United States. That's still generic but it's a statement about compensation. The rule: 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. The posting does state compensation: "Full compensation packages are based on candidate experience. Compensation ranges are established using national benchmarking data and apply across all geographic locations within the United States." That's not a specific number but it's stating that compensation ranges exist. Is that considered filler? It's not a specific number but it's still some info. The rule says avoid filler like "commensurate with experience". That phrase is similar to "based on candidate experience". Might be considered filler. Safer to not include Pay section. Benefits: they list benefits in detail, so we can include Benefits section. Schedule: they mention flexible working hours, but not specific schedule. Could be considered schedule info. The rule: never create Schedule section unless posting actually states them. It does state "Flexible working hours". That's a schedule detail. So we could include Schedule section with that line. However they also mention "Unlimited PTO", "Paid Federal holidays", etc. Those are benefits. So schedule could be just flexible working hours.
We need to avoid duplication. Also need to remove boilerplate like EEO etc.
We need to preserve all substantive information. So we need to include location, role description, responsibilities, preferred experience/qualifications, about us, compensation & benefits (maybe as Benefits), schedule (flexible working hours). Also maybe include "About Us" as a section? Not in the list of allowed headings but we could treat as About the role? Actually About Us is separate; but allowed headings list does not include About Us. However we could incorporate About Us into About the role? Might be better to have a section "About the company" but not allowed. The instruction: use
for each heading. Only include sections that have real specific content. We have location info (remote) - could be part of About the role? Probably include a short paragraph about location. The "Position" paragraph is about role description; could be About the role.
Responsibilities: we have a big block.
Preferred Experience And Qualifications: includes qualifications, experience, skills. Could split into Requirements/Qualifications/Skills but we can combine into one section maybe "Requirements". The instruction: prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements, About Us, Compensation & Benefits. Pay: they mention compensation ranges based on experience, but not specific numbers. That's vague; we should not create Pay section if only generic "based on candidate experience" and "Compensation ranges are established using national benchmarking data". That's still somewhat specific? It says compensation ranges are established using national benchmarking data and apply across all geographic locations within the United States. That's still generic but it's a statement about compensation. The rule: 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. The posting does state compensation: "Full compensation packages are based on candidate experience. Compensation ranges are established using national benchmarking data and apply across all geographic locations within the United States." That's not a specific number but it's stating that compensation ranges exist. Is that considered filler? It's not a specific number but it's still some info. The rule says avoid filler like "commensurate with experience". That phrase is similar to "based on candidate experience". Might be considered filler. Safer to not include Pay section. Benefits: they list benefits in detail, so we can include Benefits section. Schedule: they mention flexible working hours, but not specific schedule. Could be considered schedule info. The rule: never create Schedule section unless posting actually states them. It does state "Flexible working hours". That's a schedule detail. So we could include Schedule section with that line. However they also mention "Unlimited PTO", "Paid Federal holidays", etc. Those are benefits. So schedule could be just flexible working hours.
We need to avoid duplication. Also need to remove boilerplate like EEO etc.
We need to preserve all substantive information. So we need to include location, role description, responsibilities, preferred experience/qualifications, about us, compensation & benefits (maybe as Benefits), schedule (flexible working hours). Also maybe include "About Us" as a section? Not in the list of allowed headings but we could treat as About the role? Actually About Us is separate; but allowed headings list does not include About Us. However we could incorporate About Us into About the role? Might be better to have a section "About the company" but not allowed. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we could add other headings if needed, but better to stick to those. Could treat About Us as part of About the role? Might be okay to include a separate heading like "About the company" but not in list; risk. Safer to incorporate About Us into About the role or maybe as a separate section with heading "About the company" but risk of being considered not following instruction. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. Probably okay to add other headings if needed, but better to follow examples. We could put About Us under "About the role" as a paragraph describing company. That might be okay.
Thus sections: About the role (includes location, role description, about us), Responsibilities, Requirements (combines preferred experience and qualifications), Benefits, Schedule.
We need to use - for any list of duties/requirements/benefits. So responsibilities list should be
- . Also requirements list maybe bullet list.
We need to preserve all substantive information: need to include each bullet point from responsibilities, each bullet from preferred experience, each benefit item, schedule item.
Let's extract.
Location: "Location: 100% Remote. We hire anywhere in the U.S."
Role description paragraph: "We are seeking a Staff Product Manager to lead the strategic direction, prioritization, and business outcomes for Antares’ eCommerce platform, customer-facing web experience and associated cloud services. Reporting to the CTO, this role translates company strategy into a clear product roadmap across Antares’ eCommerce and cloud ecosystem. You will define the “what” and “why,” optimize investments, align stakeholders, and partner closely with Engineering, Marketing, Data, Design and IT to deliver measurable business impact for customers, partners, and internal teams."
About Us paragraph: "For nearly 30 years, Antares Audio Technologies has defined the sound of modern music. We created AutoTune, the most iconic vocal processing software in the industry, used on countless hit records and by artists ranging from bedroom producers to Grammy winners. Our mission is to empower serious music makers with tools that provide complete creative control over their vocal performances. We're a team of musicians, engineers, and product builders who obsess over craft and speed. We believe in leading with innovation, unleashing the next era of music technology, and building software that shapes pop culture."
Responsibilities bullet points: need to parse.
From responsibilities section:
- Strategic roadmap ownership & business alignment
- Define and maintain a prioritized capability roadmap that connects business strategy to execution, sequencing, and investment tradeoffs.
- Develop a clear, data-informed point of view on platform direction, business capabilities, and technology priorities; negotiate directly with stakeholders to drive alignment and optimize investment allocation.
- Establish and track OKRs that ladder up to company-level priorities.
- Measure and report on outcomes from platform investments, such as self-service adoption, checkout performance, experimentation velocity, Core Web Vitals, SEO performance, and operational efficiency.
- Evaluate vendor roadmaps and platform capabilities, representing Antares’ business needs to identify opportunities for unlocking growth and improving customer experience.
- Backlog & prioritization governance
- Triage and prioritize a varied cross-functional backlog spanning checkout, payments, growth initiatives, content workflows, data integrations, partner needs, security, infrastructure, and technical debt.
- Serve as Product Owner for the engineering team, translating business priorities into a clear, sequenced backlog and partnering with Engineering to define scope, acceptance criteria, sprint priorities, and release tradeoffs.
- Use clear business-value criteria to explain prioritization decisions and help stakeholders understand tradeoffs.
- Represent the value and risk of foundational work, including security, compliance, infrastructure hardening, disaster recovery, and technical debt remediation.
- Partner with Engineering, Program Management, IT, Security, and executive stakeholders to sequence work based on business impact, technical complexity, and organizational capacity.
- Surface priority conflicts, delivery risks, scope changes, and tradeoffs early, with clear recommendations for resolution.
- Cross-Functional Product Leadership
- Collaborate with Engineering and technical leadership with enough fluency in modern cloud-based systems to make product tradeoff decisions.
- Communicate complex technical and business tradeoffs clearly to executive, technical, and non-technical audiences.
- Drive adoption of new platform capabilities by ensuring they meet stakeholder needs and create measurable business value.
- Create visibility into commitments, dependencies, risks, and decisions across cross-functional initiatives.
- AI-Native Delivery
- Bring a genuine growth mindset to new tools, platforms, and ways of working, and incorporate state-of-the-art techniques on the job.
- Adopt AI-native delivery practices as part of day-to-day product work, including requirements review, roadmap analysis, research synthesis, and prototyping.
We need to output each as
- . Could group under headings? Not required; just list.
Preferred Experience And Qualifications bullet points:
- 7+ years of product management or product leadership experience, with a demonstrated track record owning strategic roadmaps for eCommerce, web, SaaS, licensing, or cloud-services platforms.
- Demonstrated ability to independently form and negotiate a data-backed point of view with senior stakeholders.
- Strong bias toward action, self-directed ownership, and disciplined follow-through on goals, decisions, and dependencies.
- Experience setting business goals and a track record of delivering measurable results.
- Experience managing SaaS vendor relationships, such as CMS, payments, eCommerce, experimentation, analytics, or license-management platforms.
- Experience with payment platforms (e.g., FastSpring, Stripe) and eCommerce platforms (e.g., Shopify, WooCommerce, Builder.io).
- Working knowledge of modern web and cloud architecture, including headless CMS, server-rendered JavaScript frameworks, APIs, data integrations, and major cloud providers.
- Ability to balance growth initiatives with security, compliance, reliability, and technical debt priorities.
- Excellent communication skills, with the ability to translate complex technical and business tradeoffs into clear priorities.
- Practical fluency with agentic AI tools across planning, communication, analysis, and prototyping.
- Comfort operating in ambiguity and taking ownership of outcomes end-to-end.
- Bachelor’s degree or equivalent experience.
Benefits bullet points:
- Medical, Dental and Vision with up to 100% coverage for you and your family
- Unlimited PTO
- Paid Federal holidays, including a week off for everyone at the end of the year
- Annual bonus plan
- Stipend for office and learning & development expenses
- Flexible working hours
- Paid Parental Leave
- 4% 401k match after 6 months
- Free AutoTune software!
Schedule: we have "Flexible working hours" already listed as benefit; but schedule section could include that. However we already have flexible working hours in benefits; maybe we should not duplicate. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we put flexible working hours under Benefits, that's fine. Then Schedule section may be redundant. Could we omit Schedule section because flexible working hours already captured? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state flexible working hours, which is schedule info. But we already have it under Benefits; but we could still have a Schedule section with that item. However that would duplicate content. Duplication is to be avoided: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". So we should not duplicate. So we should place flexible working hours either under Benefits or Schedule, not both. Since Benefits already has many items, we could keep flexible working hours under Benefits and not create Schedule section. That satisfies not duplicating.
Thus sections: About the role, Responsibilities, Requirements, Benefits.
We need to include location and role description and about us in About the role.
Let's craft HTML.
Start with
About the role
then Location: 100% Remote. We hire anywhere in the U.S.
then We are seeking a Staff Product Manager to lead the strategic direction, prioritization, and business outcomes for Antares’ eCommerce platform, customer-facing web experience and associated cloud services. Reporting to the CTO, this role translates company strategy into a clear product roadmap across Antares’ eCommerce and cloud ecosystem. You will define the “what” and “why,” optimize investments, align stakeholders, and partner closely with Engineering, Marketing, Data, Design and IT to deliver measurable business impact for customers, partners, and internal teams.
then <
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. Probably okay to add other headings if needed, but better to follow examples. We could put About Us under "About the role" as a paragraph describing company. That might be okay.
Thus sections: About the role (includes location, role description, about us), Responsibilities, Requirements (combines preferred experience and qualifications), Benefits, Schedule.
We need to use - for any list of duties/requirements/benefits. So responsibilities list should be
- . Also requirements list maybe bullet list.
We need to preserve all substantive information: need to include each bullet point from responsibilities, each bullet from preferred experience, each benefit item, schedule item.
Let's extract.
Location: "Location: 100% Remote. We hire anywhere in the U.S."
Role description paragraph: "We are seeking a Staff Product Manager to lead the strategic direction, prioritization, and business outcomes for Antares’ eCommerce platform, customer-facing web experience and associated cloud services. Reporting to the CTO, this role translates company strategy into a clear product roadmap across Antares’ eCommerce and cloud ecosystem. You will define the “what” and “why,” optimize investments, align stakeholders, and partner closely with Engineering, Marketing, Data, Design and IT to deliver measurable business impact for customers, partners, and internal teams."
About Us paragraph: "For nearly 30 years, Antares Audio Technologies has defined the sound of modern music. We created AutoTune, the most iconic vocal processing software in the industry, used on countless hit records and by artists ranging from bedroom producers to Grammy winners. Our mission is to empower serious music makers with tools that provide complete creative control over their vocal performances. We're a team of musicians, engineers, and product builders who obsess over craft and speed. We believe in leading with innovation, unleashing the next era of music technology, and building software that shapes pop culture."
Responsibilities bullet points: need to parse.
From responsibilities section:
- Strategic roadmap ownership & business alignment
- Define and maintain a prioritized capability roadmap that connects business strategy to execution, sequencing, and investment tradeoffs.
- Develop a clear, data-informed point of view on platform direction, business capabilities, and technology priorities; negotiate directly with stakeholders to drive alignment and optimize investment allocation.
- Establish and track OKRs that ladder up to company-level priorities.
- Measure and report on outcomes from platform investments, such as self-service adoption, checkout performance, experimentation velocity, Core Web Vitals, SEO performance, and operational efficiency.
- Evaluate vendor roadmaps and platform capabilities, representing Antares’ business needs to identify opportunities for unlocking growth and improving customer experience.
- Backlog & prioritization governance
- Triage and prioritize a varied cross-functional backlog spanning checkout, payments, growth initiatives, content workflows, data integrations, partner needs, security, infrastructure, and technical debt.
- Serve as Product Owner for the engineering team, translating business priorities into a clear, sequenced backlog and partnering with Engineering to define scope, acceptance criteria, sprint priorities, and release tradeoffs.
- Use clear business-value criteria to explain prioritization decisions and help stakeholders understand tradeoffs.
- Represent the value and risk of foundational work, including security, compliance, infrastructure hardening, disaster recovery, and technical debt remediation.
- Partner with Engineering, Program Management, IT, Security, and executive stakeholders to sequence work based on business impact, technical complexity, and organizational capacity.
- Surface priority conflicts, delivery risks, scope changes, and tradeoffs early, with clear recommendations for resolution.
- Cross-Functional Product Leadership
- Collaborate with Engineering and technical leadership with enough fluency in modern cloud-based systems to make product tradeoff decisions.
- Communicate complex technical and business tradeoffs clearly to executive, technical, and non-technical audiences.
- Drive adoption of new platform capabilities by ensuring they meet stakeholder needs and create measurable business value.
- Create visibility into commitments, dependencies, risks, and decisions across cross-functional initiatives.
- AI-Native Delivery
- Bring a genuine growth mindset to new tools, platforms, and ways of working, and incorporate state-of-the-art techniques on the job.
- Adopt AI-native delivery practices as part of day-to-day product work, including requirements review, roadmap analysis, research synthesis, and prototyping.
We need to output each as
- . Could group under headings? Not required; just list.
Preferred Experience And Qualifications bullet points:
- 7+ years of product management or product leadership experience, with a demonstrated track record owning strategic roadmaps for eCommerce, web, SaaS, licensing, or cloud-services platforms.
- Demonstrated ability to independently form and negotiate a data-backed point of view with senior stakeholders.
- Strong bias toward action, self-directed ownership, and disciplined follow-through on goals, decisions, and dependencies.
- Experience setting business goals and a track record of delivering measurable results.
- Experience managing SaaS vendor relationships, such as CMS, payments, eCommerce, experimentation, analytics, or license-management platforms.
- Experience with payment platforms (e.g., FastSpring, Stripe) and eCommerce platforms (e.g., Shopify, WooCommerce, Builder.io).
- Working knowledge of modern web and cloud architecture, including headless CMS, server-rendered JavaScript frameworks, APIs, data integrations, and major cloud providers.
- Ability to balance growth initiatives with security, compliance, reliability, and technical debt priorities.
- Excellent communication skills, with the ability to translate complex technical and business tradeoffs into clear priorities.
- Practical fluency with agentic AI tools across planning, communication, analysis, and prototyping.
- Comfort operating in ambiguity and taking ownership of outcomes end-to-end.
- Bachelor’s degree or equivalent experience.
Benefits bullet points:
- Medical, Dental and Vision with up to 100% coverage for you and your family
- Unlimited PTO
- Paid Federal holidays, including a week off for everyone at the end of the year
- Annual bonus plan
- Stipend for office and learning & development expenses
- Flexible working hours
- Paid Parental Leave
- 4% 401k match after 6 months
- Free AutoTune software!
Schedule: we have "Flexible working hours" already listed as benefit; but schedule section could include that. However we already have flexible working hours in benefits; maybe we should not duplicate. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we put flexible working hours under Benefits, that's fine. Then Schedule section may be redundant. Could we omit Schedule section because flexible working hours already captured? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state flexible working hours, which is schedule info. But we already have it under Benefits; but we could still have a Schedule section with that item. However that would duplicate content. Duplication is to be avoided: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". So we should not duplicate. So we should place flexible working hours either under Benefits or Schedule, not both. Since Benefits already has many items, we could keep flexible working hours under Benefits and not create Schedule section. That satisfies not duplicating.
Thus sections: About the role, Responsibilities, Requirements, Benefits.
We need to include location and role description and about us in About the role.
Let's craft HTML.
Start with
About the role
then Location: 100% Remote. We hire anywhere in the U.S.
then We are seeking a Staff Product Manager to lead the strategic direction, prioritization, and business outcomes for Antares’ eCommerce platform, customer-facing web experience and associated cloud services. Reporting to the CTO, this role translates company strategy into a clear product roadmap across Antares’ eCommerce and cloud ecosystem. You will define the “what” and “why,” optimize investments, align stakeholders, and partner closely with Engineering, Marketing, Data, Design and IT to deliver measurable business impact for customers, partners, and internal teams.
then <
- . Also requirements list maybe bullet list. We need to preserve all substantive information: need to include each bullet point from responsibilities, each bullet from preferred experience, each benefit item, schedule item. Let's extract. Location: "Location: 100% Remote. We hire anywhere in the U.S." Role description paragraph: "We are seeking a Staff Product Manager to lead the strategic direction, prioritization, and business outcomes for Antares’ eCommerce platform, customer-facing web experience and associated cloud services. Reporting to the CTO, this role translates company strategy into a clear product roadmap across Antares’ eCommerce and cloud ecosystem. You will define the “what” and “why,” optimize investments, align stakeholders, and partner closely with Engineering, Marketing, Data, Design and IT to deliver measurable business impact for customers, partners, and internal teams." About Us paragraph: "For nearly 30 years, Antares Audio Technologies has defined the sound of modern music. We created AutoTune, the most iconic vocal processing software in the industry, used on countless hit records and by artists ranging from bedroom producers to Grammy winners. Our mission is to empower serious music makers with tools that provide complete creative control over their vocal performances. We're a team of musicians, engineers, and product builders who obsess over craft and speed. We believe in leading with innovation, unleashing the next era of music technology, and building software that shapes pop culture." Responsibilities bullet points: need to parse. From responsibilities section: - Strategic roadmap ownership & business alignment - Define and maintain a prioritized capability roadmap that connects business strategy to execution, sequencing, and investment tradeoffs. - Develop a clear, data-informed point of view on platform direction, business capabilities, and technology priorities; negotiate directly with stakeholders to drive alignment and optimize investment allocation. - Establish and track OKRs that ladder up to company-level priorities. - Measure and report on outcomes from platform investments, such as self-service adoption, checkout performance, experimentation velocity, Core Web Vitals, SEO performance, and operational efficiency. - Evaluate vendor roadmaps and platform capabilities, representing Antares’ business needs to identify opportunities for unlocking growth and improving customer experience. - Backlog & prioritization governance - Triage and prioritize a varied cross-functional backlog spanning checkout, payments, growth initiatives, content workflows, data integrations, partner needs, security, infrastructure, and technical debt. - Serve as Product Owner for the engineering team, translating business priorities into a clear, sequenced backlog and partnering with Engineering to define scope, acceptance criteria, sprint priorities, and release tradeoffs. - Use clear business-value criteria to explain prioritization decisions and help stakeholders understand tradeoffs. - Represent the value and risk of foundational work, including security, compliance, infrastructure hardening, disaster recovery, and technical debt remediation. - Partner with Engineering, Program Management, IT, Security, and executive stakeholders to sequence work based on business impact, technical complexity, and organizational capacity. - Surface priority conflicts, delivery risks, scope changes, and tradeoffs early, with clear recommendations for resolution. - Cross-Functional Product Leadership - Collaborate with Engineering and technical leadership with enough fluency in modern cloud-based systems to make product tradeoff decisions. - Communicate complex technical and business tradeoffs clearly to executive, technical, and non-technical audiences. - Drive adoption of new platform capabilities by ensuring they meet stakeholder needs and create measurable business value. - Create visibility into commitments, dependencies, risks, and decisions across cross-functional initiatives. - AI-Native Delivery - Bring a genuine growth mindset to new tools, platforms, and ways of working, and incorporate state-of-the-art techniques on the job. - Adopt AI-native delivery practices as part of day-to-day product work, including requirements review, roadmap analysis, research synthesis, and prototyping. We need to output each as
- . Could group under headings? Not required; just list.
Preferred Experience And Qualifications bullet points:
- 7+ years of product management or product leadership experience, with a demonstrated track record owning strategic roadmaps for eCommerce, web, SaaS, licensing, or cloud-services platforms.
- Demonstrated ability to independently form and negotiate a data-backed point of view with senior stakeholders.
- Strong bias toward action, self-directed ownership, and disciplined follow-through on goals, decisions, and dependencies.
- Experience setting business goals and a track record of delivering measurable results.
- Experience managing SaaS vendor relationships, such as CMS, payments, eCommerce, experimentation, analytics, or license-management platforms.
- Experience with payment platforms (e.g., FastSpring, Stripe) and eCommerce platforms (e.g., Shopify, WooCommerce, Builder.io).
- Working knowledge of modern web and cloud architecture, including headless CMS, server-rendered JavaScript frameworks, APIs, data integrations, and major cloud providers.
- Ability to balance growth initiatives with security, compliance, reliability, and technical debt priorities.
- Excellent communication skills, with the ability to translate complex technical and business tradeoffs into clear priorities.
- Practical fluency with agentic AI tools across planning, communication, analysis, and prototyping.
- Comfort operating in ambiguity and taking ownership of outcomes end-to-end.
- Bachelor’s degree or equivalent experience.
Benefits bullet points:
- Medical, Dental and Vision with up to 100% coverage for you and your family
- Unlimited PTO
- Paid Federal holidays, including a week off for everyone at the end of the year
- Annual bonus plan
- Stipend for office and learning & development expenses
- Flexible working hours
- Paid Parental Leave
- 4% 401k match after 6 months
- Free AutoTune software!
Schedule: we have "Flexible working hours" already listed as benefit; but schedule section could include that. However we already have flexible working hours in benefits; maybe we should not duplicate. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we put flexible working hours under Benefits, that's fine. Then Schedule section may be redundant. Could we omit Schedule section because flexible working hours already captured? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state flexible working hours, which is schedule info. But we already have it under Benefits; but we could still have a Schedule section with that item. However that would duplicate content. Duplication is to be avoided: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". So we should not duplicate. So we should place flexible working hours either under Benefits or Schedule, not both. Since Benefits already has many items, we could keep flexible working hours under Benefits and not create Schedule section. That satisfies not duplicating.
Thus sections: About the role, Responsibilities, Requirements, Benefits.
We need to include location and role description and about us in About the role.
Let's craft HTML.
Start with
About the role
thenLocation: 100% Remote. We hire anywhere in the U.S.
thenWe are seeking a Staff Product Manager to lead the strategic direction, prioritization, and business outcomes for Antares’ eCommerce platform, customer-facing web experience and associated cloud services. Reporting to the CTO, this role translates company strategy into a clear product roadmap across Antares’ eCommerce and cloud ecosystem. You will define the “what” and “why,” optimize investments, align stakeholders, and partner closely with Engineering, Marketing, Data, Design and IT to deliver measurable business impact for customers, partners, and internal teams.
then <