Lead Principal Product Manager
for 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. Remove boilerplate etc.
We need to parse the job description and extract content for each section.
Sections:
- About the role: likely the introductory paragraphs describing role. We'll put that under About the role
with
content. - Responsibilities: list of responsibilities bullet points. - Requirements: maybe "Minimum Job Qualifications" includes education/experience. Could be under Requirements. - Qualifications: maybe "Qualifications Disclaimer"? Actually they have "Qualifications Disclaimer". But we need to include Qualifications section only if real specific content. The posting includes "Minimum Job Qualifications" and "Job Skills". Also "Qualifications Disclaimer". We could combine under Requirements? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have: - About the role: yes. - Responsibilities: yes. - Requirements: maybe the "Minimum Job Qualifications" (education/experience) and "Job Skills". Could be Requirements. - Qualifications: maybe the "Qualifications Disclaimer" plus any certifications? But they also have "Job Skills". Actually they list "Job Skills:" with sub-items: People Leadership, Product Domain Experience, Agile Methods Experience, Customer Interaction Experience, Certification. That seems like Skills. So Skills section. - Benefits: yes, they have benefits list. - Pay: yes, they have hiring range. - Schedule: not mentioned explicitly. No schedule info. So we should not include Schedule. Thus we will include sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to preserve all substantive information, not invent or summarize away detail. Must keep details. We need to format lists with
- . For prose use
. We need to exclude boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "About Us" maybe? That's not a section heading but could be considered boilerplate? It's about company; maybe we can keep as part of About the role? But the instruction: remove EEO/equal-opportunity boilerplate. The "About Us" paragraph at end is not EEO but could be considered boilerplate? It's generic company description. Might be considered boilerplate but not explicitly listed. Safer to remove it? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So only those specific types. "About Us" is not those, but could be considered navigation? Not sure. I'd keep it maybe as part of About the role? But we already have About the role content from earlier paragraphs. The "About Us" at end is separate; could be considered boilerplate but not listed. I'd omit to be safe? However we must preserve ALL substantive information; "About Us" is substantive about company. But it's not role-specific. Might be considered boilerplate but not excluded. I'd keep it maybe under About the role? But we already have role description. Could add a paragraph about Oracle's mission. Might be okay. But we need to avoid duplication. The earlier paragraphs already describe OCI and CHS. The "About Us" is generic Oracle statement. Could be considered boilerplate but not excluded. I'd include it as part of About the role? Might be redundant. Given the instruction to prefer few substantive sections over many thin ones, we could combine About the role and maybe include the Oracle mission as part of that. Let's extract content: About the role: The first paragraph(s) up to "We are seeking an IC5 Product Manager to own a major strategic product area within CHS software." Also includes description of OCI, CHS, role purpose. Let's capture: "At Oracle Cloud Infrastructure (OCI), we are building the next generation of cloud services that power mission-critical workloads for customers around the world. OCI combines the agility of a startup with the scale, reliability, and customer focus of one of the world’s leading technology companies. Cloud Hardware Support (CHS) plays a critical role in maintaining the health, availability, and operational readiness of OCI’s global data center infrastructure. As OCI continues to grow, CHS is investing in modern software platforms that simplify operational workflows, improve technician productivity, increase automation, and provide actionable insights across data center support operations. We are seeking an IC5 Product Manager to own a major strategic product area within CHS software. This role will define the product vision, roadmap, requirements, and execution strategy for platforms that support task management, guided workflows, inventory and logistics integration, operational analytics, workforce planning, collaboration, and data-driven decision-making. The product scope aligns to a unified operational experience where technicians, managers, support teams, and engineering partners can execute work through a single, intelligent system of engagement. As a Principal Product Manager, you will translate operational needs, user feedback, technical constraints, service reliability requirements, and business priorities into a coherent product strategy. You will partner closely with engineering, operations, technical program management, data science, service teams, and infrastructure stakeholders to define what we build, why it matters, and how success will be measured. This is a high-impact individual contributor role for a product leader who can operate from executive-level narrative to detailed product requirements. Success in this role means CHS teams have simpler workflows, clearer operational visibility, stronger automation, more reliable execution, and better data to support continuous improvement at cloud scale. The ideal candidate has deep experience with enterprise software, cloud infrastructure, operational platforms, workflow systems, analytics products, or internal tools used by large distributed organizations. You are comfortable working in ambiguous environments, driving alignment across teams, making prioritization tradeoffs, and delivering products that improve operational efficiency, reliability, and user experience." That seems good. Responsibilities: list bullet points from "Responsibilities" section. We need to capture each bullet as
- . The responsibilities list includes many sentences. Let's extract them:
- Own and continuously evolve the product strategy and roadmap for CHS software platforms supporting data center operations and hardware support workflows.
- Translate customer, operator, manager, and stakeholder needs into clear product requirements, user stories, success metrics, and phased delivery plans.
- Define product capabilities that support unified task execution, intelligent work assignment, guided procedures, inventory workflows, operational analytics, collaboration, and automation.
- Partner closely with engineering to deliver scalable, reliable, secure, and intuitive software products that operate in complex cloud infrastructure environments.
- Lead discovery with technicians, managers, support teams, service owners, and operations leaders to deeply understand workflow friction, productivity gaps, and opportunities for automation.
- Use data, metrics, and operational feedback to prioritize roadmap investments and measure product impact across efficiency, quality, resolution speed, adoption, and user satisfaction.
- Drive product requirements for task-centric workflows that reduce manual effort, minimize context switching, improve execution consistency, and make complex operational work easier to perform.
- Define analytics and reporting capabilities that provide visibility into workload, backlog, repair latency, throughput, quality, inventory readiness, technician utilization, and operational risk.
- Partner with stakeholders to build feedback loops that improve standard operating procedures, guided workflows, training, onboarding, and continuous operational improvement.
- Lead cross-functional alignment across engineering, operations, data science, program management, support, infrastructure, and service teams.
- Make clear prioritization recommendations and tradeoffs based on business impact, user value, technical feasibility, operational risk, and long-term product strategy.
- Create crisp product artifacts, including product requirement documents, roadmap narratives, launch plans, adoption plans, metric definitions, executive updates, and stakeholder communications.
- Drive product launches from concept through rollout, including pilot definition, success criteria, feedback collection, readiness planning, and adoption tracking.
- Represent the product area with senior leadership and cross-organizational stakeholders, providing clear recommendations on roadmap priorities, investment needs, risks, and execution status.
- Build deep expertise in data center support operations, cloud infrastructure workflows, hardware lifecycle processes, inventory dependencies, and operational analytics.
- Mentor product managers, engineers, and cross-functional partners by raising the quality of product thinking, customer insight, decision-making, and written product strategy.
- Champion user-centered design, operational excellence, measurable outcomes, and scalable product architecture as core principles for CHS software.
That's all.
Requirements: Minimum Job Qualifications: Education and/or Experience: 15 years of experience in product/service/project/program management, product design, or related field OR Bachelor's Degree in Engineering, Business, or related field AND 11 years of experience in product/service/project/program management, product design, or related field.
We should keep that as prose maybe
. Could also list as
- but it's a single statement with OR/AND. We'll put as
- each. Benefits: list of benefits. We need to capture all benefit items. From text: "Oracle US offers a comprehensive benefits package which includes the following: Medical, dental, and vision insurance, including expert medical opinion Short term disability and long term disability Life insurance and AD&D Supplemental life insurance (Employee/Spouse/Child) Health care and dependent care Flexible Spending Accounts Pre-tax commuter and parking benefits 401(k) Savings and Investment Plan with company match Paid time off: Flexible Vacation is provided to all eligible employees assigned to a salaried (non-overtime eligible) position. Accrued Vacation is provided to all other employees eligible for vacation benefits. For employees working at least 35 hours per week, the vacation accrual rate is 13 days annually for the first three years of employment and 18 days annually for subsequent years of employment. Vacation accrual is prorated for employees working between 20 and 34 hours per week. Employees working fewer than 20 hours per week are not eligible for vacation. 11 paid holidays Paid sick leave: 72 hours of paid sick leave upon date of hire. Refreshes each calendar year. Unused balance will carry over each year up to a maximum cap of 112 hours. Paid parental leave Adoption assistance Employee Stock Purchase Plan Financial planning and group legal Voluntary benefits including auto, homeowner and pet insurance" We need to break into list items. Could group similar but keep each distinct. Let's create list: - Medical, dental, and vision insurance, including expert medical opinion - Short term disability and long term disability - Life insurance and AD&D - Supplemental life insurance (Employee/Spouse/Child) - Health care and dependent care Flexible Spending Accounts - Pre-tax commuter and parking benefits - 401(k) Savings and Investment Plan with company match - Paid time off: Flexible Vacation is provided to all eligible employees assigned to a salaried (non-overtime eligible) position. Accrued Vacation is provided to all other employees eligible for vacation benefits. For employees working at least 35 hours per week, the vacation accrual rate is 13 days annually for the first three years of employment and 18 days annually for subsequent years of employment. Vacation accrual is prorated for employees working between
. Skills: Job Skills: People Leadership / Management Experience: 3 years of experience in a leadership role with or without direct reports. Product Domain Experience: 6 years of experience in the relevant product domain (e.g., procurement, accounting, healthcare). Agile Methods Experience: 2 years of experience in applying agile methodologies and practices (e.g., Scrum framework) to manage projects. Customer Interaction Experience: 5 years of experience in customer interaction. Certification: Product management or product domain related certifications (e.g., SAFe Scrum Master Certification, SAFe Product Owner/Product Manager Certification, Project Management Professional Certification, American Production and Inventory Control Society [APICS] Certifications). We can format as