Senior Data Hall Designer
Oracle · Nashville, TN · 4 wk ago
Information Technology$102k–$210k/yrFull-time
We need to output HTML fragment with sections: h3 headings for sections present with specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate. The posting includes "Key Responsibilities JOB DESCRIPTION ..." then many responsibilities. Then later "RESPONSIBILITIES Key Responsibilities ..." duplicates? Actually there are two sets: first "Key Responsibilities JOB DESCRIPTION ..." then later "RESPONSIBILITIES Key Responsibilities ..." which seems similar but with slightly different wording (Assists vs Leads). We need to preserve all substantive info, not duplicate lines? The instruction: "Remove duplicated lines". So we need to deduplicate overlapping responsibilities. We need to combine unique content.
We have sections: Responsibilities (maybe combine both sets). Also there is a "QUALIFICATIONS" section with disclaimer and range info. Also maybe "Benefits", "Pay", "Schedule"? The posting includes "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $102,300 - $209,500 per year." That's pay info. Also maybe benefits? Not explicit besides range. No schedule. So we should include a Pay section with that range. Benefits? Not mentioned besides "Range and benefit information". Could infer benefits but not specific; we should not create Benefits unless specific content. So only Pay.
We also have "Core Responsibilities" subsections under responsibilities? Actually after responsibilities there is "Core Responsibilities Planning & Execution: ..." etc. Those seem like generic competency sections. They might be considered part of responsibilities or qualifications? They are more like behavioral competencies. The instruction: include a section only when posting has real, specific content for it. These are generic but still content. Could be placed under a "Core Competencies" heading? But we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "Core Competencies". So we might incorporate those into Responsibilities or Skills? Probably they belong under Responsibilities (they describe expected behaviors). We'll include them under Responsibilities as bullet points.
We also have "Network Expertise", "Automation" etc under responsibilities.
Thus we will produce:
Responsibilities
- ... many items ...