Senior Principal Technical Program Manager-Data Center Infrastructure Delivery (Nashville, TN)
Oracle · United States · 1 mo ago
RemoteRemoteProject Management$115k–$235k/yrFull-time
We need to output only HTML fragment, using for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info.
We need to parse the job description.
Key sections:
- About the role: The first paragraph(s) describing role: "The Global Program Controls organization provides governance..." etc. That's about role.
- Responsibilities: The "Responsibilities" section includes bullet list items. We need to extract responsibilities.
- Skills: There's a "Required Skills" section with bullet list.
- Qualifications: There's a "Qualifications" section with disclaimer and maybe other qualifications? It includes a disclaimer about immunization etc. Also includes "This is an onsite position in Nashville, TN." That could be part of Qualifications or maybe Schedule? Actually schedule: onsite position. Could be Schedule? But schedule is about work schedule (full-time etc). Not given. So we may not include Schedule unless there is info. There's no explicit schedule like full-time, part-time. So we skip Schedule.
- Pay: There's "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $114,600 - $234,600 per year. May be eligible for bonus, equity, and compensation deferral." That's pay info. So we can include Pay section.
- Benefits: There's a long list of benefits after "Oracle US offers a comprehensive benefits package which includes the following:" So we include Benefits.
- Requirements: Might be similar to Qualifications? The posting includes "Qualifications" heading but also "Required Skills". The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. Usually "Requirements" could be qualifications like education, experience. But the posting doesn't have explicit requirements besides qualifications disclaimer and onsite location. Could treat "Qualifications" as the qualifications section (including disclaimer and onsite). "Requirements" maybe could be empty; we should not create empty heading. So we omit Requirements if no specific content.
- Skills: we have Required Skills.
- About the role: we have introductory paragraphs.
Thus sections: About the role, Responsibilities, Skills, Qualifications, Benefits, Pay.
We must not include Schedule.
We need to format:
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info.
We need to parse the job description.
Key sections:
- About the role: The first paragraph(s) describing role: "The Global Program Controls organization provides governance..." etc. That's about role.
- Responsibilities: The "Responsibilities" section includes bullet list items. We need to extract responsibilities.
- Skills: There's a "Required Skills" section with bullet list.
- Qualifications: There's a "Qualifications" section with disclaimer and maybe other qualifications? It includes a disclaimer about immunization etc. Also includes "This is an onsite position in Nashville, TN." That could be part of Qualifications or maybe Schedule? Actually schedule: onsite position. Could be Schedule? But schedule is about work schedule (full-time etc). Not given. So we may not include Schedule unless there is info. There's no explicit schedule like full-time, part-time. So we skip Schedule.
- Pay: There's "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $114,600 - $234,600 per year. May be eligible for bonus, equity, and compensation deferral." That's pay info. So we can include Pay section.
- Benefits: There's a long list of benefits after "Oracle US offers a comprehensive benefits package which includes the following:" So we include Benefits.
- Requirements: Might be similar to Qualifications? The posting includes "Qualifications" heading but also "Required Skills". The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. Usually "Requirements" could be qualifications like education, experience. But the posting doesn't have explicit requirements besides qualifications disclaimer and onsite location. Could treat "Qualifications" as the qualifications section (including disclaimer and onsite). "Requirements" maybe could be empty; we should not create empty heading. So we omit Requirements if no specific content.
- Skills: we have Required Skills.
- About the role: we have introductory paragraphs.
Thus sections: About the role, Responsibilities, Skills, Qualifications, Benefits, Pay.
We must not include Schedule.
We need to format: About the role
then
...
for prose. For lists:- ...