Postdoctoral Research Associate - Coastal Landscape Geospatial Modeling
Oak Ridge National Laboratory · Oak Ridge, TN · 1 mo ago
ManagementFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID heading. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info.
We need to parse the posting.
Key content:
Overview: description of role, project, duties.
Major Duties/Responsibilities: list of duties.
Basic Qualifications: list.
Preferred Qualifications: list.
Contact for Position: Ben Sulman (email)
Special Requirements: PhD time limit, appointment length up to 24 months, potential extension, subject to performance/funding, need three letters of reference, instructions to upload docs, Real ID compliant ID, PIV card requirement, background check, foreign national residency requirement.
About ORNL: description of lab, benefits list.
Pay: not mentioned explicitly. No pay info. So we should NOT include Pay section.
Schedule: not mentioned. No schedule.
Benefits: ORNL offers competitive pay and benefits programs, list of benefits. So we can include Benefits section with list.
Skills: maybe we can include under Qualifications? The instruction says use headings for Skills if there is content. We have qualifications (basic and preferred). Could combine into Requirements and Qualifications? The headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use.
We have overview (About the role). Responsibilities (Major Duties/Responsibilities). Requirements (Basic Qualifications). Qualifications (Preferred Qualifications). Skills maybe not separate; could embed in Qualifications. But we could still include Skills if we have specific skills like programming in Python, AI/ML, etc. However those are already in qualifications. To avoid duplication, maybe we just use About the role, Responsibilities, Requirements, Qualifications, Benefits. That's acceptable: we only include sections with real content.
We must not include placeholder text like "commensurate with experience". Not present.
We must output only HTML fragment, no /, no markdown fences.
Let's craft:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID heading. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info.
We need to parse the posting.
Key content:
Overview: description of role, project, duties.
Major Duties/Responsibilities: list of duties.
Basic Qualifications: list.
Preferred Qualifications: list.
Contact for Position: Ben Sulman (email)
Special Requirements: PhD time limit, appointment length up to 24 months, potential extension, subject to performance/funding, need three letters of reference, instructions to upload docs, Real ID compliant ID, PIV card requirement, background check, foreign national residency requirement.
About ORNL: description of lab, benefits list.
Pay: not mentioned explicitly. No pay info. So we should NOT include Pay section.
Schedule: not mentioned. No schedule.
Benefits: ORNL offers competitive pay and benefits programs, list of benefits. So we can include Benefits section with list.
Skills: maybe we can include under Qualifications? The instruction says use headings for Skills if there is content. We have qualifications (basic and preferred). Could combine into Requirements and Qualifications? The headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use.
We have overview (About the role). Responsibilities (Major Duties/Responsibilities). Requirements (Basic Qualifications). Qualifications (Preferred Qualifications). Skills maybe not separate; could embed in Qualifications. But we could still include Skills if we have specific skills like programming in Python, AI/ML, etc. However those are already in qualifications. To avoid duplication, maybe we just use About the role, Responsibilities, Requirements, Qualifications, Benefits. That's acceptable: we only include sections with real content.
We must not include placeholder text like "commensurate with experience". Not present.
We must output only HTML fragment, no /, no markdown fences.
Let's craft:
About the role
... overview text ...
Responsibilities
- ... ...
Requirements
- Basic Qualifications items ...
Qualifications
- Preferred Qualifications items ...
Benefits
- list of benefits ...
About the role
... overview ...
Contact: Ben Sulman (sulmanbn@ornl.gov)
Responsibilities
- ...
Requirements
- ... basic qualifications ...
Special requirements: ... (list)
Qualifications
- ... preferred qualifications ...
Benefits
- ... benefits list ...