Director, Platform Software Engineering
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. The posting includes many responsibilities, qualifications, benefits, pay range, etc. No explicit schedule. So we can have sections: Responsibilities, Qualifications, Benefits, Pay. Possibly also "About the role" (the initial description before Responsibilities). The job description starts with "Job Description Leads a platform group; develops strategies..." That is about the role. So we can put that in About the role
with a
. Then Responsibilities: we have many bullet-like sentences. We need to use
- for any list of duties/requirements/benefits. So we can extract responsibilities as list items. Could group them but we can just list each sentence as
- . Ensure we preserve all substantive info. Do not repeat job title. Do not include metadata like Job ID. Remove boilerplate: EEO, accommodation request, etc. Also remove "Disclaimer: Certain U.S. based..." maybe that's part of qualifications? It's a disclaimer about immunization etc. Might be considered boilerplate? It's not EEO but it's a disclaimer about requirements. Might be considered part of qualifications? It says "Certain U.S. based or U.S. customer or client-facing roles may be required to comply with applicable requirements, such as immunization/occupational health mandates, and/or drug testing requirements." That's substantive? It's a condition. Might keep as part of Qualifications? But it's a disclaimer; maybe we keep it as a note under Qualifications. However instructions: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a legal disclaimer about immunization etc. Might be considered legal boilerplate. Safer to remove it. Also remove "The role will generally accept applications..." that's application instruction, remove. Also remove "As part of Oracle's onboarding process..." that's also boilerplate. Remove "About Us" section? That's about company, maybe we can keep as "About the role"? Actually "About Us" is company description; could be considered boilerplate but it's substantive about Oracle. Might keep as a separate section? Not listed as allowed headings but we could put under About the role? The instructions say use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role. The "About Us" could be part of About the role? Probably we can incorporate that into About the role paragraph. But we must preserve all substantive information; we can include it in About the role
. However we must not repeat job title. So we can combine the initial job description and the About Us paragraph into About the role. Now Responsibilities: we need to extract all responsibilities from the text. The responsibilities section includes many bullet-like sentences under headings: Platform Software Development, Software Development and Coding..., Software Architecture..., Issue/Defect Collaboration..., Practices and Standards Compliance..., Development Operations..., Core Responsibilities (Planning & Execution, Collaboration & Partnership, Problem Solving, Continuous Learning, Continuous Improvement, Performance and Development). We need to list each duty as
- . We'll need to parse the text and create list items.
We must not invent or summarize away detail. So we need to keep each sentence essentially. Could be many items; that's okay.
Qualifications: The posting includes a "Qualifications" heading then a disclaimer (which we may remove) and then "Range and benefit information..." Actually that's under Qualifications? The text shows:
Qualifications Disclaimer: Certain U.S. based ... Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $122,500 - $355,400 per year. May be eligible for bonus, equity, and compensation deferral. Oracle maintains broad salary ranges... Candidates are typically placed into the range based on the preceding factors as well as internal peer equity. Oracle US offers a comprehensive benefits package which includes the following: [list]. Then later benefits details.
Thus qualifications section may be empty of actual qualifications (like education, experience). The posting didn't list specific qualifications like degree, years experience. So we may not have a Qualifications section with substantive content. According to instructions: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Since there are no explicit qualifications (like required education, experience), we should omit Qualifications heading. However we have pay and benefits info; those go under Pay and Benefits sections.
Pay: we have hiring range $122,500 - $355,400 per year, plus bonus, equity, compensation deferral. So we can create Pay section with that info.
Benefits: we have a comprehensive list: Medical, dental, vision insurance, etc. We'll list as
- .
Schedule: not mentioned, so omit.
Skills: not explicitly listed; maybe we can omit.
Requirements: not explicitly listed; maybe we can omit.
Thus final HTML:
About the role
... combined description ...
Responsibilities
- ... each responsibility ...
Pay
...
Benefits
- ...
- .
Schedule: not mentioned, so omit.
Skills: not explicitly listed; maybe we can omit.
Requirements: not explicitly listed; maybe we can omit.
Thus final HTML: