Digital Network Exploitation Analyst (DNEA)
AV · Annapolis Junction, MD · 4 wk ago
On-siteManagement$84k–$210k/yrFull-time
We need to output HTML fragment with sections: h3 headings for sections present: About the role? The posting includes "Job Description" and "Responsibilities", "Basic Qualifications", "Salary Range", "Benefits", "Who We Are", "What We Do". Also "ITAR Requirement" maybe but that's boilerplate? It's specific content about ITAR requirement; but it's not a standard heading list; we could include as a section maybe "ITAR Requirement". However instruction: include a section ONLY when posting has real, specific content for it. The ITAR Requirement paragraph is specific content, so we could include a section with heading "ITAR Requirement". However they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not limited to those. We can use other headings if appropriate. Probably better to stick to those standard headings: About the role (maybe from Job Description), Responsibilities, Requirements (or Qualifications), Benefits, Pay, Schedule. They said prefer a few substantive sections over many thin ones. So we can combine some.
We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings (none present). Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out EEO statements, "Principals only need apply. NO agencies please." maybe that's application instruction? It's a instruction to applicants; we should remove application instructions. Also "For more information about our company benefit offerings please visit: ..." maybe that's application instruction? It's a link; could be considered boilerplate; but it's part of benefits description. Might keep the benefits description but remove the link? The instruction: remove application instructions. The link is not exactly an instruction to apply; it's info about benefits. Might keep but could be considered navigation? Probably safe to keep the benefits description but drop the URL? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The URL is not navigation? It's a link to benefits; could be considered navigation. Safer to remove it. Also "We also encourage you to review our company website at http://www.avinc.com to learn more about us." That's navigation; remove.
Also "Who We Are" and "What We Do" are company description; could be considered boilerplate? It's substantive about the company; maybe keep as "About the Company" but not in list of headings. Could combine into "About the role" maybe not. The instruction: Prefer a few substantive sections over many thin ones. So we could have sections: About the role (combining Job Description and Who We Are/What We Do?), Responsibilities, Requirements (Basic Qualifications), Pay (Salary Range), Benefits. Possibly also ITAR Requirement as a section? Might be thin but it's specific. Could combine into Requirements? Not really. Could add a section "Security & Compliance". But they didn't list that as example. Might be better to include as a separate section "ITAR Requirement". However they said use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't forbid other headings, but they gave examples. Safer to stick to those. ITAR requirement could be placed under Requirements or Qualifications as a bullet? It's a requirement: "This position requires access to information that is subject to compliance with ITAR/EAR...". Could be added as a bullet under Requirements. That would preserve info.
Similarly, "Who We Are" and "What We Do" could be placed under About the role? The About the role section could contain a brief description of the role and company. But we must preserve all substantive information; we can include that info in a paragraph under About the role.
Thus sections: About the role (h3), Responsibilities (h3), Requirements (h3), Pay (h3), Benefits (h3). Possibly Schedule? Not mentioned except benefits includes "a 9/80 work schedule". That's schedule info; we could include under Benefits or Schedule. Since they said create Schedule section only if posting actually states them. It does state "a 9/80 work schedule". So we could have a Schedule section. But we already have Benefits section that includes that detail; we could split. Prefer few substantive sections; maybe combine schedule into Benefits. But they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state schedule, so we could create Schedule section. However we already have Benefits section; we could have both Benefits and Schedule. That's okay.
But we need to avoid filler like "commensurate with experience". Not present.
Now extract content:
Job Description: "The primary role of the Digital Network Exploitation Analyst is to analyze network and cybersecurity data to identify exploitation opportunities and support mission operations. This role applies all-source intelligence and advanced analytic tradecraft to produce actionable insights in collaboration with mission partners."
Responsibilities (list):
- Analyze target networks and develop exploitation plans using all-source data.
- Work with SIGINT and cybersecurity data across the OSI model.
- Collaborate with military, government, and contractor teams to address mission-critical intelligence needs.
- Develop and share new tradecraft and techniques as technologies evolve.
- Use your analytical skills to derive insights, distill findings, and drive forward innovative solutions.
Basic Qualifications (list):
- Bachelor’s degree in Computer Science or a related technical field (equivalent military training may be considered)
- Minimum of 8+ years of relevant experience in cybersecurity, network exploitation, or related fields.
- Strong understanding of IP core infrastructure, network traffic analysis, and cybersecurity.
- Experience with SIGINT analysis, vulnerability assessments, or penetration testing.
- Demonstrated ability to work with multi-disciplinary teams in high-stakes environments.
- An active TS/SCI clearance with polygraph
Also ITAR requirement: "This position requires access to information that is subject to compliance with the International Traffic Arms Regulations (“ITAR”) and/or the Export Administration Regulations (“EAR”). In order to comply with the requirements of the ITAR and/or the EAR, applicants will be asked to provide specific documentation to verify U.S. person status under the ITAR and the EAR. A “U.S. person” according to their definition is a U.S. citizen, U.S. lawful permanent resident (green card holder), or protected individual such as a refugee, or asylee. See 22 CFR 120.15. Some positions will require current U.S. Citizenship due to contract requirements."
We can incorporate as a bullet under Requirements: "Must be a U.S. person (U.S. citizen, lawful permanent resident, refugee, or asylee) to comply with ITAR/EAR; some positions require current U.S. Citizenship."
Salary Range: "$83,500 - $210,000" plus note about AV pay range being guideline. We should preserve the substantive info: the salary range and the note that it's a guideline. So include both.
Benefits: "AV offers an excellent benefits package including medical, dental vision, 401K with company matching, a 9/80 work schedule and a paid holiday shutdown." Also maybe mention "For more information about our company benefit offerings please visit: ..." we remove link. Also "We also encourage you to review our company website at http://www.avinc.com to learn more about us." remove.
Who We Are and What We Do: company description. We'll incorporate into About the role paragraph maybe as a separate paragraph after role description.
Thus About the role content: combine Job Description + Who We Are + What We Do.
Who We Are: "Based in California, AeroVironment (AVAV) is a global leader in unmanned aircraft systems (UAS) and tactical missile systems. Founded in 1971 by celebrated physicist and engineer, Dr. Paul MacCready, we’ve been at the leading edge of technical innovation for more than 45 years. Be a part of the team that developed the world’s most widely used military drones and created the first submarine-launched reconnaissance drone, and has seven innovative vehicles that are part of the Smithsonian Institution’s permanent collection in Washington, DC. Join us today in developing the next generation of small UAS and tactical missile systems that will deliver more actionable intelligence to our customers so they can proceed with certainty – and succeed."
What We Do: "Building on a history of technological innovation, AeroVironment designs, develops, produces, and supports an advanced portfolio of unmanned aircraft systems (UAS) and tactical missile systems. Agencies of the U.S. Department of Defense and allied military services use the company’s hand-launched UAS to provide situational awareness to tactical operating units through real-time, airborne reconnaissance, surveillance, and target acquisition. We are proud to be an EEO/AA Equal Opportunity Employer, including disability/veterans. AeroVironment, Inc. is an Equal Employment Opportunity (EEO) employer and welcomes all qualified applicants. Qualified applicants will receive fair and impartial consideration without regard to race, sex, color, religion, national origin, age, disability, protected veteran status, genetic data, sexual orientation, gender identity or other legally protected status."
But EEO statement is boilerplate; we should remove EEO/AA lines. So we need to strip out EEO/AA Equal Opportunity Employer lines. The instruction: remove EEO/equal-opportunity boilerplate. So we must delete those sentences. So from What We Do we keep the descriptive parts before EEO statement. So keep: "Building on a history of technological innovation, AeroVironment designs, develops, produces, and supports an advanced portfolio of unmanned aircraft systems (UAS) and tactical missile systems. Agencies of the U.S. Department of Defense and allied military services use the company’s hand-launched UAS to provide situational awareness to tactical operating units through real-time, airborne reconnaissance, surveillance, and target acquisition." Then stop before EEO.
Thus About the role paragraph will include Job Description + Who We Are + What We Do (without EEO). Ensure we preserve all substantive info.
Now produce HTML:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not limited to those. We can use other headings if appropriate. Probably better to stick to those standard headings: About the role (maybe from Job Description), Responsibilities, Requirements (or Qualifications), Benefits, Pay, Schedule. They said prefer a few substantive sections over many thin ones. So we can combine some.
We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings (none present). Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out EEO statements, "Principals only need apply. NO agencies please." maybe that's application instruction? It's a instruction to applicants; we should remove application instructions. Also "For more information about our company benefit offerings please visit: ..." maybe that's application instruction? It's a link; could be considered boilerplate; but it's part of benefits description. Might keep the benefits description but remove the link? The instruction: remove application instructions. The link is not exactly an instruction to apply; it's info about benefits. Might keep but could be considered navigation? Probably safe to keep the benefits description but drop the URL? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The URL is not navigation? It's a link to benefits; could be considered navigation. Safer to remove it. Also "We also encourage you to review our company website at http://www.avinc.com to learn more about us." That's navigation; remove.
Also "Who We Are" and "What We Do" are company description; could be considered boilerplate? It's substantive about the company; maybe keep as "About the Company" but not in list of headings. Could combine into "About the role" maybe not. The instruction: Prefer a few substantive sections over many thin ones. So we could have sections: About the role (combining Job Description and Who We Are/What We Do?), Responsibilities, Requirements (Basic Qualifications), Pay (Salary Range), Benefits. Possibly also ITAR Requirement as a section? Might be thin but it's specific. Could combine into Requirements? Not really. Could add a section "Security & Compliance". But they didn't list that as example. Might be better to include as a separate section "ITAR Requirement". However they said use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't forbid other headings, but they gave examples. Safer to stick to those. ITAR requirement could be placed under Requirements or Qualifications as a bullet? It's a requirement: "This position requires access to information that is subject to compliance with ITAR/EAR...". Could be added as a bullet under Requirements. That would preserve info.
Similarly, "Who We Are" and "What We Do" could be placed under About the role? The About the role section could contain a brief description of the role and company. But we must preserve all substantive information; we can include that info in a paragraph under About the role.
Thus sections: About the role (h3), Responsibilities (h3), Requirements (h3), Pay (h3), Benefits (h3). Possibly Schedule? Not mentioned except benefits includes "a 9/80 work schedule". That's schedule info; we could include under Benefits or Schedule. Since they said create Schedule section only if posting actually states them. It does state "a 9/80 work schedule". So we could have a Schedule section. But we already have Benefits section that includes that detail; we could split. Prefer few substantive sections; maybe combine schedule into Benefits. But they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state schedule, so we could create Schedule section. However we already have Benefits section; we could have both Benefits and Schedule. That's okay.
But we need to avoid filler like "commensurate with experience". Not present.
Now extract content:
Job Description: "The primary role of the Digital Network Exploitation Analyst is to analyze network and cybersecurity data to identify exploitation opportunities and support mission operations. This role applies all-source intelligence and advanced analytic tradecraft to produce actionable insights in collaboration with mission partners."
Responsibilities (list):
- Analyze target networks and develop exploitation plans using all-source data.
- Work with SIGINT and cybersecurity data across the OSI model.
- Collaborate with military, government, and contractor teams to address mission-critical intelligence needs.
- Develop and share new tradecraft and techniques as technologies evolve.
- Use your analytical skills to derive insights, distill findings, and drive forward innovative solutions.
Basic Qualifications (list):
- Bachelor’s degree in Computer Science or a related technical field (equivalent military training may be considered)
- Minimum of 8+ years of relevant experience in cybersecurity, network exploitation, or related fields.
- Strong understanding of IP core infrastructure, network traffic analysis, and cybersecurity.
- Experience with SIGINT analysis, vulnerability assessments, or penetration testing.
- Demonstrated ability to work with multi-disciplinary teams in high-stakes environments.
- An active TS/SCI clearance with polygraph
Also ITAR requirement: "This position requires access to information that is subject to compliance with the International Traffic Arms Regulations (“ITAR”) and/or the Export Administration Regulations (“EAR”). In order to comply with the requirements of the ITAR and/or the EAR, applicants will be asked to provide specific documentation to verify U.S. person status under the ITAR and the EAR. A “U.S. person” according to their definition is a U.S. citizen, U.S. lawful permanent resident (green card holder), or protected individual such as a refugee, or asylee. See 22 CFR 120.15. Some positions will require current U.S. Citizenship due to contract requirements."
We can incorporate as a bullet under Requirements: "Must be a U.S. person (U.S. citizen, lawful permanent resident, refugee, or asylee) to comply with ITAR/EAR; some positions require current U.S. Citizenship."
Salary Range: "$83,500 - $210,000" plus note about AV pay range being guideline. We should preserve the substantive info: the salary range and the note that it's a guideline. So include both.
Benefits: "AV offers an excellent benefits package including medical, dental vision, 401K with company matching, a 9/80 work schedule and a paid holiday shutdown." Also maybe mention "For more information about our company benefit offerings please visit: ..." we remove link. Also "We also encourage you to review our company website at http://www.avinc.com to learn more about us." remove.
Who We Are and What We Do: company description. We'll incorporate into About the role paragraph maybe as a separate paragraph after role description.
Thus About the role content: combine Job Description + Who We Are + What We Do.
Who We Are: "Based in California, AeroVironment (AVAV) is a global leader in unmanned aircraft systems (UAS) and tactical missile systems. Founded in 1971 by celebrated physicist and engineer, Dr. Paul MacCready, we’ve been at the leading edge of technical innovation for more than 45 years. Be a part of the team that developed the world’s most widely used military drones and created the first submarine-launched reconnaissance drone, and has seven innovative vehicles that are part of the Smithsonian Institution’s permanent collection in Washington, DC. Join us today in developing the next generation of small UAS and tactical missile systems that will deliver more actionable intelligence to our customers so they can proceed with certainty – and succeed."
What We Do: "Building on a history of technological innovation, AeroVironment designs, develops, produces, and supports an advanced portfolio of unmanned aircraft systems (UAS) and tactical missile systems. Agencies of the U.S. Department of Defense and allied military services use the company’s hand-launched UAS to provide situational awareness to tactical operating units through real-time, airborne reconnaissance, surveillance, and target acquisition. We are proud to be an EEO/AA Equal Opportunity Employer, including disability/veterans. AeroVironment, Inc. is an Equal Employment Opportunity (EEO) employer and welcomes all qualified applicants. Qualified applicants will receive fair and impartial consideration without regard to race, sex, color, religion, national origin, age, disability, protected veteran status, genetic data, sexual orientation, gender identity or other legally protected status."
But EEO statement is boilerplate; we should remove EEO/AA lines. So we need to strip out EEO/AA Equal Opportunity Employer lines. The instruction: remove EEO/equal-opportunity boilerplate. So we must delete those sentences. So from What We Do we keep the descriptive parts before EEO statement. So keep: "Building on a history of technological innovation, AeroVironment designs, develops, produces, and supports an advanced portfolio of unmanned aircraft systems (UAS) and tactical missile systems. Agencies of the U.S. Department of Defense and allied military services use the company’s hand-launched UAS to provide situational awareness to tactical operating units through real-time, airborne reconnaissance, surveillance, and target acquisition." Then stop before EEO.
Thus About the role paragraph will include Job Description + Who We Are + What We Do (without EEO). Ensure we preserve all substantive info.
Now produce HTML:
About the role
... combined paragraphs ...
Responsibilities
- ... ...
Requirements
- ... ...
Pay
Salary Range: $83,500 - $210,000. The AV pay range for this job level is a general guideline only and not a guarantee of compensation or salary. Determination of official compensation or salary relies on several factors including, but not limited to, level of position, job responsibilities, geographic location, scope of relevant work experience, educational background, certifications, contract-specific affordability, organizational requirements, alignment with local internal equity as well as alignment with market data.
Benefits
- Medical
- Dental
- Vision
- 401K with company matching
- 9/80 work schedule
- Paid holiday shutdown