Product Marketing Manager
for each heading. Use - for lists. Use
for prose. Do not repeat job title. Remove boilerplate: EEO, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. Keep substantive info.
We need to parse the posting.
First, there is an "About Torus" paragraph describing company. That is not a section heading per instructions; we can include as prose maybe under a generic "About the company"? Not required. The instructions say include a section only when posting has real, specific content for it. They list possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should include sections for those that have content.
We have:
- About The Role: description of role. So we need
About the role
then prose.
- Responsibilities: list of responsibilities. So Responsibilities
then - items.
- Required Experience: that's qualifications/requirements. So we can put under
Requirements
(or Qualifications). Use list.
- Preferred Experience: could be also under Requirements or Qualifications, maybe separate but we can combine? The instruction: prefer few substantive sections over many thin ones. Could combine Required and Preferred under Requirements. But we need to preserve all info. Could have a single Requirements section with sublists? But we must use - for any list. Could have two lists: Required Experience and Preferred Experience. Could put headings inside? Not allowed; only section headings are the specified ones. Could embed bold text? Not specified. Safer to keep separate sections: Requirements and Qualifications? But they said use headings like Requirements, Qualifications. Could treat Required Experience as Requirements, Preferred Experience as Qualifications. That seems reasonable.
- Skills: The posting includes "Skilled at translating technical features into benefit-driven messaging." etc. That's under Required Experience bullet. Could be part of Skills section. We could create a Skills section listing those skills.
- Benefits: The posting includes "Our Perks & Benefits" with details. So we need Benefits section.
- Pay: The posting includes "Compensation $165,000 - 190,000". So Pay section.
- Schedule: The posting includes "Schedule Full-Time, Salaried". So Schedule section.
Also location + travel: maybe not needed as separate heading; could be included in a short paragraph under About the role? But we have no heading for location. Could embed in a paragraph under About the role or maybe under a generic "About the role"? The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Location+travel is minor metadata; we could include as a short
after About the role or after Responsibilities? Probably after About the role.
We must remove boilerplate: EEO, E-Verify, etc. Also remove "Background Check", "Work Authorization", "Physical Requirements" maybe? Those are substantive? They are requirements but maybe considered boilerplate? They are specific to job; but they are not typical sections; we could incorporate them into Requirements or Qualifications as list items. However they are quite detailed; we could keep them under Requirements as list items.
But we must not include sections like "Physical Requirements" as heading; we can embed as list items under Requirements.
Similarly "Background Check" and "Work Authorization" could be list items under Requirements.
We must preserve all substantive information; do not invent or summarize away detail.
Thus we need to extract all bullet points.
Let's parse the posting:
About Torus: paragraph.
About The Role: paragraph: "Customers evaluating Torus need to understand how our systems provide benefits for their facilities; from hardware through software to ongoing support. As a Product Marketing Manager, you’ll work across product, engineering, sales, and manufacturing teams to make sure our customers understand our products. You’ll develop personas and segmentation, write MRDs and PRDs, support product launches, and help build sales enablement assets that translate technical complexity into benefit-driven positioning. Your goal is to help Torus fit our products in an ever-changing market."
Responsibilities: list (looks like a paragraph with semicolons). Actually it's: "Responsible for supporting cross-functional teams from product research and development to launch to installation and ongoing support, throughout the entire product lifecycle.Work across product, engineering, sales, manufacturing, and marketing to build and scale products.Lead persona development and customer segmentation across utility, C&I, data center, and government/defense markets.Drive the creation of market requirements documents ( MRD), and product requirements documents (PRD) for new and existing products.Support product launches end-to-end, including collateral, internal training, and go-to-market execution.Assist market intelligence team on packaging, pricing, feature prioritization, and messaging.Enable the sales and design teams with product data sheets."
We need to split into list items. Each sentence seems a responsibility. We'll create
- for each.
Required Experience: bullet list:
- 7+ years in product marketing, ideally in complex B2B tech—energy, infrastructure, or hardware/software hybrids.
- Experience writing or managing MRDs and PRDs with cross-functional teams.
- Strong grasp of go-to-market mechanics, including personas, ideal customer profiles, TAM/SAM/SOM, and pricing models.
- Familiarity with energy storage systems, grid interconnections, or electrical and mechanical systems.
- Skilled at translating technical features into benefit-driven messaging.
- Experience creating sales enablement assets, product collateral, and executive-ready positioning docs.
Preferred Experience:
- Experience with utilities, grid infrastructure, or energy storage (FESS, BESS, microgrids).
- Knowledge of regulatory frameworks: IEEE, UL, NERC, FERC, CAISO, etc.
- Worked in or marketed to utilities, commercial & industrial, data centers, or government/ defense sectors.
- Led multiple product launches and evolved messaging across product lifecycles.
- Background collaborating with brand, comms, and external creative partners.
- Bonus if you’ve marketed a vertically integrated product stack (hardware + firmware + software).
Additional Details:
- Background Check: All candidates are subject to a background check.
- Location + Travel: The role is based in Utah including hybrid remote with work based in your home office and our Salt Lake City/South Salt Lake warehouses, as needed.
- Schedule: Full-Time, Salaried
- Compensation: $165,000 - 190,000 (Note: We have the flexibility to hire at different levels, which may impact the corresponding pay range.)
- Work Authorization: Applicants must already have the legal authorization to work in the US without requiring any employer sponsorship.
- Physical Requirements: list of items.
- Our Perks & Benefits: details.
We need to include Benefits section with details.
We need to include Pay section with compensation range.
Schedule section with Full-Time, Salaried.
We might also include Location as a short paragraph under About the role or after? Since no heading for location, we can put a short
after About the role.
We must not include sections like "Background Check" or "Work Authorization" as headings; we can embed them as list items under Requirements or Qualifications.
Physical Requirements also as list items.
Thus we will have sections:
About the role
...
Responsibilities
...
Requirements
...
(includes Required Experience + Background Check + Work Authorization + Physical Requirements)
Qualifications
...
(Preferred Experience)
Skills
...
(maybe extract skills like translating technical features, creating sales enablement assets, etc. But those are already in Requirements. Could combine but we need a Skills section only if there is specific content. The posting includes "Skilled at translating technical features into benefit-driven messaging." and "Experience creating sales enablement assets, product collateral, and executive-ready positioning docs." Those are skills. We could put them under Skills. However they'd duplicate with Requirements. To avoid duplication, maybe we treat Requirements as the list of required experience, and Skills as a separate list of skills (like translating technical features, creating sales enablement assets, etc.). But the posting also includes "Strong grasp of go-to-market mechanics..." which is also a skill. Might be overlapping.
Given instruction: prefer few substantive sections over many thin ones. So maybe we combine Required Experience and Skills into Requirements section. And Preferred Experience into Qualifications. That seems reasonable.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We need to ensure we include all substantive info.
Let's extract details for each.
About the role paragraph: as above.
Responsibilities list items:
1. Responsible for supporting cross-functional teams from product research and development to launch to installation and ongoing support, throughout the entire product lifecycle.
2. Work across product, engineering, sales, manufacturing, and marketing to build and scale products.
3. Lead persona development and customer segmentation across utility, C&I, data center, and government/defense markets.
4. Drive the creation of market requirements documents (MRD), and product requirements documents (PRD) for new and existing products.
5. Support product launches end-to-end, including collateral, internal training, and go-to-market execution.
6. Assist market intelligence team on packaging, pricing, feature prioritization, and messaging.
7. Enable the sales and design teams with product data sheets.
Check for any missing: The original had "Work across product, engineering, sales, manufacturing, and marketing to build and scale products." yes.
Now Requirements list items (Required Experience + Background Check + Work Authorization + Physical Requirements):
Required Experience items:
- 7+ years in product marketing, ideally in complex B2B tech—energy, infrastructure, or hardware/software hybrids.
- Experience writing or managing MRDs and PRDs with cross-functional teams.
- Strong grasp of go-to-market mechanics, including personas, ideal customer profiles, TAM/SAM/SOM, and pricing models.
- Familiarity with energy storage systems, grid interconnections, or electrical and mechanical systems.
- Skilled at translating technical features into benefit-driven messaging.
- Experience creating sales enablement assets, product collateral, and executive-ready positioning docs.
Background Check: All candidates are subject to a background check.
Work Authorization: Applicants must already have the legal authorization to work in the US without requiring any employer sponsorship.
Physical Requirements list:
- Regularly operates a computer and other peripheral office equipment such as a printer or mouse.
- Ability to communicate information so others can understand.
- Must be able to exchange accurate information in these situations.
- Must report to work reliably and with the ability to use full and unimpaired skills and judgment to safely execute your job.
- Proficiency in reading, writing, and speaking English required.
- When on the production floor, required to don personal protective equipment to include, but not limited to ear protection, gloves, eye protection and/or safety helmet.
- When on the production floor, ability to observe, detect and respond to audible and visual machine malfunction warnings.
We should keep each as separate - .
Now Qualifications (Preferred Experience) list:
- Experience with utilities, grid infrastructure, or energy storage (FESS, BESS, microgrids).
- Knowledge of regulatory frameworks: IEEE, UL, NERC, FERC, CAISO, etc.
- Worked in or marketed to utilities, commercial & industrial, data centers, or government/ defense sectors.
- Led multiple product launches and evolved messaging across product lifecycles.
- Background collaborating with brand, comms, and external creative partners.
- Bonus if you’ve marketed a vertically integrated product stack (hardware + firmware + software).
Now Benefits section: extract from "Our Perks & Benefits":
- Benefits eligibility is based on employment status.
- Financial Employee Re
for prose. Do not repeat job title. Remove boilerplate: EEO, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. Keep substantive info. We need to parse the posting. First, there is an "About Torus" paragraph describing company. That is not a section heading per instructions; we can include as prose maybe under a generic "About the company"? Not required. The instructions say include a section only when posting has real, specific content for it. They list possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should include sections for those that have content. We have: - About The Role: description of role. So we need
About the role
then prose. - Responsibilities: list of responsibilities. SoResponsibilities
then- items.
- Required Experience: that's qualifications/requirements. So we can put under
Requirements
(or Qualifications). Use list. - Preferred Experience: could be also under Requirements or Qualifications, maybe separate but we can combine? The instruction: prefer few substantive sections over many thin ones. Could combine Required and Preferred under Requirements. But we need to preserve all info. Could have a single Requirements section with sublists? But we must use- for any list. Could have two lists: Required Experience and Preferred Experience. Could put headings inside? Not allowed; only section headings are the specified ones. Could embed bold text? Not specified. Safer to keep separate sections: Requirements and Qualifications? But they said use headings like Requirements, Qualifications. Could treat Required Experience as Requirements, Preferred Experience as Qualifications. That seems reasonable.
- Skills: The posting includes "Skilled at translating technical features into benefit-driven messaging." etc. That's under Required Experience bullet. Could be part of Skills section. We could create a Skills section listing those skills.
- Benefits: The posting includes "Our Perks & Benefits" with details. So we need Benefits section.
- Pay: The posting includes "Compensation $165,000 - 190,000". So Pay section.
- Schedule: The posting includes "Schedule Full-Time, Salaried". So Schedule section.
Also location + travel: maybe not needed as separate heading; could be included in a short paragraph under About the role? But we have no heading for location. Could embed in a paragraph under About the role or maybe under a generic "About the role"? The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Location+travel is minor metadata; we could include as a short
after About the role or after Responsibilities? Probably after About the role. We must remove boilerplate: EEO, E-Verify, etc. Also remove "Background Check", "Work Authorization", "Physical Requirements" maybe? Those are substantive? They are requirements but maybe considered boilerplate? They are specific to job; but they are not typical sections; we could incorporate them into Requirements or Qualifications as list items. However they are quite detailed; we could keep them under Requirements as list items. But we must not include sections like "Physical Requirements" as heading; we can embed as list items under Requirements. Similarly "Background Check" and "Work Authorization" could be list items under Requirements. We must preserve all substantive information; do not invent or summarize away detail. Thus we need to extract all bullet points. Let's parse the posting: About Torus: paragraph. About The Role: paragraph: "Customers evaluating Torus need to understand how our systems provide benefits for their facilities; from hardware through software to ongoing support. As a Product Marketing Manager, you’ll work across product, engineering, sales, and manufacturing teams to make sure our customers understand our products. You’ll develop personas and segmentation, write MRDs and PRDs, support product launches, and help build sales enablement assets that translate technical complexity into benefit-driven positioning. Your goal is to help Torus fit our products in an ever-changing market." Responsibilities: list (looks like a paragraph with semicolons). Actually it's: "Responsible for supporting cross-functional teams from product research and development to launch to installation and ongoing support, throughout the entire product lifecycle.Work across product, engineering, sales, manufacturing, and marketing to build and scale products.Lead persona development and customer segmentation across utility, C&I, data center, and government/defense markets.Drive the creation of market requirements documents ( MRD), and product requirements documents (PRD) for new and existing products.Support product launches end-to-end, including collateral, internal training, and go-to-market execution.Assist market intelligence team on packaging, pricing, feature prioritization, and messaging.Enable the sales and design teams with product data sheets." We need to split into list items. Each sentence seems a responsibility. We'll create
- for each.
Required Experience: bullet list:
- 7+ years in product marketing, ideally in complex B2B tech—energy, infrastructure, or hardware/software hybrids.
- Experience writing or managing MRDs and PRDs with cross-functional teams.
- Strong grasp of go-to-market mechanics, including personas, ideal customer profiles, TAM/SAM/SOM, and pricing models.
- Familiarity with energy storage systems, grid interconnections, or electrical and mechanical systems.
- Skilled at translating technical features into benefit-driven messaging.
- Experience creating sales enablement assets, product collateral, and executive-ready positioning docs.
Preferred Experience:
- Experience with utilities, grid infrastructure, or energy storage (FESS, BESS, microgrids).
- Knowledge of regulatory frameworks: IEEE, UL, NERC, FERC, CAISO, etc.
- Worked in or marketed to utilities, commercial & industrial, data centers, or government/ defense sectors.
- Led multiple product launches and evolved messaging across product lifecycles.
- Background collaborating with brand, comms, and external creative partners.
- Bonus if you’ve marketed a vertically integrated product stack (hardware + firmware + software).
Additional Details:
- Background Check: All candidates are subject to a background check.
- Location + Travel: The role is based in Utah including hybrid remote with work based in your home office and our Salt Lake City/South Salt Lake warehouses, as needed.
- Schedule: Full-Time, Salaried
- Compensation: $165,000 - 190,000 (Note: We have the flexibility to hire at different levels, which may impact the corresponding pay range.)
- Work Authorization: Applicants must already have the legal authorization to work in the US without requiring any employer sponsorship.
- Physical Requirements: list of items.
- Our Perks & Benefits: details.
We need to include Benefits section with details.
We need to include Pay section with compensation range.
Schedule section with Full-Time, Salaried.
We might also include Location as a short paragraph under About the role or after? Since no heading for location, we can put a short
after About the role. We must not include sections like "Background Check" or "Work Authorization" as headings; we can embed them as list items under Requirements or Qualifications. Physical Requirements also as list items. Thus we will have sections:
About the role
...
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Skills
- ...
- . Now Qualifications (Preferred Experience) list: - Experience with utilities, grid infrastructure, or energy storage (FESS, BESS, microgrids). - Knowledge of regulatory frameworks: IEEE, UL, NERC, FERC, CAISO, etc. - Worked in or marketed to utilities, commercial & industrial, data centers, or government/ defense sectors. - Led multiple product launches and evolved messaging across product lifecycles. - Background collaborating with brand, comms, and external creative partners. - Bonus if you’ve marketed a vertically integrated product stack (hardware + firmware + software). Now Benefits section: extract from "Our Perks & Benefits": - Benefits eligibility is based on employment status. - Financial Employee Re
- for any list. Could have two lists: Required Experience and Preferred Experience. Could put headings inside? Not allowed; only section headings are the specified ones. Could embed bold text? Not specified. Safer to keep separate sections: Requirements and Qualifications? But they said use headings like Requirements, Qualifications. Could treat Required Experience as Requirements, Preferred Experience as Qualifications. That seems reasonable.
- Skills: The posting includes "Skilled at translating technical features into benefit-driven messaging." etc. That's under Required Experience bullet. Could be part of Skills section. We could create a Skills section listing those skills.
- Benefits: The posting includes "Our Perks & Benefits" with details. So we need Benefits section.
- Pay: The posting includes "Compensation $165,000 - 190,000". So Pay section.
- Schedule: The posting includes "Schedule Full-Time, Salaried". So Schedule section.
Also location + travel: maybe not needed as separate heading; could be included in a short paragraph under About the role? But we have no heading for location. Could embed in a paragraph under About the role or maybe under a generic "About the role"? The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short