Principal Technical Program Manager (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. Remove boilerplate etc. Preserve all substantive info. We need to decide which sections to include based on content. From posting: - Intro paragraph about Global Program Controls organization, role description: could be "About the role" or maybe "Overview". Use

  About the role

  with paragraph. - "What You Will Do As a Technical Program Manager, you will:" then bullet list: "You will assist will the end-to-end delivery of multiple data center infrastructure projects concurrently." (typo but keep). Then bullet list: Risk Management, Project Management, Project Planning, Stakeholder Communication, Use analytical methods... So these are duties. Could be under

  Responsibilities

  with
  . - Then "Responsibilities Minimum Qualifications" heading appears weird: after bullet list there is "Responsibilities Minimum Qualifications". Actually the posting shows: Responsibilities Minimum Qualifications 4+ years of experience supporting data center build... Probably they intended "Minimum Qualifications". So we need a section for Minimum Qualifications (maybe under Requirements). Use

  Minimum Qualifications

  with list. - Then "Preferred Qualifications" list. - Then "Qualifications Disclaimer: ..." That's boilerplate (disclaimer). Should remove. - Then "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." That's Pay info. So we need a Pay section. - Then "Oracle maintains broad salary ranges..." etc. That's more pay context but we can keep as prose under Pay. - Then "Oracle US offers a comprehensive benefits package which includes the following:" then list of benefits. So Benefits section. - Then "The role will generally accept applications for at least three calendar days..." that's application instruction, remove. - Then "As part of Oracle's onboarding process..." that's boilerplate, remove. - Then "About Us" paragraph about Oracle. Could be "About the company" but we have only sections allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Us" maybe not needed; but we could put under "About the role"? However we already have About the role for role description. The About Us is company description; maybe we can include as a paragraph under About the role or maybe we can omit because not required sections. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". About Us is real content, but not in allowed headings list? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. About Us is not listed, but we could still use About the role? Might be okay to include About the role covering both role and company? But we already used About the role for role description. Could we add another heading like "About Oracle"? Not in list; better to avoid extra headings not in list. So we might omit About Us or incorporate into About the role as extra paragraph. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should stick to those. Thus sections: - About the role: includes intro paragraph and maybe What You Will Do? Actually What You Will Do is responsibilities; better to put under Responsibilities. Thus About the role: short paragraph describing the organization and role overview. - Responsibilities: list of duties (What You Will Do bullet points). Use

  • . - Minimum Qualifications: list. - Preferred Qualifications: list. - Benefits: list. - Pay: paragraph with salary range and bonus/equity note, plus maybe additional pay context. - Schedule: maybe not present; there is mention "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/travel. Could be considered Schedule section. The posting does not explicitly state schedule but gives work hours and travel. So we can include Schedule section with that info. - Requirements: maybe we could combine Minimum and Preferred Qualifications under Requirements? But we already have separate sections for Minimum and Preferred Qualifications. The allowed headings include Requirements and Qualifications. Could treat Minimum Qualifications as Requirements, Preferred Qualifications as Qualifications. Or we could have Requirements (minimum) and Qualifications (preferred). Let's map: - Requirements: Minimum Qualifications. - Qualifications: Preferred Qualifications. Thus we have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not repeat job title as heading. Now we need to preserve all substantive information. Let's extract. About the role: The first paragraph: "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. In this role, you will be a TPM within the Data Center Delivery organization and oversee and assist the end-to-end execution of large-scale data center infrastructure projects. Your ability to anticipate and mitigate risks to data center delivery will be crucial in maintaining project predictability. The role comes with a high degree of personal accountability and autonomy and will require effective engagement across various stakeholders including design, engineering, operations, supply chain, and network delivery." We can put that as

    . Responsibilities: The bullet list after "What You Will Do As a Technical Program Manager, you will:" includes: - You will assist will the end-to-end delivery of multiple data center infrastructure projects concurrently. - Risk Management: Identify potential risks and develop mitigation strategies to minimize impact on project timelines and costs. - Project Management: Oversee all phases of build, ensuring they are completed on time, within budget, and to the required quality standards. - Project Planning: Develop and implement long-term strategies aimed at reducing complexity and increasing speed of delivery for data center infrastructure projects. - Stakeholder Communication: Maintain clear and effective communication with internal and external stakeholders, providing regular updates on project status and addressing any concerns. - Use analytical methods and AI-enabled capabilities responsibly to identify patterns, exceptions, emerging risk, stale information, and forecast instability; validate findings with accountable project and functional owners before presenting conclusions. We need to keep each as

  • . Note the first bullet has a typo "assist will". Keep as is. Requirements (Minimum Qualifications): list: - 4+ years of experience supporting data center build, fitout, commissioning, readiness, construction, capital delivery, hyperscale cloud, colocation, or mission-critical facilities programs. - 4+ 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. - 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. - This is an onsite role in Nashville, TN. Note: The last two bullet points about onsite and travel maybe also schedule but we already have them in Minimum Qualifications; but we might duplicate. However we should preserve all info; we can keep them in Requirements and also maybe in Schedule? But that would duplicate. Better to keep them only once. Since they are qualifications (location, travel). We could keep them under Requirements. Then Schedule section could be empty? But we must not create empty sections. So maybe we should not have a Schedule section if the info is already covered under Requirements. However the instruction: "Prefer a few substantive sections over many thin ones." So we could omit Schedule if its content is already covered elsewhere. But we need to check if any schedule-specific info not captured: The posting also mentions "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 location/travel. Could be considered Schedule. But we already have that in Requirements. If we put Schedule section we would duplicate. Better to keep it under Requirements and not have Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now Benefits: list from "Oracle US offers a comprehensive benefits package which includes the following:" then list items: - 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 keep each as
  • . Some items have internal colons and sentences; still fine as
  • text. Pay: "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. 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." We can put as

    . Now we need to ensure we removed boilerplate: disclaimer, About Us, EEO, etc. Also remove lines like "The role will generally accept applications..." etc. Now produce HTML fragment: no or .