Postdoctoral Appointee - Fundamental Nanophotonics, Onsite
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc as headings; can fold minor metadata into short
or drop it. Remove boilerplate: EEO, legal, navigation, etc. Must preserve all substantive information. We need to parse the posting. Key sections: - Bidder Eligibility: details about temporary position up to one year, renewable up to five additional years, PhD conferred within five years prior to employment, internal bidding, etc. This is eligibility info. Could be under "About the role" or "Qualifications"? It's about eligibility for bidding. Might be considered "About the role" or "Qualifications". The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have "About Sandia" description: that's about the organization, could be "About the role"? Actually "About the role" is about the job. "About Sandia" is about the employer. Could be placed under "About the role"? Might be better as a separate section? Not in list. But we can include "About the role" heading and put description of the job there. The "About Sandia" could be part of "About the role" or maybe we can omit? The instruction: include a section ONLY when the posting has real, specific content for it. So we need to decide which headings have content. We have: - About Sandia: description of lab, benefits, flexible work arrangements, etc. This includes benefits info (flexible work arrangements, vacation, medical, 401k, learning opportunities, relocation assistance). Also mentions "These benefits vary by job classification." So we have some benefits info. - What Your Job Will Be Like: description of research scope, possible directions, etc. This is responsibilities/responsibilities. - Qualifications We Require: PhD, conferred within five years, in specific fields, strong background in photonics etc. - Qualifications We Desire: proven record of creative thinking, high-impact publications, strong communication skills. - About Our Team: description of group focus, collaborations, mentorship. - Posting Duration: open for minimum three days, may extend. - Security Clearance: details about clearance requirements, drug test, background review, etc. This is not benefits/pay/schedule but could be under "Requirements"? Might be considered "Requirements" (security clearance requirement). Could be placed under "Requirements" heading. - Also there is "Bidder Eligibility" which is about eligibility for bidding internal positions; not directly about the job but maybe part of "Requirements"? Could be considered "Requirements" as eligibility criteria. We need to avoid boilerplate: EEO, NNSA Requirements for MedPEDs, etc. Also remove duplicated lines, application instructions. Also remove "Job ID: 699062" etc. We must preserve all substantive information. So we need to include content from Bidder Eligibility, About Sandia, What Your Job Will Be Like, Qualifications We Require, Qualifications We Desire, About Our Team, Posting Duration, Security Clearance (maybe as Requirements). Also maybe include "Benefits" from About Sandia (flexible work arrangements, vacation, medical, 401k, learning opportunities, relocation assistance). Also note "These benefits vary by job classification." That's substantive. We must not create Pay or Schedule sections unless posting actually states them. There's no explicit pay or schedule info. So we should not include Pay or Schedule headings. We must not create Benefits section unless posting actually states them. The posting does state benefits: flexible work arrangements, generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance. So we can include Benefits section. We must not create a section with filler like "commensurate with experience". Not present. Thus we can have sections: - About the role (maybe combine About Sandia and What Your Job Will Be Like? Actually About the role could be description of job responsibilities. Could put "What Your Job Will Be Like" under About the role. Or we could have separate sections: About the role (description of job) and Responsibilities (list of duties). But we have limited headings; we can choose to use About the role for job description, Responsibilities for list of duties (maybe bullet list). However the posting does not have a explicit list of duties; it's prose describing research directions. Could treat that as Responsibilities. - Requirements: could include Bidder Eligibility, Security Clearance, maybe also qualifications? But Qualifications We Require and Qualifications We Desire are separate. Could put those under Qualifications heading. Requirements could be eligibility and clearance. - Qualifications: include both required and desired. - Skills: maybe not explicitly listed; we have strong background in photonics etc. That's more qualifications. Could skip Skills. - Benefits: include flexible work arrangements, vacation, medical, 401k, learning, relocation. - About Our Team: could be under About the role or separate? Could be a section "About the team". Not in list but we could maybe put under About the role? But we have limited headings; maybe we can include "About the team" as a subsection under About the role? But instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those headings.
Thus we need to fit all content into those headings.
Let's decide:
- About the role: include description of the job (What Your Job Will Be Like) and maybe About Sandia? Actually About Sandia is about employer, not role. Could be part of About the role? Might be okay to include a brief description of Sandia as context. But we could also put About Sandia under About the role as "About Sandia". Might be okay.
- Responsibilities: maybe we can list specific duties: pursuing fundamental scientific questions, exploring new physical phenomena, developing theoretical frameworks, connecting with experiments, possible research directions, etc. Could be bullet list.
- Requirements: include Bidder Eligibility (temporary position up to one year, renewable, PhD within five years, internal bidding rules, employee one-year rule, manager approval, collective bargaining, etc.) and Security Clearance details (no DOE clearance required, drug test, background review, USAF base access, restrictions on certain nationalities, UPIV process, etc.). Also maybe include "Due to the nature of the work, the selected candidate must be able to work onsite." That's a requirement.
- Qualifications: include Qualifications We Require (PhD within five years, fields, strong background in photonics etc.) and Qualifications We Desire (creative thinking, publications, communication skills).
- Skills: maybe not needed; we could omit if no specific skill list.
- Benefits: include flexible work arrangements (9/80, 4/10, part-time, telecommuting), generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance, amenities for work/life balance. Also note "These benefits vary by job classification."
- Pay: not present, omit.
- Schedule: not present, omit.
We must not include filler like "commensurate with experience". Not present.
We must not include boilerplate: EEO, NNSA Requirements for MedPEDs, etc. Also remove duplicated lines.
We need to output only HTML fragment, no markdown fences.
Let's craft.
Structure:
About the role
... (About Sandia + job description)
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...