Jobs · Virginia

C-UAS Hardware Development Lead

Drone.vet · Virginia, United States · 1 mo ago
$108k–$195k/yrFull-time
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 as heading. No Job ID. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Content: - Clearance: Active Secret with Ability to obtain a Top-Secret security clearance. - Location: Huntsville Alabama, Alexandria Virginia. Telecommuting may be available. - This position is contingent upon contract award. - Leidos is seeking a Hardware Development Lead to drive microelectronics hardware design, prototyping, integration, and testing for the Army’s Counter‑UAS (C‑UAS) Network Communication System (NCS). You’ll lead hardware engineering that enables secure, reliable network integration of M‑LIDS and FS‑LIDS systems supporting Short‑Range Air Defense (SHORAD) missions. This role owns hardware architecture decisions, directs a team of engineers/technicians, and ensures hardware solutions meet performance, security, and military standards while integrating tightly with software, RF, and cybersecurity teams. Key Duties (list): - Lead hardware architecture, design, prototyping, and microelectronics upgrades for NCS. - Define hardware interfaces, components, and data flows aligned with secure system architecture. - Direct circuit/board‑level design, component selection, and secure hardware/firmware integration. - Oversee hardware‑software‑network integration and support secure remote access/data transfer. - Lead hardware testing, qualification (environmental, EMI/EMC, reliability), and corrective actions. - Support RMF/ATO hardware requirements, patch assessments, and cybersecurity integration. - Present hardware technical approach at TIMs; maintain hardware sections of system documentation. - Manage and mentor hardware engineers and technicians within an Agile, cross‑functional workflow. Basic Qualifications: - Bachelor’s in EE/CE/Hardware Engineering + 10+ years hardware engineering (lead experience required). - Current Secret clearance with the ability to obtain a Top Secret security clearance. - Proven leadership in hardware design for networked/embedded/tactical microelectronics systems. - Experience with hardware‑software integration, secure communication hardware, and qualification testing. - Knowledge of DoD cybersecurity requirements and RMF/ATO as applied to hardware. - Strong technical writing and ability to brief government stakeholders. Preferred Qualifications: - Experience with C‑UAS/SHORAD/LIDS hardware programs. - Hardware development for fielded tactical systems (M‑LIDS/FS‑LIDS). - Microelectronics design for contested/DIL environments. Then there is marketing fluff: "If you're looking for comfort, keep scrolling..." etc. Remove. Then "Original Posting September 9, 2026" etc. Remove. Then "For U.S. Positions: While subject to change..." Remove. Then "Pay Range Pay Range $107,900.00 - $195,050.00 The Leidos pay range for this job level is a general guideline only and not a guarantee of compensation or salary. Additional factors considered in extending an offer include (but are not limited to) responsibilities of the job, education, experience, knowledge, skills, and abilities, as well as internal equity, alignment with market data, applicable bargaining agreement (if any), or other law." We need to include Pay section if posting actually states them. Yes, pay range given. So we include Pay section with that range. Schedule: Not mentioned. No schedule info. So we omit Schedule. Benefits: Not mentioned. No benefits. So omit Benefits. Skills: Could be derived from qualifications? But we need a Skills section only if posting has real specific content for it. The posting does not have a separate "Skills" bullet list; qualifications cover skills. But we could still create a Skills section summarizing? The instruction: "Prefer a few substantive sections over many thin ones." And "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should not create a Skills section unless there is explicit skills list. There isn't. So we omit Skills. We need sections: About the role (maybe a prose paragraph summarizing role), Responsibilities (list of duties), Requirements (maybe basic qualifications?), Qualifications (maybe preferred qualifications?), Pay. But we need to decide mapping: The instructions list possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. - About the role: could be the introductory paragraph describing the role and mission. - Responsibilities: the Key Duties list. - Requirements: Basic Qualifications (mandatory). - Qualifications: Preferred Qualifications (nice-to-have). - Pay: the pay range. We should not repeat job title as heading. We need to output only HTML fragment, no /. Use

for section headings. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. Thus we need to include all details from the posting, except boilerplate. Let's extract all substantive info: - Clearance: Active Secret with Ability to obtain a Top-Secret security clearance. - Location: Huntsville Alabama, Alexandria Virginia. Telecommuting may be available. - Contingent upon contract award. - Role description: Leidos is seeking a Hardware Development Lead to drive microelectronics hardware design, prototyping, integration, and testing for the Army’s Counter‑UAS (C‑UAS) Network Communication System (NCS). You’ll lead hardware engineering that enables secure, reliable network integration of M‑LIDS and FS‑LIDS systems supporting Short‑Range Air Defense (SHORAD) missions. This role owns hardware architecture decisions, directs a team of engineers/technicians, and ensures hardware solutions meet performance, security, and military standards while integrating tightly with software, RF, and cybersecurity teams. - Key Duties list (as above). - Basic Qualifications list (as above). - Preferred Qualifications list (as above). - Pay Range: $107,900.00 - $195,050.00 plus note that it's a guideline. We need to include that note? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include the note about guideline. Thus Pay section should contain a paragraph with the range and the note. We should not include "Original Posting September 9, 2026", "For U.S. Positions..." etc. We should also include the location and clearance and contingency maybe in About the role paragraph. Let's craft About the role paragraph: Leidos is seeking a Hardware Development Lead to drive microelectronics hardware design, prototyping, integration, and testing for the Army’s Counter‑UAS (C‑UAS) Network Communication System (NCS). The role leads hardware engineering enabling secure, reliable network integration of M‑LIDS and FS‑LIDS systems supporting Short‑Range Air Defense (SHORAD) missions. It owns hardware architecture decisions, directs a team of engineers/technicians, and ensures hardware solutions meet performance, security, and military standards while integrating tightly with software, RF, and cybersecurity teams. The position requires an Active Secret clearance with ability to obtain a Top‑Secret clearance, is located in Huntsville, AL or Alexandria, VA with possible telecommuting, and is contingent upon contract award. That captures location, clearance, contingency. Now Responsibilities: list of Key Duties. Requirements: Basic Qualifications list. Qualifications: Preferred Qualifications list. Pay: paragraph with range and note. We must not include Skills, Benefits, Schedule. Now ensure we use proper HTML:

    About the role

    ...

    etc. For lists:
    • ...
    We need to preserve all details exactly as in posting, but we can rephrase slightly? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should not lose any detail. We can keep the exact phrasing but we can combine into prose. However we must not invent or summarize away detail. Summarizing may be okay if we keep all details? The instruction says do NOT summarize away detail. So we should avoid omitting any detail. We need to include each bullet point exactly as given, maybe as list items. Thus for Responsibilities we should output each duty as a list item, preserving the exact phrasing. Similarly for Requirements (Basic Qualifications) and Qualifications (Preferred Qualifications). We need to ensure we don't lose any nuance. Let's copy the exact bullet points from the posting: Key Duties: - Lead hardware architecture, design, prototyping, and microelectronics upgrades for NCS. - Define hardware interfaces, components, and data flows aligned with secure system architecture. - Direct circuit/board‑level design, component selection, and secure hardware/firmware integration. - Oversee hardware‑software‑network integration and support secure remote access/data transfer. - Lead hardware testing, qualification (environmental, EMI/EMC, reliability), and corrective actions. - Support RMF/ATO hardware requirements, patch assessments, and cybersecurity integration. - Present hardware technical approach at TIMs; maintain hardware sections of system documentation. - Manage and mentor hardware engineers and technicians within an Agile, cross‑functional workflow. Basic Qualifications: - Bachelor’s in EE/CE/Hardware Engineering + 10+ years hardware engineering (lead experience required). - Current Secret clearance with the ability to obtain a Top Secret security clearance. - Proven leadership in hardware design for networked/embedded/tactical microelectronics systems. - Experience with hardware‑software integration, secure communication hardware, and qualification testing. - Knowledge of DoD cybersecurity requirements and RMF/ATO as applied to hardware. - Strong technical writing and ability to brief government stakeholders. Preferred Qualifications: - Experience with C‑UAS/SHORAD/LIDS hardware programs. - Hardware development for fielded tactical systems (M‑LIDS/FS‑LIDS). - Microelectronics design for contested/DIL environments. Now About the role paragraph: we need to include the introductory sentences plus location, clearance, contingency. Let's capture the exact sentences from posting: "Leidos is seeking a Hardware Development Lead to drive microelectronics hardware design, prototyping, integration, and testing for the Army’s Counter‑UAS (C‑UAS) Network Communication System (NCS). You’ll lead hardware engineering that enables secure, reliable network integration of M‑LIDS and FS‑LIDS systems supporting Short‑Range Air Defense (SHORAD) missions. This role owns hardware architecture decisions, directs a team of engineers/technicians, and ensures hardware solutions meet performance, security, and military standards while integrating tightly with software, RF, and cybersecurity teams." Then we add location, clearance, contingency: "Clearance: Active Secret with Ability to obtain a Top-Secret security clearance. Location: Huntsville Alabama, Alexandria Virginia. Telecommuting may be available . This position is contingent upon contract award." We should combine into a paragraph, preserving all info. Now Pay: The posting says: "Pay Range Pay Range $107,900.00 - $195,050.00 The Leidos pay range for this job level is a general guideline only and not a guarantee of compensation or salary. Additional factors considered in extending an offer include (but are not limited to) responsibilities of the job, education, experience, knowledge, skills, and abilities, as well as internal equity, alignment with market data, applicable bargaining agreement (if any), or other law." Note there is a duplicate "Pay Range". We should preserve the info but not repeat unnecessarily? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The duplicate phrase "Pay Range" appears twice; we could keep it as is or we could combine. But to preserve all substantive information, we should keep the exact text? However the duplicate is likely a typo; but we should not invent or summarize away

Similar jobs

C-UAS Engineer

LMINew York, NY· 7 mo ago
Engineeringapply on careers-lmi.icims.com

C-UAS Program Lead

Parsons CorporationAlexandria, VA· 3 mo ago
Consulting$134k–$241k/yrapply on parsons.wd5.myworkdayjobs.com

C-UAS Test Engineer

Parsons CorporationSummit Point, WV· 4 mo ago
Engineering$75k–$131k/yrapply on parsons.wd5.myworkdayjobs.com