Radar and Optics Applications Staff Assistant

We need to output HTML fragment with sections: 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. We need to preserve all substantive info, remove boilerplate like EEO, navigation, cookie, etc. Also remove application instructions (like file types, email, etc). Also remove duplicated lines. We need to parse the posting. Let's extract sections: Overview: description of ORNL, research areas, culture. Could be "About the role" maybe? Actually "Overview" could be about the role? The posting includes "Overview" describing ORNL and the role context. We could treat that as "About the role". Use

About the role

then

with that content. Major Duties/Responsibilities: list of duties. Use

Responsibilities

then

• items. Basic Qualifications: list. Could be under Requirements or Qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we need to map. We have Basic Qualifications and Preferred Qualifications. Could combine into Qualifications section (maybe separate Basic and Preferred?). But we need to avoid thin sections. Could have a single Qualifications section with both basic and preferred as lists. Also Special Requirements: Visa sponsorship not available, Q Clearance with SCI, WSAP testing, polygraph. That could be under Requirements or maybe a separate section like Requirements. Could include under Requirements. Skills: maybe list of skills from qualifications: experience with prototyping RF electronics, AI/ML, RF signature recognition, computational imaging, etc. Could be under Skills. Benefits: The posting lists many benefits under "ORNL offers competitive pay and benefits programs..." then list of benefits. So we can have Benefits section. Pay: Not specified explicitly; only says competitive pay but no numbers. According to rule: do NOT create Pay section unless posting actually states them. It says "competitive pay" but no specific. That's vague; maybe we should not include Pay because it's not specific. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "competitive pay" is vague but still a statement? It's not a specific number or range. Likely considered placeholder. Safer to omit Pay section. Schedule: Not mentioned. So omit. Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits. We need to ensure we preserve all substantive info. Let's extract each. About the role: The Overview paragraph(s). Let's combine: "The Oak Ridge National Laboratory (ORNL) conducts research, development, and deployment of radar and optics technologies to address national security and other worldwide challenges. Our research and development capabilities include radar and optics technologies, radio frequency (RF) communications, computational imaging, artificial intelligence / machine learning (AI/ML), neuromorphic sensing, video super-resolution, electromagnetics, real-time systems, data mining and analysis, high performance computing, cyber security protection for radar and related training systems, signal processing, and software development. In general, activities involve first-class interdisciplinary research with multiple research groups at ORNL, collaborations with private industry and academic partners across the nation, and mission-specific support for our national security research sponsors. ORNL thrives in a culture of respect, diversity, curiosity, and discovery." That's substantive. Responsibilities: The Major Duties/Responsibilities paragraph plus bullet list. We need to capture the prose before bullet list: "As a full-time Assistant Staff Member, you will support research staff on research projects and provide technical engineering support, technology assessments, engineering analysis, engineering studies, design reviews, and specifications development for upgrading existing radar and optical tracking systems and developing new radar and optical tracking systems for the Department of Energy (DoE) and other government agencies (OGAs). As part of your routine tasks, you may be required to:" Then bullet list items. We should include that prose as a

  then

  • for each bullet. Bullet items: - Assist in the development and prototyping of radar and optical tracking systems, neuromorphic sensor systems, radar transponders, and advanced sensor fusion technologies - Apply AI/ML to improve detection and identification of radar and optical tracking systems, or execute radar and optics systems performance tests and analyze the results to influence strategic national security decisions. - In short, you will help envision, design, develop, test, and deploy radar and optics technologies to support national security needs. - The position requires development of innovative solutions for general radar and optics challenges and collaboration with other team members for the development of technical demonstrations, proposals, oral presentations, and publications. - No less important, the interdisciplinary nature of projects demands strong interpersonal skills, evidence of working well in teams, and an expected desire to seek and develop healthy relationships. - Finally, the position requires a passion for mission-focused National Security challenges. - Deliver ORNL’s mission by aligning behaviors, priorities, and interactions with our core values of Impact, Integrity, Teamwork, Safety, and Service. - Promote equal opportunity by fostering a respectful workplace – in how we treat one another, work together, and measure success. We need to keep all. Qualifications: Combine Basic and Preferred. Basic Qualifications: - BS, MS or PhD degree with experience in Electrical and Computer Engineering, Computer Science, Mathematics, or a science related field. - Proven experience in radar and optics applications. - Excellent communication skills for conveying technical material to both scientists and non-scientists in both written and oral presentations. - Self-disciplined work ethic and eagerness to tackle challenging research problems. - Strong desire to work in a team environment. - Ability to obtain a security clearance. Preferred Qualifications: - Experience with prototyping RF electronics in a lab environment. - Experience with AI/ML. - Experience with RF signature recognition and classification algorithms. - Experience with Computational Imaging and Image Reconstruction techniques. We could separate Basic and Preferred as subheadings? But only allowed headings list; we could still include subheadings using

    ? Not specified; but we can keep as separate

    or

    with note. Probably better to have two lists: Basic Qualifications and Preferred Qualifications under Qualifications section, each with heading? But we shouldn't create extra headings not in list? The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use

    for section headings (list). It may be okay to use

    for subheadings, but safer to just include as

    with bold? But we cannot use markdown. We could just have two

    with preceding

    stating "Basic Qualifications:" and "Preferred Qualifications:" as plain text. We'll do:

    Qualifications

    Basic Qualifications:

    ...

    Preferred Qualifications:

    ...
    But using is okay; it's HTML. Skills: Could extract from qualifications: experience with prototyping RF electronics, AI/ML, RF signature recognition, computational imaging, etc. Also communication skills, teamwork, etc. But we already have those in qualifications. Might be redundant. Perhaps better to have Skills section separate listing technical skills: RF electronics prototyping, AI/ML, RF signature recognition, computational imaging, radar and optics applications, etc. But we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine qualifications and skills into one Qualifications section that includes both basic, preferred, and skills. But we already have qualifications. Could we drop Skills section? The instruction says we can include a section only when posting has real specific content for it. Skills are present (experience with prototyping RF electronics, AI/ML, etc). But we already covered them under Preferred Qualifications. Could still create Skills section listing those specific technical skills. However that would be thin? Might be okay. But we need to avoid duplication? Not explicitly forbidden, but we should preserve all substantive info; duplication is okay if we keep info. However better to avoid redundancy. Let's think: The posting includes Basic Qualifications (education, experience, communication, work ethic, teamwork, clearance). Preferred Qualifications (specific technical experiences). That's essentially skills. So we could have Qualifications section with two sublists: Basic and Preferred. That covers all. Then we don't need separate Skills section. Thus sections: About the role, Responsibilities, Qualifications, Benefits. Check Benefits: The posting lists many benefits after "ORNL offers competitive pay and benefits programs..." then list: Prescription Drug Plan, Dental Plan, Vision Plan, 401(k) Retirement Plan, Contributory Pension Plan, Life Insurance, Disability Benefits, Generous Vacation and Holidays, Parental Leave, Legal Insurance with Identity Theft Protection, Employee Assistance Plan, Flexible Spending Accounts, Health Savings Accounts, Wellness Programs, Educational Assistance, Relocation Assistance, and Employee Discounts. We should include that as
    • items. We must exclude boilerplate like "This position will remain open for a minimum of 5 days..." etc. Also remove application instructions (file types, email, etc). Also remove EEO statements, etc. Now construct HTML. We'll start with

      About the role

      then

      with the overview paragraph(s). Might need to split into two paragraphs? Could keep as one

      with line breaks? We'll keep as one

      . Then

      Responsibilities

      then

      with the introductory sentence(s) before bullet list. Then

      • for each bullet. Then

        Qualifications

        then

        Basic Qualifications:

        ...

        Preferred Qualifications:

        ...
        Then

        Benefits

        then
        • ...
        Make sure no extra whitespace? It's fine. Check that we didn't include Pay or Schedule. Now verify we preserved all substantive info: Overview, duties, responsibilities, basic qualifications, preferred qualifications, benefits. Did we miss any specifics like "Visa sponsorship is not available for this position." and "Q Clearance with SCI: This position requires the ability to obtain and maintain a Sensitive Compartmented Information (SCI) clearance from the Department of Energy. As such, this position is a Workplace Substance Abuse (WSAP) testing designated position. WSAP positions require passing a pre-placement drug test and participation in an ongoing random drug testing program. In addition, due the SCI, you may be also be subject to random polygraph testing." This is important; it's under Special Requirements. Should we include that? It's not covered in Basic Qualifications (ability to obtain a security clearance) but we need to include specifics about SCI clearance, WSAP, polygraph. That is substantive. We should include it somewhere, maybe under Qualifications as a separate list "Security Requirements" or under Responsibilities? Better to add a subsection under Qualifications: "Security Requirements". But we are limited to headings list; we could add a

        with that info under Qualifications after Preferred Qualifications. Thus we need to add that info. Let's extract that paragraph: "Special Requirements Visa sponsorship is not available for this position.Q Clearance with SCI: This position requires the ability to obtain and maintain a Sensitive Compartmented Information (SCI) clearance from the Department of Energy. As such, this position is a Workplace Substance Abuse (WSAP) testing designated position. WSAP positions require passing a pre-placement drug test and participation in an ongoing random drug testing