Senior Datalinks Engineer

We need to output HTML fragment with sections: About the role? The posting includes "Position Overview", "Primary Role", "Expected Areas of Emphasis", "Responsibilities", "Required Qualifications", "Highly Desired Qualifications", "Desired Professional Attributes", "Why join Thompson Gray?" plus benefits etc. We must use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to these headings appropriately. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings if content matches. We need to include a section only when posting has real, specific content for it. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to decide which sections to include: About the role (maybe from Position Overview and Primary Role). Responsibilities (list). Requirements (maybe Required Qualifications). Qualifications (maybe Highly Desired Qualifications). Skills (maybe Desired Professional Attributes). Benefits (from Why join Thompson Gray? includes benefits). Pay (not mentioned explicitly; they say "Competitive pay based on your qualifications" but that's vague; we should not create Pay section unless posting actually states them. It says "Competitive pay based on your qualifications" - that is somewhat generic but still mentions pay. However instruction: 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 based on your qualifications" is somewhat vague but still states pay exists. Might be acceptable? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Competitive pay based on your qualifications". That is a statement about pay, albeit not specific numbers. I'd say we can include Pay section with that sentence. Schedule: they mention "Full Time onsite Position" and "Ability to work primarily on-site with limited telework eligibility." That's schedule info. So we can include Schedule section. Benefits: they list many benefits. So include Benefits. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement; we should drop that. We need to output only HTML fragment. Let's structure:

  About the role

  Full Time onsite Position Overview ...

  maybe combine Position Overview and Primary Role. But we need to avoid duplication. Let's read the posting text: "Full Time onsite Position Overview We are seeking a highly capable Senior Datalinks Engineer to support the PM UAS Technical Management Division (TMD) and serve as the primary Division-level technical expert for UAS datalinks. This individual will work in direct support of the Chief Engineer, the PM UAS Product Offices, the Component Technology Branch, and special projects aligned with the PM UAS mission. The position is full-time and primarily on-site, with limited telework eligibility. Primary Role The Senior Datalinks Engineer will serve as the primary datalinks subject matter expert for PM UAS at the Division level, supporting the Chief Engineer and providing technical leadership across the PM UAS enterprise. The individual will provide technical oversight and subject matter expertise for UAS datalink system development, integration, qualification, fielding, sustainment, modernization, and issue resolution. Relevant Technologies Include Modems and radio frequency (RF) equipmentAntennas and radomesRF interfaces and architecturesCommunication protocolsDatalink standardsSoftware and firmwareWaveformsFrequency managementEMI/EMV design and qualificationElectronic warfare (EW) hardening and resiliencyRF modeling and analysisEncryption, including AES-256 and Type 1 encryption conceptsCommunications Security (COMSEC)Transmission Security (TRANSEC) The ideal candidate will combine significant RF/datalink technical expertise with strong systems engineering judgment, strategic thinking, acquisition awareness, communication skills, and the ability to lead through complex technical and organizational challenges." We can put that in About the role. Then Expected Areas of Emphasis (40% etc). That could be part of Responsibilities? But we have a separate Responsibilities section later. Might be better to treat Expected Areas of Emphasis as part of Responsibilities (since it's about emphasis). However we have a Responsibilities section later with bullet list. We could merge them. But instruction: Use
  • for any list of duties/requirements/benefits. The Expected Areas of Emphasis includes percentages and bullet-like items. Could be a list. We could create a section "Responsibilities" that includes both the Expected Areas of Emphasis and the Responsibilities list. But we need to avoid duplication. Let's see the Responsibilities section later: It starts with "Responsibilities Develop and coordinate a comprehensive UAS datalink strategy ..." That's a long list. Thus we could have:

    About the role

    ... (Position Overview + Primary Role + Relevant Technologies + Ideal candidate description)

    Responsibilities

    • ... items from Expected Areas of Emphasis (maybe each bullet)
    • ... items from Responsibilities list
    But we need to preserve all info; we can combine. Then

    Requirements

    for Required Qualifications.

    Qualifications

    for Highly Desired Qualifications.

    Skills

    for Desired Professional Attributes.

    Benefits

    for Why join Thompson Gray? (benefits list).

    Pay

    for "Competitive pay based on your qualifications".

    Schedule

    for "Full-time and primarily on-site, with limited telework eligibility." plus maybe travel up to 25%? Travel could be part of schedule? Might be separate but we can include in Schedule. We must not create sections with filler. All have content. Now we need to ensure we don't repeat job title. Not using. Now we need to extract details precisely. Let's parse the posting. **Position Overview** (first paragraph): "We are seeking a highly capable Senior Datalinks Engineer to support the PM UAS Technical Management Division (TMD) and serve as the primary Division-level technical expert for UAS datalinks. This individual will work in direct support of the Chief Engineer, the PM UAS Product Offices, the Component Technology Branch, and special projects aligned with the PM UAS mission. The position is full-time and primarily on-site, with limited telework eligibility." **Primary Role**: "The Senior Datalinks Engineer will serve as the primary datalinks subject matter expert for PM UAS at the Division level, supporting the Chief Engineer and providing technical leadership across the PM UAS enterprise. The individual will provide technical oversight and subject matter expertise for UAS datalink system development, integration, qualification, fielding, sustainment, modernization, and issue resolution." **Relevant Technologies Include** (list): "Modems and radio frequency (RF) equipment Antennas and radomes RF interfaces and architectures Communication protocols Datalink standards Software and firmware Waveforms Frequency management EMI/EMV design and qualification Electronic warfare (EW) hardening and resiliency RF modeling and analysis Encryption, including AES-256 and Type 1 encryption concepts Communications Security (COMSEC) Transmission Security (TRANSEC)" **Ideal candidate description**: "The ideal candidate will combine significant RF/datalink technical expertise with strong systems engineering judgment, strategic thinking, acquisition awareness, communication skills, and the ability to lead through complex technical and organizational challenges." Now Expected Areas of Emphasis: "Approximately 40% – Enterprise Datalink Strategy, Frequency Management, and External Coordination Support frequency management activities across the PM UAS enterprise. Lead or support the JSIL Interface Control Working Group (ICWG) for datalinks. Develop, maintain, and communicate an overarching PM UAS datalink strategy and technical roadmap. Coordinate with government laboratories, other government agencies, military organizations, development organizations, and other stakeholders. Coordinate, as applicable, with organizations such as AvMC, C5ISR, NSA, NATO, OSW, C2N, and other relevant technical organizations. Maintain awareness of Army, Joint, partner-service, coalition, and government investments and activities that may affect UAS datalink capabilities. Represent PM UAS/TMD datalink strategy in internal and external technical and programmatic forums." "Approximately 50% – Product Office Technical Support Provide datalink engineering expertise and direct support across the PM UAS Product Offices, including: Small UAS (SUAS) Tactical UAS (TUAS) UAS Launched Effects / related product portfolios Long Endurance / applicable UAS portfolios Emerging UAS / applicable future product portfolios Activities May Include System architecture and design reviews Requirements development and assessment RF and communications engineering Integration and qualification System upgrades and modernization Field issue investigation and resolution Engineering trade studies Technical risk assessments Acquisition planning Government-furnished equipment and information coordination Contractor technical oversight Sustainment engineering Datalink interoperability" "Approximately 10% – Chief Engineer and Special Project Support Support technical issues and special projects assigned by the Chief Engineer, Division leadership, or Branch leadership. Rapidly investigate emerging technical issues and provide technically defensible recommendations. Support cross-functional engineering and acquisition activities outside the traditional datalinks portfolio when needed. Apply broad systems engineering judgment to new or evolving PM UAS challenges." Now Responsibilities list (starting after Expected Areas? Actually after Expected Areas they have "Responsibilities" heading then a long paragraph with many items separated by periods. Let's extract each as bullet. Responsibilities text: "Develop and coordinate a comprehensive UAS datalink strategy consistent with PM UAS objectives, missions, architectures, and future capabilities. Serve as the principal datalink technical advisor to the Chief Engineer, TMD leadership, Product Offices, and other PM UAS stakeholders. Provide technical oversight for datalink system development, integration, qualification, production, fielding, modernization, and sustainment. Evaluate systems, subsystems, and components involving RF equipment, antennas, modems, radomes, communications protocols, interfaces, software, waveforms, and associated technologies. Assess relevant threat environments and evaluate potential impacts to UAS RF and communications systems. Evaluate datalink resiliency, interoperability, spectrum, encryption, COMSEC, TRANSEC, EMI/EMV, and EW considerations. Support technical assessments of current and emerging datalink capabilities, technologies, standards, and architectures. Maintain awareness of relevant government, military service, laboratory, industry, and coalition datalink initiatives. Lead and participate in technical working groups, interface control working groups, engineering reviews, and acquisition forums. Coordinate with government laboratories, development organizations, contractors, other Product Offices, and external stakeholders. Make recommendations concerning technical direction, architectures, standards, policies, and investments to improve UAS mission effectiveness and survivability. Represent PM UAS in external forums and effectively communicate both technical and programmatic considerations. Coordinate with peer organizations for government-furnished equipment, government-furnished information, development, production, integration, and sustainment activities. Plan, coordinate, and execute changes required to address critical system upgrades, modernization efforts, obsolescence issues, and field problems. Develop, author, and review Performance Work Statements, Statements of Work, technical requirements, evaluation criteria,