Principal Technical Program Manager- Global Program Data and Insights (Nashville, TN)

We need to output HTML fragment with sections: headings

for sections like 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. Preserve all substantive info; remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the job description and extract sections: "About the role" maybe from first paragraph? The description includes "Job Description" then paragraphs about Global Program Controls etc. Could treat that as "About the role". Then "What You Will Do" includes bullet-like paragraphs (Data Product and Insight Development, Final Mile Recovery and Execution Support, Tooling and Continuous Improvement). Those could be under Responsibilities? Actually there is a separate "Responsibilities" heading later. The "What You Will Do" seems like responsibilities. Then there is a "Responsibilities" section later with "This is a full-time onsite role in Nashville, TN." That's more about location and schedule. Then "Minimum Qualifications", "Preferred Qualifications", "Success in This Role", "Qualifications Disclaimer", "Range and benefit information", "About Us". Also "Pay" and "Schedule" maybe from the Responsibilities section: "Ability to work on-site in Nashville, Tennessee, during standard daytime business hours; candidates must be based in or willing to relocate to Nashville. Ability to travel up to 30% for global site visits, working sessions, and critical delivery events." That's schedule/location. Pay info: "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $90,100 - $209,500 per year. May be eligible for bonus and equity." So we need Pay section. Benefits: list of benefits after "Oracle US offers a comprehensive benefits package which includes the following:" then bullet list. We need to avoid boilerplate like EEO, legal, etc. Remove "Qualifications Disclaimer", "About Us" maybe? The "About Us" is generic corporate fluff; but it's substantive? It's about Oracle mission. Might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" is not explicitly listed but could be considered generic marketing; but it's not EEO. Might keep? However they said prefer few substantive sections over many thin ones. Could combine "About the role" and "About Us"? Probably keep "About the role" as description of role; "About Us" maybe not needed. But we need to preserve ALL substantive information; not invent or summarize away detail. So we must keep all substantive info, but we can omit boilerplate. "About Us" is substantive? It's about Oracle's mission; could be considered boilerplate but it's not legal. Might keep as a section? But they said prefer few substantive sections; maybe we can incorporate into "About the role". However the instruction: "Prefer a few substantive sections over many thin ones." So we could have sections: About the role (combining initial description and About Us?), Responsibilities (What You Will Do + Responsibilities bullet?), Requirements (Minimum Qualifications + Preferred Qualifications?), Benefits, Pay, Schedule. That seems reasonable. We must not create sections with filler text. Ensure each section has real content. Let's extract content: About the role: The first paragraph(s) before "What You Will Do": "The Global Program Controls organization provides governance, reporting, controls processes, cost management support, and portfolio visibility to help Oracle Cloud Infrastructure deliver global data center programs with greater consistency, transparency, and execution discipline. Oracle Cloud Infrastructure is seeking a principal-level individual contributor to work within Strategic Operations & Execution (SO&E), an execution-assurance organization within Global Program Controls. This role will support final-mile recovery while turning complex, distributed delivery data into clear, decision-ready insights that help project teams identify risk earlier, focus intervention, and improve delivery predictability. The successful candidate combines deep technical program or project-management experience with exceptional data fluency. They will work across Oracle Primavera Cloud, Confluence, Jira, approved reporting environments, home-grown tools, and emerging AI capabilities to create a coherent view of schedules, milestones, dependencies, risks, actions, decisions, and delivery outcomes. The role works alongside build TPMs and functional teams to strengthen execution without transferring their delivery accountability." That's substantive. Responsibilities: Combine "What You Will Do" subsections and the later "Responsibilities" paragraph (which is about full-time onsite role). Actually the later "Responsibilities" heading includes: "This is a full-time onsite role in Nashville, TN." That's more about schedule/location; but we could treat that under Schedule. However we already have a Schedule section later. Let's parse: Under "What You Will Do": three bullet-like sections: - Data Product and Insight Development (paragraphs) - Final Mile Recovery and Execution Support (paragraphs) - Tooling and Continuous Improvement (paragraphs) Then later there is a heading "Responsibilities" with: "This is a full-time onsite role in Nashville, TN." That's just a sentence about location; maybe we treat that under Schedule. Thus Responsibilities section will contain the three subsections as list items? Could be

  • each subsection heading as ? But we need to use
    • for any list of duties/requirements/benefits. So we can make each duty as a list item. Within each list item we can have

      for prose. Thus:

      Responsibilities

      • Data Product and Insight Development

        ...

      • Final Mile Recovery and Execution Support

        ...

      • Tooling and Continuous Improvement

        ...

      Now Requirements: Could combine Minimum Qualifications and Preferred Qualifications? Or separate sections: Requirements (Minimum Qualifications) and Qualifications (Preferred). But they said use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have:

      Requirements

      for Minimum Qualifications (the list). Use
      • for each qualification line. Then

        Qualifications

        for Preferred Qualifications. Alternatively we could have Skills section for certifications etc. But we have Preferred Qualifications includes certifications. Could treat as Skills. But we need to avoid thin sections; maybe combine Minimum and Preferred into Requirements? But they'd be mixed. Better to follow instruction: Use headings for sections when posting has real specific content. The posting has Minimum Qualifications and Preferred Qualifications separate. So we can have both. Thus:

        Requirements

        • 8+ years of progressively responsible technical program management, project management, program controls, business intelligence, analytics, or comparable experience in complex, cross-functional environments.
        • Demonstrated ability to work with complex, multi-source operational data and translate it into clear program insights, prioritized actions, and executive-ready communication.
        • Strong command of project controls, including schedules, milestones, risks/issues, actions, dependencies, forecasts, and performance reporting.
        • Experience with enterprise delivery and collaboration tools such as Primavera Cloud or comparable scheduling platforms, Jira, Confluence, reporting/analytics tools, and internally developed applications.
        • Experience applying multi-source operational data analytics, data integrity and health practices, workflow automation, and AI-enabled analysis to improve delivery insight and execution.
        • Strong analytical judgment and problem-solving skills, including the ability to evaluate data quality, reconcile conflicting signals, and distinguish patterns from isolated exceptions.
        • Excellent written and verbal communication skills, with the ability to explain complex data and technical concepts in clear business language.
        • Ability to work on-site in Nashville, Tennessee, during standard daytime business hours; candidates must be based in or willing to relocate to Nashville.
        • Ability to travel up to 30% for global site visits, working sessions, and critical delivery events.
        • Bachelor’s degree in engineering, construction management, information technology, data/analytics, business, or a related field; or equivalent practical experience.
        Then

        Qualifications

        for Preferred Qualifications:
        • Experience supporting data center build, fitout, commissioning, readiness, construction, capital delivery, hyperscale cloud, colocation, or mission-critical facilities programs.
        • Experience developing metrics, dashboards, data models, reporting products, or data-governance practices for a complex operational portfolio.
        • Practical experience applying AI-assisted analysis or automation to improve operational reporting, insight generation, data discovery, or workflow efficiency, with appropriate validation and governance.
        • Experience developing or improving workflow automation, data-health controls, and AI-enabled operational analysis for a complex delivery environment.
        • PMP, PRINCE2, Lean/Six Sigma, Agile, data/analytics, or comparable professional certification.
        Now Benefits: list from Oracle US offers a comprehensive benefits package. We need to extract each benefit item: - 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 put each as
      • . Some are long sentences; okay. Pay:

        Pay

        with

        containing the range and bonus/equity info. Schedule:

        Schedule

        with

        containing onsite requirement and travel. We also have "Success in This Role" paragraph; could be under Responsibilities or a separate section like "Success Metrics". But we have no heading for that in list; but we could incorporate into Responsibilities as additional list item? However it's not a duty but a success metric. Could be its own section "Success". But headings list includes Skills, Benefits, Pay, Schedule; not Success. But we could add a section "Success" if we want, but they said prefer few substantive sections. Might incorporate into Responsibilities as a note. However we must preserve ALL substantive information; we can't omit it. So we need to include it somewhere. Could add a

        Success Metrics

        but not in allowed headings list? The instruction says use

        for section headings (e.g. About the