Senior Radar Systems Test Engineer

We need to output HTML fragment with sections: About the role? The posting includes Position Summary, Responsibilities, Qualifications, Additional Information (Location, Travel), Company Overview. We need to use

for section headings. Do not repeat job title as heading. No Job ID. No boilerplate. We must preserve all substantive information. Remove cookie/navigation/legal/EEO etc. There's no explicit EEO but there is a note about compensation etc. That's substantive? It's about compensation determination; we could include maybe in a "Compensation" section? But rule: only include Pay/Schedule/Benefits sections if posting actually states them. The posting says: "Please note: Final compensation for this position will be determined by various factors such as the Federal Government contract labor categories and contract wage rates, relevant work experience, specific skills and competencies, geographic location, education, and certifications." That's about compensation but not a specific pay range. It's not a specific pay figure; it's a statement that compensation will be determined by factors. According to 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. This is somewhat vague but it's not a specific pay; it's a statement that compensation will be determined by factors. That could be considered filler? It's not a specific number but it's substantive info about how compensation determined. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about compensation determination, but not a specific pay. I'd lean to not include a Pay section because it's not a concrete figure. However we could include a short paragraph under Additional Information maybe. The rule says "Prefer a few substantive sections over many thin ones." So we could combine Location, Travel, and compensation note into an "Additional Information" section. We need sections: About the role (Position Summary), Responsibilities, Qualifications, Additional Information (Location, Travel, Compensation note), Company Overview. We must use

for each section heading. Use

• for any list of duties/requirements/benefits. For responsibilities we have a list of duties; we can turn each bullet into
• . For qualifications we have Minimum Required Qualifications (with multiple subpoints) and Preferred Qualifications, Technical Skills, Interpersonal Skills. Could be many sub-sections; but we could keep Qualifications as a section with nested lists? The instruction: Use
  • for any list of duties/requirements/benefits. So we can have multiple lists inside the Qualifications section. We must not repeat the job title as heading. The job title is Senior Radar Systems Test Engineer. We'll not use that. We must not put Job ID/requisition numbers as headings; none present. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting. Let's extract content. Position Summary paragraph: "Odyssey has an exciting opportunity for an Senior Radar Systems Test Engineer supporting the 46 Test Squadron’s Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance (C5ISR) Agile Test Flight at Eglin AFB, FL. The Radar Systems Test Engineer will support developmental and operational testing of fixed and tactical radar systems, providing subject‑matter expertise across radar operations, ground and flight testing, data analysis, and C2 system integration. This is a full‑time position located at Eglin AFB, FL, with approximately 25% CONUS/OCONUS travel." We'll put that in a

    under About the role. Responsibilities: The section "Responsibilities" includes subheadings: Radar Test Planning & Execution, Technical Support & Analysis, Program & Stakeholder Coordination, Documentation & Reporting, Team Leadership & Operational Readiness. Each has bullet points (some paragraphs). We'll need to convert each bullet into

  • . The text includes sentences; we can keep them as list items. We must preserve all substantive information; we should not lose any details. Let's list each bullet: Under Radar Test Planning & Execution: - Plan, execute, and report on developmental test and evaluation of tactical and fixed radar systems supporting command and control operations. - Develop and conduct ground and flight tests to verify radar system performance and requirements. - Perform Verification & Validation (V&V) of radar system requirements. - Lead or participate in formal and informal radar test activities, including monitoring test results, data collection/reduction, analysis, and mission‑effectiveness assessments. Technical Support & Analysis: - Provide radar systems technical expertise during test planning, procedure development, data collection, analysis, and reporting. - Review system requirements and support creation of program‑specific ground and flight test documents (e.g., test procedures, charters, methods of test, test reports). - Interpret test directives, guides, and manuals (DODI 5000 series, AFI 99‑103, TO 00‑35D‑54) to derive test tasks and requirements. - Support contractor test events, DT&E, OT&E, Force Development Evaluations (FDE), and system certification for test readiness. Program & Stakeholder Coordination: - Participate in working groups and test team planning meetings to determine testable requirements, required resources, and appropriate methods. - Attend program meetings to provide technical information and updates on developmental and qualification test activities. - Document deficiencies, anomalies, and participate in deficiency review boards (DRBs). - Support long‑range and quick‑reaction test planning and contribute to cost and resource estimating. Documentation & Reporting: - Support development of strategic test documentation such as test strategies, scenario plans, and modeling/simulation plans. - Produce technical briefings, written reports, and formal presentations. - Communicate clearly and effectively to both technical and non‑technical stakeholders. Team Leadership & Operational Readiness: - Provide expert radar system knowledge and mentorship within team environments. - Lead and direct the work of others, as required. - Maintain up‑to‑date knowledge of deployable and fixed C2 systems. - Willingness to work extended hours, weekends, or holidays as required to meet mission needs. - Ability to travel worldwide to support test events. Qualifications: There's a "Qualifications" heading with subparts: Citizenship, Minimum Required Qualifications (with several bullet-like statements), Demonstrated experience..., Understanding..., Working knowledge..., Experience..., Ability..., Ability..., Ability..., Strong..., Ability... Then "Preferred Qualifications" with Education..., Experience..., etc. Then "Technical Skills" bullet list, then "Interpersonal Skills" bullet list. We need to preserve all. We'll structure as:

    Qualifications

    • Citizenship: Must be a US citizen
    • Minimum Required Qualifications:
      • Clearance: Active Secret clearance required
      • Education: Bachelor of Science degree and 18 years of relevant experience, OR PhD and 8 years of relevant experience
      • 12 years of applicable experience + Master’s equivalency (22 total)
      • 8 years of technical experience + Bachelor’s equivalency (18 total)
      • Demonstrated experience in the maintenance and operation of fixed and tactical radar systems supporting ATC and C2 operations.
      • Understanding of RF theory as applied to radar.
      • Working knowledge of ASTERIX protocol (categories and message formatting).
      • Experience in ground and flight radar testing, including proper radio phraseology for aircraft communication.
      • Ability to interpret DoD, USAF, and technical directives to derive test tasks.
      • Ability to develop test plans, charters, procedures, methods of test, and reports.
      • Strong written and verbal communication skills, including technical writing and briefings.
      • Ability to work effectively on teams and provide radar system expertise.
    • Preferred Qualifications:
      • Education: Master of Science degree and over 10 years of experience in C4ISR systems, including digital data maintenance, communications systems, or software development/testing
      • Experience with both mobile and fixed tactical radar systems.
      • Familiarity with tactical communications systems (radios, phones, intercoms, switches) and deployed communications laydown.
      • Experience with tactical sensors, fixed communications systems, or computer‑based systems.
      • Experience with ATCRBS IFF Mark XII Systems (AIMS) certification testing, including Mode 4, Mode 5, and Mode S.
      • Experience with RADES RS4 Radar Environment Simulator (RES) and Radar Analysis Support System (RASS) tools.
      • Experience with USAF Technical Order (TO) processes (creation, V&V, and management).
      • Proficiency in Microsoft Office Suite (Word, Excel, PowerPoint, Outlook, Access).
      • Developmental/Operational test experience.
    • Technical Skills:
      • Expertise in radar system operations, maintenance, and testing.
      • Knowledge of C4ISR system integration and radar‑to‑C2 interactions.
      • Understanding of RF theory and radar signal behaviors.
      • Proficiency in ASTERIX protocol message formats.
      • Ability to develop test plans, scenarios, procedures, and technical documentation.
      • Experience collecting, reducing, analyzing, and reporting radar test data.
    • Interpersonal Skills:
      • Ability to communicate clearly in technical writing, briefings, and presentations.
      • Demonstrated teamwork and ability to lead small or large groups.
      • Ability to coordinate with government, contractor, and test team stakeholders.
      • Strong organization and decision‑making skills.
      • Ability to work extended hours for mission‑support demands.
    But note: The instruction says use
    • for any list of duties/requirements/benefits. It didn't forbid nested lists, but we must ensure we use
      • for lists. Nested
        inside
        • is okay. Additional Information: Location: Eglin AFB, FL Travel: 25% Onsite #TMAS3 #CTG (maybe those are tags). Also compensation note. We'll include location, travel, and compensation note as

          maybe. Company Overview: paragraph about Odyssey. We must not include boilerplate like "Please note: Final compensation..." maybe we keep it as part of Additional Information. We must not include any markdown fences. Let's craft final HTML. We'll start with

          About the role

          then

          ...

          Then

          Responsibilities

          then
          with each bullet as
          • . We'll need to break down each bullet as per above. Then

            Qualifications

            then nested lists as above. Then

            Additional Information

            then

            Location: Eglin AFB, FL. Travel: Approximately 25% CONUS/OCONUS (onsite). Final compensation will be determined by various factors such as the Federal Government contract labor categories and contract wage rates, relevant work experience, specific skills and competencies, geographic location, education, and certifications.

            Also maybe include the tags #TMAS3 #CTG? They are likely internal tags; we could include them as part of the paragraph. Then

            Company Overview

            then

            ...

            Check that we didn't miss any substantive info: The Position Summary also mentions "full‑time position located at Eglin AFB, FL, with approximately 25% CONUS/OCONUS travel." We included that in Additional Information; but we also had it in Position Summary. To avoid duplication, we could