Tactical Communications and Field Systems Engineer
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading (the page already shows it)
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless the posting actually states them
9. Prefer a few substantive sections over many thin ones
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
- Location, Travel, Clearance, Reports to: metadata
- About NODA AI: company description
- Position Summary: role overview
- Key Responsibilities: list of duties
- Required Qualifications: list of requirements
- Preferred Qualifications: list of preferred qualifications
- Field Operations Expectations: expectations
- Benefits & Perks: detailed benefits list
- Professional Development: career growth info
- Export Control: legal requirement
- Equal Employment Opportunity: boilerplate
- Need an accommodation: contact info
I need to structure this into appropriate sections. The rules say to use
for section headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But I should only include sections that have real content.
Let me map:
- "About the role" could cover Position Summary and maybe company description
- "Responsibilities" for Key Responsibilities
- "Requirements" for Required Qualifications
- "Qualifications" could be for Preferred Qualifications (but maybe combine with Requirements? The rules list both "Requirements" and "Qualifications" as possible headings)
- "Benefits" for Benefits & Perks
- "Professional Development" could be a section or part of Benefits
- Field Operations Expectations could be its own section or part of Responsibilities
The rules say: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can use these headings.
I should not include Pay or Schedule sections unless the posting states them. The posting mentions travel up to 50%, work nights and weekends, but not a specific schedule or pay. So no Pay or Schedule sections.
I need to fold minor metadata (Location, Travel, Clearance, Reports to) into a short
or drop it. I'll include them in a brief paragraph at the top, maybe under "About the role" or a separate "Role details" but the rules don't list that as a heading. I could put them in a
before the first heading, but the output should be HTML fragment with sections. Perhaps include them in the "About the role" section as a paragraph.
The rules: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it."
So I'll create a short paragraph with location, travel, clearance, reports to.
Now, I need to remove boilerplate: Export Control, Equal Employment Opportunity, Need an accommodation. Those are legal/EEO boilerplate, so remove.
Also remove duplicated lines and application instructions (none here).
Now, structure:
1. About the role: includes company description, position summary, and metadata paragraph.
2. Responsibilities: Key Responsibilities as a list.
3. Requirements: Required Qualifications as a list.
4. Qualifications: Preferred Qualifications as a list (maybe heading "Preferred Qualifications" but the rules say "Qualifications" as example heading. I'll use "Preferred Qualifications" as a subheading? But the rules say use
for section headings like "Qualifications". I could have two sections: "Requirements" and "Preferred Qualifications". But the example includes both "Requirements" and "Qualifications". I'll use "Requirements" for required, and "Preferred Qualifications" for preferred. However, the rules say "Qualifications" as a heading example. I'll use "Preferred Qualifications" as an maybe. But to follow the example, I could use "Qualifications" for preferred. But the posting has "Required Qualifications" and "Preferred Qualifications". I'll make two sections: "Requirements" and "Preferred Qualifications". That seems clear.
5. Field Operations Expectations: could be a section "Expectations" or "Field Operations Expectations". The rules don't list that, but I can create a heading if there's real content. I'll include it as a section.
6. Benefits: Benefits & Perks as a list.
7. Professional Development: could be part of Benefits or separate. I'll include as a separate section "Professional Development".
Now, I need to ensure each section has substantive content. All do.
Now, write HTML.
I'll start with a paragraph for metadata.
Then sections with and - for lists,
for prose.
Let's craft.
Note: The rules say "Output ONLY the HTML fragment — no /, no markdown code fences." So just the HTML tags.
I'll write:
Location: Austin, Texas; on-site when not deployed. Travel: Up to 50%, including international travel and deployments to combat zones. Clearance: U.S. citizen with an active DoD Secret clearance or eligibility for reinstatement. Reports to: Field Operations Lead.
About the role
NODA is a Veteran-owned, venture-backed technology company that is transforming how unmanned systems collaborate in complex, mission-critical environments. We are developing next-generation solutions that enable the autonomous orchestration of heterogeneous unmanned systems across air, sea, land, and space with vital applications in the defense, intelligence, and commercial sectors. Joining NODA means working on meaningful technology that pushes the boundaries of autonomy alongside a team that thrives on innovation, rapid iteration, and collaboration.
The Tactical Communications and Field Systems Engineer designs, integrates, and maintains the networks that connect NODA’s unmanned platforms, ground control stations, and customer systems. The role supports field testing, demonstrations, exercises, and operational deployments, with responsibility for communications readiness, troubleshooting, and technical documentation.
Responsibilities
- Develop mission communications plans covering radio and satellite links, mesh networks, IP addressing, encryption, antenna placement and separation, and backhaul.
- Establish primary, alternate, contingency, and emergency (PACE) options for critical links.
- Configure, test, and maintain communications between unmanned air, ground, surface, and underwater platforms and their ground control stations, including relay and retransmission sites for beyond-line-of-sight connectivity.
- Diagnose faults in radios, antennas, cabling, power systems, and IP networks, both on-site and remotely.
- Identify and mitigate external and self-generated interference, including jamming.
- Coordinate frequency and satellite access requests with range, military, and host-nation authorities.
- Manage communications security (COMSEC) key loading and accountability, and apply transmission security (TRANSEC) procedures.
- Fabricate and repair cables, harnesses, and connectors.
- Maintain equipment inventories, configuration records, spares, antennas, and field power systems.
- Survey and establish field sites, verify communications before deployment, and integrate command and control, telemetry, video, and link-health data into customer systems.
- Evaluate radios, waveforms, and antennas.
- Maintain network diagrams, configuration files, frequency records, communications plans, and after-action reports.
- Train and qualify teammates and customers on communications equipment and procedures.
- Work with Engineering, Product, and customer teams, and support site setup, teardown, and other field activities.
Requirements
- At least five years of experience planning, installing, operating, and maintaining tactical communications as a military communicator or field service representative, including deployments with combat or combat support units.
- Hands-on experience with HF, VHF, UHF, SATCOM, and mobile ad hoc or mesh networks, including configuration, encryption, link testing, and retransmission.
- Relevant systems include L3Harris AN/PRC-117G, AN/PRC-152, and AN/PRC-163; Motorola; TACSAT/MUOS; MPU5; Silvus; Doodle Labs; and Microhard.
- Working knowledge of RF propagation, antenna theory, and electromagnetic interference.
- Practical skills in RF cabling, connectors, grounding, field power, and soldering, with experience using spectrum analyzers, power and standing wave ratio meters, and multimeters.
- Proficiency in IP networking, including subnetting, DHCP, VLANs, routing, firewalls, VPNs, and Ethernet connections between radios, ground control stations, and payloads.
- Experience with COMSEC key handling and accountability, TRANSEC, emission control, spectrum coordination, and PACE planning in environments affected by electronic warfare or jamming.
- U.S. citizen with an active DoD Secret clearance or eligibility for reinstatement.
- A valid U.S. passport, or the ability to obtain one, and the ability to meet deployment medical and processing requirements.
- Ability to travel up to 50%, including internationally and to combat zones; work nights and weekends as required; and lift up to 60 pounds in demanding field conditions.
Preferred Qualifications
- CompTIA Security+, Network+, Linux+, Cisco CCNA, or a certification applicable to DoD 8140 workforce requirements.
- Military tactical communications experience, such as Army 18E/25C/25S/25U, Marine Corps 0621/0629, Air Force combat communications or TACP, Navy IT/ET, or Coast Guard IT, or equivalent contractor experience.
- Integration or testing of unmanned aircraft and ground, surface, or underwater vehicles, including ground control station datalinks and counter-UAS systems.
- RF spectrum monitoring and signals analysis, with experience in 4G/LTE or satellite backhaul systems such as Starlink, Iridium, or VSAT.
- Experience using Python for automation, equipment configuration, or log and telemetry analysis.
- Experience with Linux command-line tools, single-board computers such as Raspberry Pi, and network diagnostics using Wireshark.
- Experience with Jira and Confluence.
Field Operations Expectations
The engineer is expected to identify communications risks before events, troubleshoot methodically under time pressure, and maintain accurate readiness and configuration records. The role requires sound judgment in austere conditions, collaboration across teams, and willingness to cross-train in piloting, hardware integration, and demonstration support.
Benefits
- Premium medical, dental, and vision coverage with zero
for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: - Location, Travel, Clearance, Reports to: metadata - About NODA AI: company description - Position Summary: role overview - Key Responsibilities: list of duties - Required Qualifications: list of requirements - Preferred Qualifications: list of preferred qualifications - Field Operations Expectations: expectations - Benefits & Perks: detailed benefits list - Professional Development: career growth info - Export Control: legal requirement - Equal Employment Opportunity: boilerplate - Need an accommodation: contact info I need to structure this into appropriate sections. The rules say to use
for section headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But I should only include sections that have real content.
Let me map:
- "About the role" could cover Position Summary and maybe company description
- "Responsibilities" for Key Responsibilities
- "Requirements" for Required Qualifications
- "Qualifications" could be for Preferred Qualifications (but maybe combine with Requirements? The rules list both "Requirements" and "Qualifications" as possible headings)
- "Benefits" for Benefits & Perks
- "Professional Development" could be a section or part of Benefits
- Field Operations Expectations could be its own section or part of Responsibilities
The rules say: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can use these headings.
I should not include Pay or Schedule sections unless the posting states them. The posting mentions travel up to 50%, work nights and weekends, but not a specific schedule or pay. So no Pay or Schedule sections.
I need to fold minor metadata (Location, Travel, Clearance, Reports to) into a short
or drop it. I'll include them in a brief paragraph at the top, maybe under "About the role" or a separate "Role details" but the rules don't list that as a heading. I could put them in a
before the first heading, but the output should be HTML fragment with sections. Perhaps include them in the "About the role" section as a paragraph. The rules: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I'll create a short paragraph with location, travel, clearance, reports to. Now, I need to remove boilerplate: Export Control, Equal Employment Opportunity, Need an accommodation. Those are legal/EEO boilerplate, so remove. Also remove duplicated lines and application instructions (none here). Now, structure: 1. About the role: includes company description, position summary, and metadata paragraph. 2. Responsibilities: Key Responsibilities as a list. 3. Requirements: Required Qualifications as a list. 4. Qualifications: Preferred Qualifications as a list (maybe heading "Preferred Qualifications" but the rules say "Qualifications" as example heading. I'll use "Preferred Qualifications" as a subheading? But the rules say use
for section headings like "Qualifications". I could have two sections: "Requirements" and "Preferred Qualifications". But the example includes both "Requirements" and "Qualifications". I'll use "Requirements" for required, and "Preferred Qualifications" for preferred. However, the rules say "Qualifications" as a heading example. I'll use "Preferred Qualifications" as an maybe. But to follow the example, I could use "Qualifications" for preferred. But the posting has "Required Qualifications" and "Preferred Qualifications". I'll make two sections: "Requirements" and "Preferred Qualifications". That seems clear.
5. Field Operations Expectations: could be a section "Expectations" or "Field Operations Expectations". The rules don't list that, but I can create a heading if there's real content. I'll include it as a section.
6. Benefits: Benefits & Perks as a list.
7. Professional Development: could be part of Benefits or separate. I'll include as a separate section "Professional Development".
Now, I need to ensure each section has substantive content. All do.
Now, write HTML.
I'll start with a paragraph for metadata.
Then sections with and - for lists,
for prose.
Let's craft.
Note: The rules say "Output ONLY the HTML fragment — no /, no markdown code fences." So just the HTML tags.
I'll write:
Location: Austin, Texas; on-site when not deployed. Travel: Up to 50%, including international travel and deployments to combat zones. Clearance: U.S. citizen with an active DoD Secret clearance or eligibility for reinstatement. Reports to: Field Operations Lead.
About the role
NODA is a Veteran-owned, venture-backed technology company that is transforming how unmanned systems collaborate in complex, mission-critical environments. We are developing next-generation solutions that enable the autonomous orchestration of heterogeneous unmanned systems across air, sea, land, and space with vital applications in the defense, intelligence, and commercial sectors. Joining NODA means working on meaningful technology that pushes the boundaries of autonomy alongside a team that thrives on innovation, rapid iteration, and collaboration.
The Tactical Communications and Field Systems Engineer designs, integrates, and maintains the networks that connect NODA’s unmanned platforms, ground control stations, and customer systems. The role supports field testing, demonstrations, exercises, and operational deployments, with responsibility for communications readiness, troubleshooting, and technical documentation.
Responsibilities
- Develop mission communications plans covering radio and satellite links, mesh networks, IP addressing, encryption, antenna placement and separation, and backhaul.
- Establish primary, alternate, contingency, and emergency (PACE) options for critical links.
- Configure, test, and maintain communications between unmanned air, ground, surface, and underwater platforms and their ground control stations, including relay and retransmission sites for beyond-line-of-sight connectivity.
- Diagnose faults in radios, antennas, cabling, power systems, and IP networks, both on-site and remotely.
- Identify and mitigate external and self-generated interference, including jamming.
- Coordinate frequency and satellite access requests with range, military, and host-nation authorities.
- Manage communications security (COMSEC) key loading and accountability, and apply transmission security (TRANSEC) procedures.
- Fabricate and repair cables, harnesses, and connectors.
- Maintain equipment inventories, configuration records, spares, antennas, and field power systems.
- Survey and establish field sites, verify communications before deployment, and integrate command and control, telemetry, video, and link-health data into customer systems.
- Evaluate radios, waveforms, and antennas.
- Maintain network diagrams, configuration files, frequency records, communications plans, and after-action reports.
- Train and qualify teammates and customers on communications equipment and procedures.
- Work with Engineering, Product, and customer teams, and support site setup, teardown, and other field activities.
Requirements
- At least five years of experience planning, installing, operating, and maintaining tactical communications as a military communicator or field service representative, including deployments with combat or combat support units.
- Hands-on experience with HF, VHF, UHF, SATCOM, and mobile ad hoc or mesh networks, including configuration, encryption, link testing, and retransmission.
- Relevant systems include L3Harris AN/PRC-117G, AN/PRC-152, and AN/PRC-163; Motorola; TACSAT/MUOS; MPU5; Silvus; Doodle Labs; and Microhard.
- Working knowledge of RF propagation, antenna theory, and electromagnetic interference.
- Practical skills in RF cabling, connectors, grounding, field power, and soldering, with experience using spectrum analyzers, power and standing wave ratio meters, and multimeters.
- Proficiency in IP networking, including subnetting, DHCP, VLANs, routing, firewalls, VPNs, and Ethernet connections between radios, ground control stations, and payloads.
- Experience with COMSEC key handling and accountability, TRANSEC, emission control, spectrum coordination, and PACE planning in environments affected by electronic warfare or jamming.
- U.S. citizen with an active DoD Secret clearance or eligibility for reinstatement.
- A valid U.S. passport, or the ability to obtain one, and the ability to meet deployment medical and processing requirements.
- Ability to travel up to 50%, including internationally and to combat zones; work nights and weekends as required; and lift up to 60 pounds in demanding field conditions.
Preferred Qualifications
- CompTIA Security+, Network+, Linux+, Cisco CCNA, or a certification applicable to DoD 8140 workforce requirements.
- Military tactical communications experience, such as Army 18E/25C/25S/25U, Marine Corps 0621/0629, Air Force combat communications or TACP, Navy IT/ET, or Coast Guard IT, or equivalent contractor experience.
- Integration or testing of unmanned aircraft and ground, surface, or underwater vehicles, including ground control station datalinks and counter-UAS systems.
- RF spectrum monitoring and signals analysis, with experience in 4G/LTE or satellite backhaul systems such as Starlink, Iridium, or VSAT.
- Experience using Python for automation, equipment configuration, or log and telemetry analysis.
- Experience with Linux command-line tools, single-board computers such as Raspberry Pi, and network diagnostics using Wireshark.
- Experience with Jira and Confluence.
Field Operations Expectations
The engineer is expected to identify communications risks before events, troubleshoot methodically under time pressure, and maintain accurate readiness and configuration records. The role requires sound judgment in austere conditions, collaboration across teams, and willingness to cross-train in piloting, hardware integration, and demonstration support.
Benefits
- Premium medical, dental, and vision coverage with zero
and - for lists,
for prose.
Let's craft.
Note: The rules say "Output ONLY the HTML fragment — no /, no markdown code fences." So just the HTML tags.
I'll write:
Location: Austin, Texas; on-site when not deployed. Travel: Up to 50%, including international travel and deployments to combat zones. Clearance: U.S. citizen with an active DoD Secret clearance or eligibility for reinstatement. Reports to: Field Operations Lead.
About the role
NODA is a Veteran-owned, venture-backed technology company that is transforming how unmanned systems collaborate in complex, mission-critical environments. We are developing next-generation solutions that enable the autonomous orchestration of heterogeneous unmanned systems across air, sea, land, and space with vital applications in the defense, intelligence, and commercial sectors. Joining NODA means working on meaningful technology that pushes the boundaries of autonomy alongside a team that thrives on innovation, rapid iteration, and collaboration.
The Tactical Communications and Field Systems Engineer designs, integrates, and maintains the networks that connect NODA’s unmanned platforms, ground control stations, and customer systems. The role supports field testing, demonstrations, exercises, and operational deployments, with responsibility for communications readiness, troubleshooting, and technical documentation.
Responsibilities
- Develop mission communications plans covering radio and satellite links, mesh networks, IP addressing, encryption, antenna placement and separation, and backhaul.
- Establish primary, alternate, contingency, and emergency (PACE) options for critical links.
- Configure, test, and maintain communications between unmanned air, ground, surface, and underwater platforms and their ground control stations, including relay and retransmission sites for beyond-line-of-sight connectivity.
- Diagnose faults in radios, antennas, cabling, power systems, and IP networks, both on-site and remotely.
- Identify and mitigate external and self-generated interference, including jamming.
- Coordinate frequency and satellite access requests with range, military, and host-nation authorities.
- Manage communications security (COMSEC) key loading and accountability, and apply transmission security (TRANSEC) procedures.
- Fabricate and repair cables, harnesses, and connectors.
- Maintain equipment inventories, configuration records, spares, antennas, and field power systems.
- Survey and establish field sites, verify communications before deployment, and integrate command and control, telemetry, video, and link-health data into customer systems.
- Evaluate radios, waveforms, and antennas.
- Maintain network diagrams, configuration files, frequency records, communications plans, and after-action reports.
- Train and qualify teammates and customers on communications equipment and procedures.
- Work with Engineering, Product, and customer teams, and support site setup, teardown, and other field activities.
Requirements
- At least five years of experience planning, installing, operating, and maintaining tactical communications as a military communicator or field service representative, including deployments with combat or combat support units.
- Hands-on experience with HF, VHF, UHF, SATCOM, and mobile ad hoc or mesh networks, including configuration, encryption, link testing, and retransmission.
- Relevant systems include L3Harris AN/PRC-117G, AN/PRC-152, and AN/PRC-163; Motorola; TACSAT/MUOS; MPU5; Silvus; Doodle Labs; and Microhard.
- Working knowledge of RF propagation, antenna theory, and electromagnetic interference.
- Practical skills in RF cabling, connectors, grounding, field power, and soldering, with experience using spectrum analyzers, power and standing wave ratio meters, and multimeters.
- Proficiency in IP networking, including subnetting, DHCP, VLANs, routing, firewalls, VPNs, and Ethernet connections between radios, ground control stations, and payloads.
- Experience with COMSEC key handling and accountability, TRANSEC, emission control, spectrum coordination, and PACE planning in environments affected by electronic warfare or jamming.
- U.S. citizen with an active DoD Secret clearance or eligibility for reinstatement.
- A valid U.S. passport, or the ability to obtain one, and the ability to meet deployment medical and processing requirements.
- Ability to travel up to 50%, including internationally and to combat zones; work nights and weekends as required; and lift up to 60 pounds in demanding field conditions.
Preferred Qualifications
- CompTIA Security+, Network+, Linux+, Cisco CCNA, or a certification applicable to DoD 8140 workforce requirements.
- Military tactical communications experience, such as Army 18E/25C/25S/25U, Marine Corps 0621/0629, Air Force combat communications or TACP, Navy IT/ET, or Coast Guard IT, or equivalent contractor experience.
- Integration or testing of unmanned aircraft and ground, surface, or underwater vehicles, including ground control station datalinks and counter-UAS systems.
- RF spectrum monitoring and signals analysis, with experience in 4G/LTE or satellite backhaul systems such as Starlink, Iridium, or VSAT.
- Experience using Python for automation, equipment configuration, or log and telemetry analysis.
- Experience with Linux command-line tools, single-board computers such as Raspberry Pi, and network diagnostics using Wireshark.
- Experience with Jira and Confluence.
Field Operations Expectations
The engineer is expected to identify communications risks before events, troubleshoot methodically under time pressure, and maintain accurate readiness and configuration records. The role requires sound judgment in austere conditions, collaboration across teams, and willingness to cross-train in piloting, hardware integration, and demonstration support.
Benefits
- Premium medical, dental, and vision coverage with zero
for prose. Let's craft. Note: The rules say "Output ONLY the HTML fragment — no /, no markdown code fences." So just the HTML tags. I'll write:
Location: Austin, Texas; on-site when not deployed. Travel: Up to 50%, including international travel and deployments to combat zones. Clearance: U.S. citizen with an active DoD Secret clearance or eligibility for reinstatement. Reports to: Field Operations Lead.
About the role
NODA is a Veteran-owned, venture-backed technology company that is transforming how unmanned systems collaborate in complex, mission-critical environments. We are developing next-generation solutions that enable the autonomous orchestration of heterogeneous unmanned systems across air, sea, land, and space with vital applications in the defense, intelligence, and commercial sectors. Joining NODA means working on meaningful technology that pushes the boundaries of autonomy alongside a team that thrives on innovation, rapid iteration, and collaboration.
The Tactical Communications and Field Systems Engineer designs, integrates, and maintains the networks that connect NODA’s unmanned platforms, ground control stations, and customer systems. The role supports field testing, demonstrations, exercises, and operational deployments, with responsibility for communications readiness, troubleshooting, and technical documentation.
Responsibilities
- Develop mission communications plans covering radio and satellite links, mesh networks, IP addressing, encryption, antenna placement and separation, and backhaul.
- Establish primary, alternate, contingency, and emergency (PACE) options for critical links.
- Configure, test, and maintain communications between unmanned air, ground, surface, and underwater platforms and their ground control stations, including relay and retransmission sites for beyond-line-of-sight connectivity.
- Diagnose faults in radios, antennas, cabling, power systems, and IP networks, both on-site and remotely.
- Identify and mitigate external and self-generated interference, including jamming.
- Coordinate frequency and satellite access requests with range, military, and host-nation authorities.
- Manage communications security (COMSEC) key loading and accountability, and apply transmission security (TRANSEC) procedures.
- Fabricate and repair cables, harnesses, and connectors.
- Maintain equipment inventories, configuration records, spares, antennas, and field power systems.
- Survey and establish field sites, verify communications before deployment, and integrate command and control, telemetry, video, and link-health data into customer systems.
- Evaluate radios, waveforms, and antennas.
- Maintain network diagrams, configuration files, frequency records, communications plans, and after-action reports.
- Train and qualify teammates and customers on communications equipment and procedures.
- Work with Engineering, Product, and customer teams, and support site setup, teardown, and other field activities.
Requirements
- At least five years of experience planning, installing, operating, and maintaining tactical communications as a military communicator or field service representative, including deployments with combat or combat support units.
- Hands-on experience with HF, VHF, UHF, SATCOM, and mobile ad hoc or mesh networks, including configuration, encryption, link testing, and retransmission.
- Relevant systems include L3Harris AN/PRC-117G, AN/PRC-152, and AN/PRC-163; Motorola; TACSAT/MUOS; MPU5; Silvus; Doodle Labs; and Microhard.
- Working knowledge of RF propagation, antenna theory, and electromagnetic interference.
- Practical skills in RF cabling, connectors, grounding, field power, and soldering, with experience using spectrum analyzers, power and standing wave ratio meters, and multimeters.
- Proficiency in IP networking, including subnetting, DHCP, VLANs, routing, firewalls, VPNs, and Ethernet connections between radios, ground control stations, and payloads.
- Experience with COMSEC key handling and accountability, TRANSEC, emission control, spectrum coordination, and PACE planning in environments affected by electronic warfare or jamming.
- U.S. citizen with an active DoD Secret clearance or eligibility for reinstatement.
- A valid U.S. passport, or the ability to obtain one, and the ability to meet deployment medical and processing requirements.
- Ability to travel up to 50%, including internationally and to combat zones; work nights and weekends as required; and lift up to 60 pounds in demanding field conditions.
Preferred Qualifications
- CompTIA Security+, Network+, Linux+, Cisco CCNA, or a certification applicable to DoD 8140 workforce requirements.
- Military tactical communications experience, such as Army 18E/25C/25S/25U, Marine Corps 0621/0629, Air Force combat communications or TACP, Navy IT/ET, or Coast Guard IT, or equivalent contractor experience.
- Integration or testing of unmanned aircraft and ground, surface, or underwater vehicles, including ground control station datalinks and counter-UAS systems.
- RF spectrum monitoring and signals analysis, with experience in 4G/LTE or satellite backhaul systems such as Starlink, Iridium, or VSAT.
- Experience using Python for automation, equipment configuration, or log and telemetry analysis.
- Experience with Linux command-line tools, single-board computers such as Raspberry Pi, and network diagnostics using Wireshark.
- Experience with Jira and Confluence.
Field Operations Expectations
The engineer is expected to identify communications risks before events, troubleshoot methodically under time pressure, and maintain accurate readiness and configuration records. The role requires sound judgment in austere conditions, collaboration across teams, and willingness to cross-train in piloting, hardware integration, and demonstration support.
Benefits
- Premium medical, dental, and vision coverage with zero