Senior Product Manager, Control Plane, RSC-G & Government

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove inclusion sections? Those are likely boilerplate; they are about inclusion, EEO, etc. Should be removed. Also remove LinkedIn etc. Also remove "Join Us in Securing and Accelerating the World's AI Transformation" maybe part of description? Might be considered substantive? It's more marketing; but we need to preserve all substantive information. However the instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The inclusion sections are not exactly legal but maybe considered boilerplate? They are about inclusion, but not EEO? Might be considered part of company culture; but they might be considered boilerplate? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Inclusion sections are not exactly EEO but could be considered similar. Safer to remove them as they are likely boilerplate. Also remove "Equal Opportunity Employer/Veterans/Disabled" etc. We need to extract sections: About The Product Org, About The Team, About The Role (which includes responsibilities). Also Preferred Qualifications (list). Also Pay range. Also maybe Benefits? Not mentioned besides "eligible for bonus potential, equity and benefits." No specifics. So we should not create Benefits section unless specific. So we omit Benefits. Schedule not mentioned. So omit Schedule. We need headings: About the role (maybe combine About The Product Org, About The Team, About The Role?). The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. Possibly also About The Product Org and About The Team could be part of About the role? But we need to follow headings list; we can include About the role as a heading and put the description under it. Could also split into About the product org and About the team as subheadings? Not allowed; only those headings. So we should put all descriptive paragraphs under About the role. Responsibilities: list of duties from About The Role bullet points. Requirements: maybe the qualifications? Actually we have Preferred Qualifications list. Also maybe Requirements could be the required qualifications? The posting doesn't have explicit "Requirements" separate from Preferred Qualifications. Could treat Preferred Qualifications as Requirements? Or we could have Requirements empty? Better to have Qualifications section for the preferred qualifications list. And maybe Skills for certain skills? But we have many skills listed; could put them under Skills. However we need to avoid duplication. Let's parse: About The Role paragraph includes responsibilities: Own Rubrik's cloud and virtual scale out cluster software: Lead the full product lifecycle... etc. That's a list of duties. Then later: Preferred Qualifications list: Bachelor's degree..., Experience with defining..., Strong understanding..., Experience with deploying..., Understands modeling..., Needs to understand..., Is able to apply..., 5+ years..., Strong understanding..., Experience presenting..., Ability to manage..., Data protection..., Experience writing..., Experience presenting..., A desire..., Demonstrate... Also earlier: "What we do truly matters..." etc is fluff. We need to preserve all substantive info. So we need to include the paragraphs about About The Product Org, About The Team, About The Role (the narrative). Also the Preferred Qualifications list. Also the Pay range. We also have "The minimum and maximum base salaries for this role are posted below; additionally, the role is eligible for bonus potential, equity and benefits." That's substantive about Pay and eligibility for bonus/equity/benefits. Since we don't have specific benefits details, we can still include Pay section with the range and note about bonus/equity/benefits. We should not include Benefits section because no specifics. We need to output HTML fragment only. Structure:

About the role

... paragraphs combined ...

Responsibilities

• ...
...

Qualifications

• ...
...

Pay

US Pay Range $170,400—$255,600 USD. The role is eligible for bonus potential, equity and benefits.

We might also include Skills? Could extract skills from qualifications but they'd duplicate. Better not to create Skills if no distinct content. Check for duplicated lines: The posting repeats "Experience presenting technical material to small and large audiences." twice. We should deduplicate. Also "Experience writing detailed complex documentation." appears once. Also "Strong understanding of cloud data management solutions and data center infrastructure." appears maybe twice? Let's check: In Preferred Qualifications: "Strong understanding of cloud data management solutions and data center infrastructure." appears once. Also earlier: "Strong understanding of cloud data management solutions and data center infrastructure." maybe not. We'll deduplicate. Now craft About the role paragraph: combine About The Product Org, About The Team, About The Role narrative. About The Product Org: "The Product Team at Rubrik is responsible for driving Rubrik’s mission of securing the world’s data by creating products that simplify the complexity of managing cyber resilience across all applications and types of data. We seek to build consumer grade experiences to solve the hardest and most complex enterprise challenges." About The Team: "The Platform Product team is responsible for delivering Rubrik’s industry leading SaaS solution across all environments–ranging from the data center to the cloud. We ensure that we can meet customer’s needs to deliver our solution across a range of server platforms from multiple vendors, onto all leading hypervisors and into hyperscale cloud providers." About The Role narrative: "Own Rubrik's cloud and virtual scale out cluster software: Lead the full product lifecycle, from ideation through development, launch, and ongoing enhancements. Drive alignment and consistency of management between cloud offerings and on-premises solutions deployed on the industry leading virtualization platforms to ensure our solution can be deployed in any environment on the latest server platforms. Define and communicate the product vision, strategy, and roadmap, aligning with customer needs and business objectives. Collaborate with engineering, design, and marketing teams to develop new features and optimize existing functionalities. Monitor and analyze key performance indicators (KPIs) to assess product success and drive data-driven decisions for continuous improvement. Engage with customers and partners to gather feedback and drive product improvements based on their needs. Drive strategic product initiatives: Continuously evaluate the competitive landscape and market trends to identify opportunities and threats. Develop and execute strategies to differentiate Rubrik’s offerings and strengthen market position. Communicate the product vision and strategy effectively to internal and external stakeholders, ensuring alignment and support. Support and engage with Rubrik field, the Rubrik reseller community and customers: Provide technical expertise and support to sales teams and resellers, enabling them to deliver compelling data management solutions. Develop training and enablement materials to ensure sales teams and resellers are well-equipped to sell and support Rubrik products. Engage with key customers and prospects to understand their needs and nt collaboration, interpersonal and verbal and written communication skills. Utilize industry standard product management methodologies to document and communicate product status and roadmap: Write detailed and complex documentation for both internal and external audiences, ensuring clarity and thoroughness. Present technical material to small and large audiences, effectively communicating complex concepts and product features. Maintain open and effective communication channels with all stakeholders to foster collaboration and transparency." Note there is a typo "nt collaboration". We'll keep as is. Now Responsibilities: we can extract bullet points from the About The Role narrative. But we already used that narrative for About the role. Might be duplication. Better to separate: About the role could be a brief summary, and Responsibilities list the duties. However the instruction says include a section only when posting has real specific content. We have both narrative and list; we can keep both. But we need to avoid repeating same content. We could make About the role a short paragraph summarizing the role (maybe first two sentences). Then Responsibilities list the detailed duties. Let's craft About the role paragraph: "Own Rubrik's cloud and virtual scale out cluster software, leading the full product lifecycle from ideation through launch and ongoing enhancements, and driving alignment between cloud and on-premises solutions across virtualization platforms and server environments." That's concise but we must preserve all substantive info; we cannot summarize away detail. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot summarize; we must keep all details. So we need to keep the full narrative. If we also list responsibilities as bullet points, we would be duplicating content. That's not allowed? It says preserve ALL substantive information; does not forbid duplication but better to avoid redundancy. However we could keep the narrative as is and not have a separate Responsibilities list, or we could turn the narrative into a list. The instruction: Use

• for any list of duties/requirements/benefits. So if we have duties, we should put them in a list. The narrative is not a list; we could convert it to list items. That would preserve all details without summarizing. So we can have a Responsibilities section with list items each duty. Then we don't need a separate About the role paragraph (except maybe a brief intro). But we need About the role heading per instruction; we could still have About the role with a short summary but that would be summarizing. Better to not have About the role section if we have Responsibilities covering duties? But instruction says use headings like About the role, Responsibilities, etc. It doesn't mandate we must include About the role; we include only when posting has real specific content for it. The posting does have a description about the role (the narrative). So we need About the role section with that content. Could we put the narrative in a

  under About the role, and also have Responsibilities list? That would duplicate. To avoid duplication, we could make About the role section contain a brief overview (maybe first sentence) and Responsibilities list the rest. But that would be summarizing (omitting details) from About the role. That violates "preserve ALL substantive information". So we need to include all details somewhere. We could put the full narrative in About the role as a paragraph, and also have Responsibilities list that repeats the same content but that's duplication but still preserves all info (no loss). Duplication is not prohibited explicitly, but might be considered redundant. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not inventing or summarizing away; it's repeating. It's allowed but maybe not ideal. However we could avoid duplication by making About the role section just a heading with no content? Not allowed because we must not emit heading followed by filler/placeholder text. So we need content. Thus we could put the narrative in About the role as a paragraph, and then Responsibilities list could be omitted (since we already covered duties). But we need to decide which sections to include. The instruction list includes Responsibilities as an example heading; we can include it if we have specific content. We have duties; we could put them in Responsibilities list and omit About the role paragraph (or make About the role just a short intro that is not summarizing? That would lose details). So better to put duties in Responsibilities list and maybe keep About the role as a brief description that is not summarizing but maybe just a generic statement like "The role involves leading product management for Rubrik's cloud and virtual scale-out cluster software." That is still summarizing but maybe acceptable? The instruction says do NOT summarize away detail. That implies we cannot omit details; summarizing would lose detail. So we must keep all details. Therefore we need to keep the full narrative somewhere. If we put it in About the role as a paragraph, we have all details. Then we could still have Respons