Insider Threat Investigator
Los Alamos National Laboratory · Los Alamos, NM · 1 mo ago
Information TechnologyFull-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 as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning). Also remove duplicated lines, application instructions. Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes benefits description under "Our generous benefits package includes:" So we can include Benefits section. Pay? Not mentioned. Schedule? Not mentioned (though mentions flexible schedules and time off (PTO) under benefits). So schedule not separate. So we can have sections: About the role (maybe from first paragraph), Responsibilities (the list after "In this position, you will:"), Requirements (minimum job requirements), Qualifications (desired qualifications), Skills (maybe communication and interpersonal skills, analysis etc). Could combine some. But we need to follow rule: prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But they ask to use headings for those categories if content exists. We'll decide to include About the role, Responsibilities, Requirements, Qualifications, Benefits. Possibly Skills as part of Requirements/Qualifications. But we can include Skills if there is distinct content: there is "Analysis, Reports, and Briefings", "Communication And Interpersonal Skills". Those could be Skills. However we might combine them into Requirements. To avoid many thin sections, we could have: About the role, Responsibilities, Requirements (includes minimum job requirements, desired qualifications, analysis, communication skills), Benefits. That's four sections.
We must not include filler like "Position commitment: Regular appointment employees..." that's maybe not needed? It's substantive but maybe not a section. Could be included in About the role or Requirements? It's about eligibility. Might be considered part of Requirements? Could be included in About the role as note. But we need to preserve all substantive info. We'll embed that info in About the role or Requirements as a paragraph.
We must remove boilerplate: EEO, equal opportunity, drug test, clearance details? Clearance is substantive (required). Should keep. The note about citizenship restrictions is substantive. We'll keep that in Requirements or About the role.
We must not include application instructions like "Note to Applicants: With your application..." That's application instructions, should be removed. Also "Although the position will not ordinarily require extensive travel..." that's maybe not application instruction but could be considered job detail; it's about travel requirement. Might be kept as part of Responsibilities or About the role. It's not application instruction. We'll keep.
We must not include duplicated lines. We'll ensure no repeats.
Now craft HTML.
Structure:
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 as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning). Also remove duplicated lines, application instructions. Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes benefits description under "Our generous benefits package includes:" So we can include Benefits section. Pay? Not mentioned. Schedule? Not mentioned (though mentions flexible schedules and time off (PTO) under benefits). So schedule not separate. So we can have sections: About the role (maybe from first paragraph), Responsibilities (the list after "In this position, you will:"), Requirements (minimum job requirements), Qualifications (desired qualifications), Skills (maybe communication and interpersonal skills, analysis etc). Could combine some. But we need to follow rule: prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But they ask to use headings for those categories if content exists. We'll decide to include About the role, Responsibilities, Requirements, Qualifications, Benefits. Possibly Skills as part of Requirements/Qualifications. But we can include Skills if there is distinct content: there is "Analysis, Reports, and Briefings", "Communication And Interpersonal Skills". Those could be Skills. However we might combine them into Requirements. To avoid many thin sections, we could have: About the role, Responsibilities, Requirements (includes minimum job requirements, desired qualifications, analysis, communication skills), Benefits. That's four sections.
We must not include filler like "Position commitment: Regular appointment employees..." that's maybe not needed? It's substantive but maybe not a section. Could be included in About the role or Requirements? It's about eligibility. Might be considered part of Requirements? Could be included in About the role as note. But we need to preserve all substantive info. We'll embed that info in About the role or Requirements as a paragraph.
We must remove boilerplate: EEO, equal opportunity, drug test, clearance details? Clearance is substantive (required). Should keep. The note about citizenship restrictions is substantive. We'll keep that in Requirements or About the role.
We must not include application instructions like "Note to Applicants: With your application..." That's application instructions, should be removed. Also "Although the position will not ordinarily require extensive travel..." that's maybe not application instruction but could be considered job detail; it's about travel requirement. Might be kept as part of Responsibilities or About the role. It's not application instruction. We'll keep.
We must not include duplicated lines. We'll ensure no repeats.
Now craft HTML.
Structure:
About the role
... paragraphs summarizing role description, location, commitment, etc.
Responsibilities
- ... each bullet from "In this position, you will:" list.
Requirements
... combine minimum job requirements, desired qualifications, analysis, communication skills, clearance, citizenship restrictions, position commitment, etc.
Benefits
- ... each benefit from list.