Product Insights & System Integration Product Manager
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate etc. Preserve all substantive info. Do not invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them.
We have content: company description, role description, responsibilities (HOW YOU’LL SPEND YOUR TIME HERE with sub-sections), requirements (WE’D LOVE TO TALK TO YOU IF YOU HAVE MANY OF THE FOLLOWING), qualifications (Bachelor's degree required, MBA preferred), maybe skills (list of skills). Pay range given. Benefits mentioned: comprehensive benefits framework (health and wellness benefits, vacation, paid holidays and refresh days, 401(k) retirement plan, life and disability insurance coverages, etc). Schedule: In-Office Expectations: 2-3 days a week in office for those within commute. That's schedule info.
We need to map to sections: About the role (company overview and role purpose). Responsibilities (the HOW YOU’LL SPEND YOUR TIME HERE bullet points). Requirements (maybe the "WE’D LOVE TO TALK TO YOU IF YOU HAVE MANY OF THE FOLLOWING" list). Qualifications (Bachelor's degree required, MBA preferred). Skills (maybe the list of specific skills like experience with PRM systems, Salesforce, UAT, project management, analytical, etc). Benefits (the benefits description). Pay (the pay range). Schedule (In-Office Expectations). Ensure we don't create sections with filler.
We must not repeat job title. No headings for Job ID etc.
We must output only HTML fragment, no /, no markdown fences.
We need to use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information. So we need to include details like company description, mission, etc.
Let's extract substantive content:
Company description: "Cohesity is a leader in AI-powered data security and management. Aided by an extensive ecosystem of partners, Cohesity makes it easy to secure, protect, manage, and get value from data — across the data center, edge, and cloud. Cohesity helps organizations defend against cybersecurity threats with comprehensive data security and management capabilities, including immutable backup snapshots, AI-based threat detection, monitoring for malicious behavior, and rapid recovery at scale. We’ve been named a Leader by multiple analyst firms and have been globally recognized for Innovation, Product Strength, and Simplicity in Design. Join us on our mission to shape the future of our industry."
Role overview: "Cohesity is looking for an experienced and passionate Principal Product Manager to join our product management team to drive partner insights and systems integration. Cohesity is a leader in the Gartner Magic Quadrant for Data Protection as well as “Leader” and “Outperformer” in the GigaOm Radar for Enterprise Scale-Out File Systems and we are only just starting. We are looking for someone who, like us, cares deeply about understanding our customer’s needs and takes pride in building irresistibly delightful products built from the ground up for protecting and managing customer data. At Cohesity, we are aggressively taking market share from the legacy players in a $10B+ market and you’ll be instrumental in driving that growth. At Cohesity, product management plays a central role in driving product development by working in close collaboration with our engineering and go-to-market teams. Our team works across all levels of the organization; engaging with executive stakeholders, directly with customers across the globe, and interacting heavily with our user experience team. You’ll do your best work at Cohesity with an incredibly talented team! This is a pivotal, highly strategic position that will shape Cohesity’s overall security strategy, security portfolio, and roadmap across both its traditional customer-managed platforms and Cohesity’s cloud-based SaaS platform as well as App Marketplace in service of Cohesity’s ever-expanding list of enterprise customers across different verticals and geographies. If this sounds like the next step in your career, read on! This is a SaaS product management role at the center of Cohesity's partner ecosystem."
Then responsibilities broken into sub-sections: Partner Listening & Requirements Gathering, Product Management & Competitive Market Analysis, Enterprise Technology & Systems Integration, Project Management & User Acceptance Testing. Each has bullet points.
We need to output as
- for each duty. Could group under a single Responsibilities section with subheadings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid subheadings inside sections, but we should follow only those headings. Could embed subheadings as maybe but not required. Safer to just list responsibilities as bullet points under Responsibilities . We can include the detailed bullet points.
Similarly, Requirements section: list of requirements from "WE’D LOVE TO TALK TO YOU IF YOU HAVE MANY OF THE FOLLOWING". That's a list.
Qualifications: Bachelor's degree required, MBA preferred or equivalent experience.
Skills: maybe list of specific skills: outbound product management experience, ease with partners, hands-on experience with PRM systems, Salesforce proficiency, UAT experience, project management skills, competitive/market analysis, analytical skills, organizational/time-management, experience with project/analytics tooling, experience with partner advisory councils, etc.
Benefits: "Additionally, full-time employees are eligible to participate in our comprehensive benefits framework, including health and wellness benefits, vacation, paid holidays and refresh days, 401(k) retirement plan, life and disability insurance coverages, and other benefits the Company may offer from time to time."
Pay: "Pay Range : $174,960.00-$194,400.00". Also note about bonus, commission, equity.
Schedule: "In-Office Expectations Cohesity employees who are within a reasonable commute (e.g. within a forty-five (45) minute average travel time) work out of our core offices 2-3 days a week of their choosing. We strongly prefer candidates who are currently located in or near the designated job location. Candidates outside the area should apply only if they are committed to relocating prior to their start date and have the legal right to work in the job location."
We should not include application instructions (like contact info for accommodation). Also remove EEO boilerplate, data privacy notice, etc.
We must not include filler like "commensurate with experience". Not present.
Now craft HTML.
Structure:
About the role
... company description and role overview ...
Responsibilities
- Partner Listening & Requirements Gathering: ... (maybe break into sub-bullets? Could keep as one li with semicolons)
- Product Management & Competitive Market Analysis: ...
- Enterprise Technology & Systems Integration: ...
- Project Management & User Acceptance Testing: ...
But we need to preserve all substantive information; we can break each bullet into multiple li for each sub-point. However the instruction says use - for any list of duties/requirements/benefits. It doesn't forbid nested lists. Could do top-level li for each responsibility area, and inside each li we could have another
for sub-points. That's still using - . Acceptable.
Similarly for Requirements: list of items.
Skills: list.
Benefits: list.
Pay: maybe just
with range.
Schedule:
with description.
Let's extract details precisely.
Company description paragraph: combine first paragraph plus maybe second paragraph about mission.
I'll craft a concise but complete paragraph preserving all details.
About the role paragraph:
"Cohesity is a leader in AI-powered data security and management, aided by an extensive ecosystem of partners that makes it easy to secure, protect, manage, and get value from data across the data center, edge, and cloud. The company helps organizations defend against cybersecurity threats with capabilities such as immutable backup snapshots, AI-based threat detection, monitoring for malicious behavior, and rapid recovery at scale. Cohesity has been named a Leader by multiple analyst firms and globally recognized for Innovation, Product Strength, and Simplicity in Design. The mission is to shape the future of the industry. Cohesity is seeking an experienced and passionate Principal Product Manager to drive partner insights and systems integration, shaping the overall security strategy, portfolio, and roadmap across traditional customer‑managed platforms, the cloud‑based SaaS platform, and the App Marketplace for enterprise customers across verticals and geographies."
That seems to capture.
Now Responsibilities: we need to include all bullet points from each sub-section.
Let's extract each sub-section's bullet points:
Partner Listening & Requirements Gathering:
- Sit directly with partners and other stakeholders — in listening sessions, demos, advisory boards, and 1:1 conversations — to gather feedback and probe for the real requirement behind the request.
- Own multi-channel partner feedback infrastructure (NPS, transactional surveys, always-on sentiment, qualitative interviews, field-gathered insight from channel managers) across distributors, VARs, MSPs, SIs, and ISVs.
- Convert qualitative and quantitative partner feedback into clear, prioritized, testable requirements that Enterprise Technology can design against.
- Close the loop with partners: communicate how their feedback shaped program and system decisions, building trust in the listening process.
- Facilitate structured feedback mechanisms that give partner voices a formal channel to Cohesity leadership.
Product Management & Competitive Market Analysis:
- Bring outbound product management discipline from an enterprise SaaS background — market sizing, competitive teardown, positioning input, and voice-of-partner synthesis — to the partner systems roadmap.
- Continuously track the competitive landscape for partner programs, PRM platforms, and partner portal experiences; bring market insight to bear on requirements and prioritization.
- Own and prioritize the partner-facing product/requirements backlog, balancing partner-voiced needs against Enterprise Technology capacity and business impact.
- Apply knowledge of how partner and channel business actually flows — deal registration, MDF/rebate claims, tiering, onboarding — to judge whether a proposed system design will actually work in the field.
- Build the business case (cost/benefit, adoption impact) for proposed product and system changes and present it to Partner Programs and Enterprise Technology leadership.
Enterprise Technology & Systems Integration:
- Serve as the primary liaison between the Partner Programs team, Business Stakeholders, and Enterprise Technology, translating approved program requirements into system and integration specifications.
- Partner with Business Stakeholders & Enterprise Technology on the systemic integration of program design into core systems — CRM/SFDC, partner portal, deal registration, automated workflow, reporting, and analytics platforms.
- Act as subject-matter expert on how channel systems interconnect (e.g., SFDC-to-partner-portal integration, automated process flows between systems) and troubleshoot systemic issues in partnership with global system administrators.
- Test and validate that new or modified systems and integrations accurately reflect program requirements before go-live, and own defect triage during rollout.
- Identify opportunities to automate manual, error-prone channel processes in collaboration with Enterprise Technology.
Project Management & User Acceptance Testing:
- Own the end-to-end project plan for translating each approved requirement into a live, integrated system capability — scope, mil
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate etc. Preserve all substantive info. Do not invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. We have content: company description, role description, responsibilities (HOW YOU’LL SPEND YOUR TIME HERE with sub-sections), requirements (WE’D LOVE TO TALK TO YOU IF YOU HAVE MANY OF THE FOLLOWING), qualifications (Bachelor's degree required, MBA preferred), maybe skills (list of skills). Pay range given. Benefits mentioned: comprehensive benefits framework (health and wellness benefits, vacation, paid holidays and refresh days, 401(k) retirement plan, life and disability insurance coverages, etc). Schedule: In-Office Expectations: 2-3 days a week in office for those within commute. That's schedule info. We need to map to sections: About the role (company overview and role purpose). Responsibilities (the HOW YOU’LL SPEND YOUR TIME HERE bullet points). Requirements (maybe the "WE’D LOVE TO TALK TO YOU IF YOU HAVE MANY OF THE FOLLOWING" list). Qualifications (Bachelor's degree required, MBA preferred). Skills (maybe the list of specific skills like experience with PRM systems, Salesforce, UAT, project management, analytical, etc). Benefits (the benefits description). Pay (the pay range). Schedule (In-Office Expectations). Ensure we don't create sections with filler. We must not repeat job title. No headings for Job ID etc. We must output only HTML fragment, no /, no markdown fences. We need to use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information. So we need to include details like company description, mission, etc.
Let's extract substantive content:
Company description: "Cohesity is a leader in AI-powered data security and management. Aided by an extensive ecosystem of partners, Cohesity makes it easy to secure, protect, manage, and get value from data — across the data center, edge, and cloud. Cohesity helps organizations defend against cybersecurity threats with comprehensive data security and management capabilities, including immutable backup snapshots, AI-based threat detection, monitoring for malicious behavior, and rapid recovery at scale. We’ve been named a Leader by multiple analyst firms and have been globally recognized for Innovation, Product Strength, and Simplicity in Design. Join us on our mission to shape the future of our industry."
Role overview: "Cohesity is looking for an experienced and passionate Principal Product Manager to join our product management team to drive partner insights and systems integration. Cohesity is a leader in the Gartner Magic Quadrant for Data Protection as well as “Leader” and “Outperformer” in the GigaOm Radar for Enterprise Scale-Out File Systems and we are only just starting. We are looking for someone who, like us, cares deeply about understanding our customer’s needs and takes pride in building irresistibly delightful products built from the ground up for protecting and managing customer data. At Cohesity, we are aggressively taking market share from the legacy players in a $10B+ market and you’ll be instrumental in driving that growth. At Cohesity, product management plays a central role in driving product development by working in close collaboration with our engineering and go-to-market teams. Our team works across all levels of the organization; engaging with executive stakeholders, directly with customers across the globe, and interacting heavily with our user experience team. You’ll do your best work at Cohesity with an incredibly talented team! This is a pivotal, highly strategic position that will shape Cohesity’s overall security strategy, security portfolio, and roadmap across both its traditional customer-managed platforms and Cohesity’s cloud-based SaaS platform as well as App Marketplace in service of Cohesity’s ever-expanding list of enterprise customers across different verticals and geographies. If this sounds like the next step in your career, read on! This is a SaaS product management role at the center of Cohesity's partner ecosystem."
Then responsibilities broken into sub-sections: Partner Listening & Requirements Gathering, Product Management & Competitive Market Analysis, Enterprise Technology & Systems Integration, Project Management & User Acceptance Testing. Each has bullet points.
We need to output as
- for each duty. Could group under a single Responsibilities section with subheadings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid subheadings inside sections, but we should follow only those headings. Could embed subheadings as maybe but not required. Safer to just list responsibilities as bullet points under Responsibilities . We can include the detailed bullet points.
Similarly, Requirements section: list of requirements from "WE’D LOVE TO TALK TO YOU IF YOU HAVE MANY OF THE FOLLOWING". That's a list.
Qualifications: Bachelor's degree required, MBA preferred or equivalent experience.
Skills: maybe list of specific skills: outbound product management experience, ease with partners, hands-on experience with PRM systems, Salesforce proficiency, UAT experience, project management skills, competitive/market analysis, analytical skills, organizational/time-management, experience with project/analytics tooling, experience with partner advisory councils, etc.
Benefits: "Additionally, full-time employees are eligible to participate in our comprehensive benefits framework, including health and wellness benefits, vacation, paid holidays and refresh days, 401(k) retirement plan, life and disability insurance coverages, and other benefits the Company may offer from time to time."
Pay: "Pay Range : $174,960.00-$194,400.00". Also note about bonus, commission, equity.
Schedule: "In-Office Expectations Cohesity employees who are within a reasonable commute (e.g. within a forty-five (45) minute average travel time) work out of our core offices 2-3 days a week of their choosing. We strongly prefer candidates who are currently located in or near the designated job location. Candidates outside the area should apply only if they are committed to relocating prior to their start date and have the legal right to work in the job location."
We should not include application instructions (like contact info for accommodation). Also remove EEO boilerplate, data privacy notice, etc.
We must not include filler like "commensurate with experience". Not present.
Now craft HTML.
Structure:
About the role
... company description and role overview ...
Responsibilities
- Partner Listening & Requirements Gathering: ... (maybe break into sub-bullets? Could keep as one li with semicolons)
- Product Management & Competitive Market Analysis: ...
- Enterprise Technology & Systems Integration: ...
- Project Management & User Acceptance Testing: ...
But we need to preserve all substantive information; we can break each bullet into multiple li for each sub-point. However the instruction says use - for any list of duties/requirements/benefits. It doesn't forbid nested lists. Could do top-level li for each responsibility area, and inside each li we could have another
for sub-points. That's still using - . Acceptable.
Similarly for Requirements: list of items.
Skills: list.
Benefits: list.
Pay: maybe just
with range.
Schedule:
with description.
Let's extract details precisely.
Company description paragraph: combine first paragraph plus maybe second paragraph about mission.
I'll craft a concise but complete paragraph preserving all details.
About the role paragraph:
"Cohesity is a leader in AI-powered data security and management, aided by an extensive ecosystem of partners that makes it easy to secure, protect, manage, and get value from data across the data center, edge, and cloud. The company helps organizations defend against cybersecurity threats with capabilities such as immutable backup snapshots, AI-based threat detection, monitoring for malicious behavior, and rapid recovery at scale. Cohesity has been named a Leader by multiple analyst firms and globally recognized for Innovation, Product Strength, and Simplicity in Design. The mission is to shape the future of the industry. Cohesity is seeking an experienced and passionate Principal Product Manager to drive partner insights and systems integration, shaping the overall security strategy, portfolio, and roadmap across traditional customer‑managed platforms, the cloud‑based SaaS platform, and the App Marketplace for enterprise customers across verticals and geographies."
That seems to capture.
Now Responsibilities: we need to include all bullet points from each sub-section.
Let's extract each sub-section's bullet points:
Partner Listening & Requirements Gathering:
- Sit directly with partners and other stakeholders — in listening sessions, demos, advisory boards, and 1:1 conversations — to gather feedback and probe for the real requirement behind the request.
- Own multi-channel partner feedback infrastructure (NPS, transactional surveys, always-on sentiment, qualitative interviews, field-gathered insight from channel managers) across distributors, VARs, MSPs, SIs, and ISVs.
- Convert qualitative and quantitative partner feedback into clear, prioritized, testable requirements that Enterprise Technology can design against.
- Close the loop with partners: communicate how their feedback shaped program and system decisions, building trust in the listening process.
- Facilitate structured feedback mechanisms that give partner voices a formal channel to Cohesity leadership.
Product Management & Competitive Market Analysis:
- Bring outbound product management discipline from an enterprise SaaS background — market sizing, competitive teardown, positioning input, and voice-of-partner synthesis — to the partner systems roadmap.
- Continuously track the competitive landscape for partner programs, PRM platforms, and partner portal experiences; bring market insight to bear on requirements and prioritization.
- Own and prioritize the partner-facing product/requirements backlog, balancing partner-voiced needs against Enterprise Technology capacity and business impact.
- Apply knowledge of how partner and channel business actually flows — deal registration, MDF/rebate claims, tiering, onboarding — to judge whether a proposed system design will actually work in the field.
- Build the business case (cost/benefit, adoption impact) for proposed product and system changes and present it to Partner Programs and Enterprise Technology leadership.
Enterprise Technology & Systems Integration:
- Serve as the primary liaison between the Partner Programs team, Business Stakeholders, and Enterprise Technology, translating approved program requirements into system and integration specifications.
- Partner with Business Stakeholders & Enterprise Technology on the systemic integration of program design into core systems — CRM/SFDC, partner portal, deal registration, automated workflow, reporting, and analytics platforms.
- Act as subject-matter expert on how channel systems interconnect (e.g., SFDC-to-partner-portal integration, automated process flows between systems) and troubleshoot systemic issues in partnership with global system administrators.
- Test and validate that new or modified systems and integrations accurately reflect program requirements before go-live, and own defect triage during rollout.
- Identify opportunities to automate manual, error-prone channel processes in collaboration with Enterprise Technology.
Project Management & User Acceptance Testing:
- Own the end-to-end project plan for translating each approved requirement into a live, integrated system capability — scope, mil
for prose. We need to preserve all substantive information. So we need to include details like company description, mission, etc. Let's extract substantive content: Company description: "Cohesity is a leader in AI-powered data security and management. Aided by an extensive ecosystem of partners, Cohesity makes it easy to secure, protect, manage, and get value from data — across the data center, edge, and cloud. Cohesity helps organizations defend against cybersecurity threats with comprehensive data security and management capabilities, including immutable backup snapshots, AI-based threat detection, monitoring for malicious behavior, and rapid recovery at scale. We’ve been named a Leader by multiple analyst firms and have been globally recognized for Innovation, Product Strength, and Simplicity in Design. Join us on our mission to shape the future of our industry." Role overview: "Cohesity is looking for an experienced and passionate Principal Product Manager to join our product management team to drive partner insights and systems integration. Cohesity is a leader in the Gartner Magic Quadrant for Data Protection as well as “Leader” and “Outperformer” in the GigaOm Radar for Enterprise Scale-Out File Systems and we are only just starting. We are looking for someone who, like us, cares deeply about understanding our customer’s needs and takes pride in building irresistibly delightful products built from the ground up for protecting and managing customer data. At Cohesity, we are aggressively taking market share from the legacy players in a $10B+ market and you’ll be instrumental in driving that growth. At Cohesity, product management plays a central role in driving product development by working in close collaboration with our engineering and go-to-market teams. Our team works across all levels of the organization; engaging with executive stakeholders, directly with customers across the globe, and interacting heavily with our user experience team. You’ll do your best work at Cohesity with an incredibly talented team! This is a pivotal, highly strategic position that will shape Cohesity’s overall security strategy, security portfolio, and roadmap across both its traditional customer-managed platforms and Cohesity’s cloud-based SaaS platform as well as App Marketplace in service of Cohesity’s ever-expanding list of enterprise customers across different verticals and geographies. If this sounds like the next step in your career, read on! This is a SaaS product management role at the center of Cohesity's partner ecosystem." Then responsibilities broken into sub-sections: Partner Listening & Requirements Gathering, Product Management & Competitive Market Analysis, Enterprise Technology & Systems Integration, Project Management & User Acceptance Testing. Each has bullet points. We need to output as
- for each duty. Could group under a single Responsibilities section with subheadings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid subheadings inside sections, but we should follow only those headings. Could embed subheadings as
maybe but not required. Safer to just list responsibilities as bullet points under Responsibilities
. We can include the detailed bullet points. Similarly, Requirements section: list of requirements from "WE’D LOVE TO TALK TO YOU IF YOU HAVE MANY OF THE FOLLOWING". That's a list. Qualifications: Bachelor's degree required, MBA preferred or equivalent experience. Skills: maybe list of specific skills: outbound product management experience, ease with partners, hands-on experience with PRM systems, Salesforce proficiency, UAT experience, project management skills, competitive/market analysis, analytical skills, organizational/time-management, experience with project/analytics tooling, experience with partner advisory councils, etc. Benefits: "Additionally, full-time employees are eligible to participate in our comprehensive benefits framework, including health and wellness benefits, vacation, paid holidays and refresh days, 401(k) retirement plan, life and disability insurance coverages, and other benefits the Company may offer from time to time." Pay: "Pay Range : $174,960.00-$194,400.00". Also note about bonus, commission, equity. Schedule: "In-Office Expectations Cohesity employees who are within a reasonable commute (e.g. within a forty-five (45) minute average travel time) work out of our core offices 2-3 days a week of their choosing. We strongly prefer candidates who are currently located in or near the designated job location. Candidates outside the area should apply only if they are committed to relocating prior to their start date and have the legal right to work in the job location." We should not include application instructions (like contact info for accommodation). Also remove EEO boilerplate, data privacy notice, etc. We must not include filler like "commensurate with experience". Not present. Now craft HTML. Structure:
About the role
... company description and role overview ...
Responsibilities
- Partner Listening & Requirements Gathering: ... (maybe break into sub-bullets? Could keep as one li with semicolons)
- Product Management & Competitive Market Analysis: ...
- Enterprise Technology & Systems Integration: ...
- Project Management & User Acceptance Testing: ...
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. Could do top-level li for each responsibility area, and inside each li we could have another
- for sub-points. That's still using
- . Acceptable.
Similarly for Requirements: list of items.
Skills: list.
Benefits: list.
Pay: maybe just
with range. Schedule:
with description. Let's extract details precisely. Company description paragraph: combine first paragraph plus maybe second paragraph about mission. I'll craft a concise but complete paragraph preserving all details. About the role paragraph: "Cohesity is a leader in AI-powered data security and management, aided by an extensive ecosystem of partners that makes it easy to secure, protect, manage, and get value from data across the data center, edge, and cloud. The company helps organizations defend against cybersecurity threats with capabilities such as immutable backup snapshots, AI-based threat detection, monitoring for malicious behavior, and rapid recovery at scale. Cohesity has been named a Leader by multiple analyst firms and globally recognized for Innovation, Product Strength, and Simplicity in Design. The mission is to shape the future of the industry. Cohesity is seeking an experienced and passionate Principal Product Manager to drive partner insights and systems integration, shaping the overall security strategy, portfolio, and roadmap across traditional customer‑managed platforms, the cloud‑based SaaS platform, and the App Marketplace for enterprise customers across verticals and geographies." That seems to capture. Now Responsibilities: we need to include all bullet points from each sub-section. Let's extract each sub-section's bullet points: Partner Listening & Requirements Gathering: - Sit directly with partners and other stakeholders — in listening sessions, demos, advisory boards, and 1:1 conversations — to gather feedback and probe for the real requirement behind the request. - Own multi-channel partner feedback infrastructure (NPS, transactional surveys, always-on sentiment, qualitative interviews, field-gathered insight from channel managers) across distributors, VARs, MSPs, SIs, and ISVs. - Convert qualitative and quantitative partner feedback into clear, prioritized, testable requirements that Enterprise Technology can design against. - Close the loop with partners: communicate how their feedback shaped program and system decisions, building trust in the listening process. - Facilitate structured feedback mechanisms that give partner voices a formal channel to Cohesity leadership. Product Management & Competitive Market Analysis: - Bring outbound product management discipline from an enterprise SaaS background — market sizing, competitive teardown, positioning input, and voice-of-partner synthesis — to the partner systems roadmap. - Continuously track the competitive landscape for partner programs, PRM platforms, and partner portal experiences; bring market insight to bear on requirements and prioritization. - Own and prioritize the partner-facing product/requirements backlog, balancing partner-voiced needs against Enterprise Technology capacity and business impact. - Apply knowledge of how partner and channel business actually flows — deal registration, MDF/rebate claims, tiering, onboarding — to judge whether a proposed system design will actually work in the field. - Build the business case (cost/benefit, adoption impact) for proposed product and system changes and present it to Partner Programs and Enterprise Technology leadership. Enterprise Technology & Systems Integration: - Serve as the primary liaison between the Partner Programs team, Business Stakeholders, and Enterprise Technology, translating approved program requirements into system and integration specifications. - Partner with Business Stakeholders & Enterprise Technology on the systemic integration of program design into core systems — CRM/SFDC, partner portal, deal registration, automated workflow, reporting, and analytics platforms. - Act as subject-matter expert on how channel systems interconnect (e.g., SFDC-to-partner-portal integration, automated process flows between systems) and troubleshoot systemic issues in partnership with global system administrators. - Test and validate that new or modified systems and integrations accurately reflect program requirements before go-live, and own defect triage during rollout. - Identify opportunities to automate manual, error-prone channel processes in collaboration with Enterprise Technology. Project Management & User Acceptance Testing: - Own the end-to-end project plan for translating each approved requirement into a live, integrated system capability — scope, mil
- . Acceptable.
Similarly for Requirements: list of items.
Skills: list.
Benefits: list.
Pay: maybe just