Supply Chain Operations– Principal Supply Demand Planner 4

We need to output HTML fragment with sections: About the role? The description includes "Job Description Oracle is seeking a Principal-level Supply/Demand Planner...". The first paragraph is about the role. We'll treat that as "About the role". Then "Responsibilities" with bullet list from "What You’ll Do". Then "Requirements" maybe combine "What We’re Looking For" and "Minimum Qualifications" and "Preferred Qualifications". But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. We have content for About the role, Responsibilities, Requirements (maybe combine Minimum Qualifications), Qualifications (maybe Preferred Qualifications?), Skills (expert-level Excel, planning, analytical). Benefits (detailed). Pay (range). Schedule? Not mentioned. So we omit Schedule. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, legal, etc. Also remove "About Us" maybe? That's not required but could be considered boilerplate? It's about company, not job specifics. Probably remove. Also remove "Career Level - IC4". Remove "The role will generally accept applications..." etc. Remove disclaimer about immunization? That's maybe part of Qualifications? It's a qualifier but could be included under Qualifications? It's a disclaimer about certain US roles may be required to comply with immunization etc. Might be considered boilerplate? It's specific to role but maybe keep under Qualifications? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a legal disclaimer about immunization/occupational health mandates, drug testing. Might be considered legal boilerplate; safer to remove. Also remove "Range and benefit information provided in this posting are specific to the stated locations only". That's part of Pay/Benefits but we can keep the range and benefits. The sentence about range being specific to locations is meta; we can keep the range and benefits but maybe drop that sentence. We'll keep the range and benefits details. We need to preserve all substantive information. So we need to include the bullet points from Responsibilities, the bullet points from What We’re Looking For, Minimum Qualifications, Preferred Qualifications, Skills (maybe combine), Benefits details, Pay range. We must not invent or summarize away detail. So we need to keep each bullet as is. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not emit a heading followed by filler/placeholder text. So ensure each section has real content. We'll structure:

  About the role

  Oracle is seeking a Principal-level Supply/Demand Planner to drive end-to-end planning for assigned products, partnering with Sourcing, Demand Management, Finance, and suppliers to build resilient supply plans, optimize inventory strategies, and quickly resolve supply-demand imbalances that impact revenue, customer delivery, and margin. This is a highly visible role for a self-directed planner who can operate independently, lead cross-functional execution, and communicate forward-looking supply capability to senior leadership in a fast-paced, ambiguous environment.

  Responsibilities

  • Develop and own supply plans in partnership with Sourcing Management, Demand Management, and suppliers to meet customer and business commitments.
  • Create inventory strategies (targets, buffers, risk mitigation approaches) that balance service levels, cost, and working capital.
  • Identify and resolve supply-demand gaps (shortages/excess) and lead cross-functional teams to drive corrective actions that protect revenue and margin.
  • Assess forward-looking revenue capability and supply risk, providing clear insights and scenarios to senior leadership for decision-making.
  • Coordinate supply allocations when required, partnering with internal teams and suppliers to optimize outcomes and ensure fair, transparent execution.
  • Present business results and recommendations to stakeholders across Supply Chain, Finance, and business units—translating complex analysis into actionable plans.
  • Improve planning processes and systems by contributing to the design, development, and evaluation of new tools, metrics, and operating rhythms.
  • Mentor and guide junior planners, providing direction, specialist knowledge, and training; support senior planners and management on ad-hoc initiatives.
  • Build strong stakeholder relationships across Oracle lines of business and external suppliers, influencing without authority to drive alignment and results.
  Now we need a section for Requirements? Could combine Minimum Qualifications and maybe also "What We’re Looking For" as Requirements? But we also have Skills section. The instruction: Use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - What We’re Looking For: Strong planning and analytical capability, etc. That's more like Skills/Requirements. - Minimum Qualifications: Bachelor’s degree, 7+ years experience, etc. - Preferred Qualifications: 10+ years experience, etc. We could put Requirements as Minimum Qualifications (maybe plus Preferred?). Qualifications could be Preferred Qualifications? Or we could treat Requirements as both Minimum and Preferred? But we need to avoid duplication. Let's decide: Requirements: Minimum Qualifications (the must-haves). Qualifications: Preferred Qualifications (nice-to-haves). Skills: The specific skills like expert-level Excel, planning, analytical, commodity planning, influencing, communication, continuous improvement. But the "What We’re Looking For" includes many skill-like items. We'll put those under Skills. Thus:

  Requirements

  • Bachelor’s degree in Business Management, Supply Chain Management, Computer Science, or similar (or equivalent experience).
  • 7+ years of experience in Supply/Demand Planning, Sourcing, or broader supply chain leadership (preferably in a related industry).
  • Demonstrated experience communicating progress, risks, and recommendations to cross-functional and senior leadership audiences.
  • Expert-level Excel skills (advanced modeling, pivots, forecasting/scenario analysis).
  But note that expert-level Excel also appears in Skills; we might duplicate. However we need to preserve all substantive information; if we list it under Requirements, we still need to include it under Skills? The instruction says preserve ALL substantive information; not necessarily avoid duplication across sections, but we should not invent or summarize away detail. Duplication is okay if it's in the source. However the source lists expert-level Excel skills twice: once in What We’re Looking For and once in Minimum Qualifications. We could keep it only once under Requirements (or Skills) but then we would be dropping one occurrence. That would be summarizing away detail? It's duplicate info; removing one duplicate still preserves the information (the skill is still present). It's not losing substantive info; it's just removing redundancy. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Removing a duplicate does not lose substantive info; the info is still there. So we can deduplicate. Thus we can place expert-level Excel under Requirements (as it's a minimum qualification). Then Skills can include the other skill items from What We’re Looking For: Strong planning and analytical capability, complex/statistical data analysis, scenario modeling, structured problem solving, commodity planning experience (Memory storage Electronics commodity planning experience), ability to align across PMs and supply types, proven ability to influence cross-functional partners, lead through ambiguity, drive outcomes, excellent communication, presentation, stakeholder management skills, continuous improvement mindset. We need to keep the exact phrasing? We should preserve the substance but not necessarily exact wording? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the details, but we can rephrase slightly as long as we don't lose detail. Safer to keep the original phrasing. Thus Skills section bullet list: - Strong planning and analytical capability, including complex/statistical data analysis, scenario modeling, and structured problem solving. - Commodity planning experience (Memory storage Electronics commodity planning experience). - Must be able to align across PMs and supply types to align and ensure our contract manufacturers are getting the right signal at the right time. - Proven ability to influence cross-functional partners, lead through ambiguity, and drive outcomes in a dynamic environment. - Excellent communication, presentation, and stakeholder management skills (from working teams through executive discussions). - Continuous improvement mindset—comfortable standardizing processes, defining metrics, and simplifying workflows. Note: The phrase "Must be able to align across PMs and supply types to align and ensure our contract manufacturers are getting the right signal at the right time." is a bit awkward but we keep. Now Benefits: we need to list the benefits as bullet list. The posting includes a long list. We'll capture all. We need to exclude the sentence: "Range and benefit information provided in this posting are specific to the stated locations only". We'll keep the benefits list. Thus Benefits section:

  Benefits

  • 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
  Pay: we need to include the range and mention bonus/equity eligibility. Thus:

  Pay

  US: Hiring Range in USD from: $102,300 - $209,500 per year. May be eligible for bonus and equity.

  We could also note that Oracle maintains broad salary ranges etc. That's substantive? It's explanatory; we could include but it's not required. Might be considered boilerplate? It's about salary ranges; it's part of the posting. We'll keep it as a paragraph after the range. Thus Pay section:

  Pay

  US: Hiring Range in USD from: $102,300 - $209,500 per year. May be eligible for bonus and equity. Oracle maintains broad salary ranges for its roles in order to account for variations in knowledge, skills, experience, market conditions and locations, as well as reflect Oracle's differing products, industries and lines of business. Candidates are typically placed into the range based on the preceding factors as well as internal peer equity.

  Now we need to ensure we didn't include any boilerplate like EEO, etc. We removed those. Check for any leftover boilerplate: The "About Us" paragraph we removed. The "Career Level - IC4" removed. The "The role will generally accept applications..." removed. The "Disclaimer: Certain U.S