Cyber Security Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include based on content.
We have:
- About L3Harris Technologies (company overview). Could be "About the role"? Actually "About the role" is a heading suggestion but we can use "About L3Harris Technologies" as a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not strict list; we can use those headings if appropriate. For company overview maybe "About the company" but not in list. Could use "About the role" for role description? But we have Job Description separate. Perhaps we can have sections: About the role (maybe combine company overview and job description?), Responsibilities (Essential Functions), Requirements (Qualifications), Skills (Preferred Additional Skills), Benefits, Pay, Schedule.
We have schedule info: "Job Schedule: 9/80: Employees work 9 out of every 14 days – totaling 80 hours worked – and have every other Friday off". That's specific, so we can include Schedule section.
Pay: salary range given: "$80,500 - $149,500". That's specific, so include Pay section.
Benefits: list of benefits given: health and disability insurance, 401(k) match, flexible spending accounts, EAP, education assistance, parental leave, paid time off, company-paid holidays. So include Benefits.
Qualifications: we have qualifications bullet: Bachelor’s Degree in Engineering discipline and minimum 4 years of developing embedded software-based engineering solutions. Graduate Degree and a minimum of 2 years of prior related experience. In lieu of a degree, minimum of 8 years of prior related experience. That's qualifications.
Requirements: maybe essential functions? Actually "Essential Functions" list includes experience with security requirements analysis, etc. Could be considered Responsibilities? The job description includes duties. We can treat "Job Description" as Responsibilities. The "Essential Functions" could be Requirements? But we already have Qualifications. Might combine.
Preferred Additional Skills: list: Strong verbal and written communication skills. Radio communications or networking experience preferred. Knowledge of configuration management tools. That's Skills.
We also have "About L3Harris Technologies" which is company overview. Could be placed under "About the role"? But maybe better to have a section "About the company". However instruction only gave examples; but we can still use any heading as long as it's . It didn't forbid other headings. It said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings; but we could also use others? Safer to stick to those headings. So we need to map content to those headings.
We have:
- About the role: could include company overview and job description? But we also have Responsibilities separate. Maybe About the role = brief summary of role (maybe from Job Description first sentence). Responsibilities = detailed duties from Job Description and Essential Functions. Requirements = maybe security clearance, citizenship, etc. Qualifications = education/experience. Skills = preferred additional skills. Benefits, Pay, Schedule.
We must not repeat job title as heading. Not include Job ID etc.
We need to preserve all substantive information. So we need to include all details from the posting, except boilerplate.
Let's extract substantive content:
Company overview: "L3Harris is dedicated to recruiting and developing high-performing talent who are passionate about what they do. Our employees are unified in a shared dedication to our customers’ mission and quest for professional growth. L3Harris provides an inclusive, engaging environment designed to empower employees and promote work-life success. Fundamental to our culture is an unwavering focus on values, dedication to our communities, and commitment to excellence in everything we do. L3Harris is the Trusted Disruptor in defense tech. With customers’ mission-critical needs always in mind, our employees deliver end-to-end technology solutions connecting the space, air, land, sea and cyber domains in the interest of national security. L3Harris Technologies is an agile global aerospace and defense technology innovator, delivering end-to-end solutions that meet customers’ mission-critical needs. The company provides advanced defense and commercial technologies across space, air, land, sea and cyber domains. L3Harris has approximately $18 billion in annual revenue and 47,000 employees, with customers in more than 100 countries."
Job Description: "The Information Security Systems Engineer will be involved in Information Assurance (IA) related architecture development, CONOPS development, trade studies, requirements analysis and flow down to hardware/software configuration items as well as requirements validation and verification. This position requires DoD IA expertise to support embedment of cryptographic components within tactical radio platforms. Candidate will analyze and allocate system security requirements, such as those imposed by NSA, and those under DOD Information Assurance Certification and Accreditation Process (RMF), as well as National Information Assurance Partnership (NIAP) Common Criteria and National Institute of Standards and Technology (NIST) FIPS standards. The Candidate will also oversee and prepare NSA security certification documents, such as System Evaluation Document (SED), Key and Certificate Management Plan (KCMP), Software/Hardware Requirements and Design Specifications (SHRS/SHDD), Security Verification (SV) Test Plans and Reports, Physical Configuration Audit (PCA) Plans and Reports. The candidate should have a good understanding of DoD Configuration Management (CM) processes and management of formal Engineering Change Proposals (ECP). The Candidate will interact with mechanical, electrical and SW engineers to make sure designs meet security requirements."
Essential Functions: "Must have experience with security requirements analysis and specification generation. Highly motivated, a self starter, and able to operate with little supervision in diverse environments.Must have a successful track record in planning, executing, and tracking personal task assignments.Experience with emerging security standards and evolution of NSA certification processes.Must have experience with certification of secure architectures.Active Secret U.S. Security Clearance or ability to obtain one.US citizenship is required."
Qualifications: "Bachelor’s Degree in Engineering discipline and minimum 4 years of developing embedded software-based engineering solutions. Graduate Degree and a minimum of 2 years of prior related experience. In lieu of a degree, minimum of 8 years of prior related experience."
Preferred Additional Skills: "Strong verbal and written communication skills.Radio communications or networking experience preferredKnowledge of configuration management tools"
Pay: "In compliance with pay transparency requirements, the salary range for this role in NY is $80,500 - $149,500. This is not a guarantee of compensation or salary, as final offer amount may vary based on factors including but not limited to experience and geographic location."
Benefits: "L3Harris also offers a variety of benefits, including health and disability insurance, 401(k) match, flexible spending accounts, EAP, education assistance, parental leave, paid time off, and company-paid holidays. The specific programs and options available to an employee may vary depending on date of hire, schedule type, and the applicability of collective bargaining agreements."
Schedule: "Job Schedule: 9/80: Employees work 9 out of every 14 days – totaling 80 hours worked – and have every other Friday off"
Location: "Job Location: Rochester, NY" - location is substantive but not a heading per examples. Could be placed in a short paragraph maybe under About the role? Or we could add a
with location. The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata but still substantive; we can include in a short
.
We must not include boilerplate: EEO, E-Verify, drug-free workplace, etc. Remove those.
Now decide sections.
We could have:
About the role
- includes company overview and maybe location? But we also have Responsibilities separate.
Better: Use sections: About the role (company overview + location?), Responsibilities (Job Description + Essential Functions?), Requirements (security clearance, citizenship?), Qualifications (education/experience), Skills (preferred additional skills), Benefits, Pay, Schedule.
But we need to avoid duplication. Essential Functions includes some requirements like security clearance, citizenship, experience. Those could be under Requirements. Responsibilities could be the job description duties.
Let's map:
About the role: company overview paragraph(s). Could also include location? Might be okay.
Responsibilities: the job description duties (the paragraph about IA related architecture development, etc.) plus maybe the interaction with engineers.
Requirements: security clearance, US citizenship, experience with security requirements analysis, etc. Actually Essential Functions list includes many "Must have experience..." which are more like requirements. Could be Requirements.
Qualifications: education/experience.
Skills: preferred additional skills.
Benefits: list.
Pay: salary range.
Schedule: 9/80.
We must ensure we don't create sections with filler. All have real content.
Now format: Use for each heading. Use
for prose. Use
- for lists.
We need to preserve all substantive information. Let's extract each piece precisely.
Company overview: multiple sentences. We'll combine into one or two paragraphs.
Location: "Job Location: Rochester, NY". We'll put in a short
maybe under About the role.
Responsibilities: The job description paragraph(s). Let's copy exactly:
"The Information Security Systems Engineer will be involved in Information Assurance (IA) related architecture development, CONOPS development, trade studies, requirements analysis and flow down to hardware/software configuration items as well as requirements validation and verification. This position requires DoD IA expertise to support embedment of cryptographic components within tactical radio platforms. Candidate will analyze and allocate system security requirements, such as those imposed by NSA, and those under DOD Information Assurance Certification and Accreditation Process (RMF), as well as National Information Assurance Partnership (NIAP) Common Criteria and National Institute of Standards and Technology (NIST) FIPS standards. The Candidate will also oversee and prepare NSA security certification documents, such as System Evaluation Document (SED), Key and Certificate Management Plan (KCMP), Software/Hardware Requirements and Design Specifications (SHRS/SHDD), Security Verification (SV) Test Plans and Reports, Physical Configuration Audit (PCA) Plans and Reports. The candidate should have a good understanding of DoD Configuration Management (CM) processes and management of formal Engineering Change Proposals (ECP). The Candidate will interact with mechanical, electrical and SW engineers to make sure designs meet security requirements."
We could split into two paragraphs for readability but it's fine as one.
Requirements: Essential Functions list items:
- Must have experience with security requirements analysis and specification generation.
- Highly motivated, a self
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. We have: - About L3Harris Technologies (company overview). Could be "About the role"? Actually "About the role" is a heading suggestion but we can use "About L3Harris Technologies" as a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not strict list; we can use those headings if appropriate. For company overview maybe "About the company" but not in list. Could use "About the role" for role description? But we have Job Description separate. Perhaps we can have sections: About the role (maybe combine company overview and job description?), Responsibilities (Essential Functions), Requirements (Qualifications), Skills (Preferred Additional Skills), Benefits, Pay, Schedule.
We have schedule info: "Job Schedule: 9/80: Employees work 9 out of every 14 days – totaling 80 hours worked – and have every other Friday off". That's specific, so we can include Schedule section.
Pay: salary range given: "$80,500 - $149,500". That's specific, so include Pay section.
Benefits: list of benefits given: health and disability insurance, 401(k) match, flexible spending accounts, EAP, education assistance, parental leave, paid time off, company-paid holidays. So include Benefits.
Qualifications: we have qualifications bullet: Bachelor’s Degree in Engineering discipline and minimum 4 years of developing embedded software-based engineering solutions. Graduate Degree and a minimum of 2 years of prior related experience. In lieu of a degree, minimum of 8 years of prior related experience. That's qualifications.
Requirements: maybe essential functions? Actually "Essential Functions" list includes experience with security requirements analysis, etc. Could be considered Responsibilities? The job description includes duties. We can treat "Job Description" as Responsibilities. The "Essential Functions" could be Requirements? But we already have Qualifications. Might combine.
Preferred Additional Skills: list: Strong verbal and written communication skills. Radio communications or networking experience preferred. Knowledge of configuration management tools. That's Skills.
We also have "About L3Harris Technologies" which is company overview. Could be placed under "About the role"? But maybe better to have a section "About the company". However instruction only gave examples; but we can still use any heading as long as it's . It didn't forbid other headings. It said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings; but we could also use others? Safer to stick to those headings. So we need to map content to those headings.
We have:
- About the role: could include company overview and job description? But we also have Responsibilities separate. Maybe About the role = brief summary of role (maybe from Job Description first sentence). Responsibilities = detailed duties from Job Description and Essential Functions. Requirements = maybe security clearance, citizenship, etc. Qualifications = education/experience. Skills = preferred additional skills. Benefits, Pay, Schedule.
We must not repeat job title as heading. Not include Job ID etc.
We need to preserve all substantive information. So we need to include all details from the posting, except boilerplate.
Let's extract substantive content:
Company overview: "L3Harris is dedicated to recruiting and developing high-performing talent who are passionate about what they do. Our employees are unified in a shared dedication to our customers’ mission and quest for professional growth. L3Harris provides an inclusive, engaging environment designed to empower employees and promote work-life success. Fundamental to our culture is an unwavering focus on values, dedication to our communities, and commitment to excellence in everything we do. L3Harris is the Trusted Disruptor in defense tech. With customers’ mission-critical needs always in mind, our employees deliver end-to-end technology solutions connecting the space, air, land, sea and cyber domains in the interest of national security. L3Harris Technologies is an agile global aerospace and defense technology innovator, delivering end-to-end solutions that meet customers’ mission-critical needs. The company provides advanced defense and commercial technologies across space, air, land, sea and cyber domains. L3Harris has approximately $18 billion in annual revenue and 47,000 employees, with customers in more than 100 countries."
Job Description: "The Information Security Systems Engineer will be involved in Information Assurance (IA) related architecture development, CONOPS development, trade studies, requirements analysis and flow down to hardware/software configuration items as well as requirements validation and verification. This position requires DoD IA expertise to support embedment of cryptographic components within tactical radio platforms. Candidate will analyze and allocate system security requirements, such as those imposed by NSA, and those under DOD Information Assurance Certification and Accreditation Process (RMF), as well as National Information Assurance Partnership (NIAP) Common Criteria and National Institute of Standards and Technology (NIST) FIPS standards. The Candidate will also oversee and prepare NSA security certification documents, such as System Evaluation Document (SED), Key and Certificate Management Plan (KCMP), Software/Hardware Requirements and Design Specifications (SHRS/SHDD), Security Verification (SV) Test Plans and Reports, Physical Configuration Audit (PCA) Plans and Reports. The candidate should have a good understanding of DoD Configuration Management (CM) processes and management of formal Engineering Change Proposals (ECP). The Candidate will interact with mechanical, electrical and SW engineers to make sure designs meet security requirements."
Essential Functions: "Must have experience with security requirements analysis and specification generation. Highly motivated, a self starter, and able to operate with little supervision in diverse environments.Must have a successful track record in planning, executing, and tracking personal task assignments.Experience with emerging security standards and evolution of NSA certification processes.Must have experience with certification of secure architectures.Active Secret U.S. Security Clearance or ability to obtain one.US citizenship is required."
Qualifications: "Bachelor’s Degree in Engineering discipline and minimum 4 years of developing embedded software-based engineering solutions. Graduate Degree and a minimum of 2 years of prior related experience. In lieu of a degree, minimum of 8 years of prior related experience."
Preferred Additional Skills: "Strong verbal and written communication skills.Radio communications or networking experience preferredKnowledge of configuration management tools"
Pay: "In compliance with pay transparency requirements, the salary range for this role in NY is $80,500 - $149,500. This is not a guarantee of compensation or salary, as final offer amount may vary based on factors including but not limited to experience and geographic location."
Benefits: "L3Harris also offers a variety of benefits, including health and disability insurance, 401(k) match, flexible spending accounts, EAP, education assistance, parental leave, paid time off, and company-paid holidays. The specific programs and options available to an employee may vary depending on date of hire, schedule type, and the applicability of collective bargaining agreements."
Schedule: "Job Schedule: 9/80: Employees work 9 out of every 14 days – totaling 80 hours worked – and have every other Friday off"
Location: "Job Location: Rochester, NY" - location is substantive but not a heading per examples. Could be placed in a short paragraph maybe under About the role? Or we could add a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings; but we could also use others? Safer to stick to those headings. So we need to map content to those headings. We have: - About the role: could include company overview and job description? But we also have Responsibilities separate. Maybe About the role = brief summary of role (maybe from Job Description first sentence). Responsibilities = detailed duties from Job Description and Essential Functions. Requirements = maybe security clearance, citizenship, etc. Qualifications = education/experience. Skills = preferred additional skills. Benefits, Pay, Schedule. We must not repeat job title as heading. Not include Job ID etc. We need to preserve all substantive information. So we need to include all details from the posting, except boilerplate. Let's extract substantive content: Company overview: "L3Harris is dedicated to recruiting and developing high-performing talent who are passionate about what they do. Our employees are unified in a shared dedication to our customers’ mission and quest for professional growth. L3Harris provides an inclusive, engaging environment designed to empower employees and promote work-life success. Fundamental to our culture is an unwavering focus on values, dedication to our communities, and commitment to excellence in everything we do. L3Harris is the Trusted Disruptor in defense tech. With customers’ mission-critical needs always in mind, our employees deliver end-to-end technology solutions connecting the space, air, land, sea and cyber domains in the interest of national security. L3Harris Technologies is an agile global aerospace and defense technology innovator, delivering end-to-end solutions that meet customers’ mission-critical needs. The company provides advanced defense and commercial technologies across space, air, land, sea and cyber domains. L3Harris has approximately $18 billion in annual revenue and 47,000 employees, with customers in more than 100 countries." Job Description: "The Information Security Systems Engineer will be involved in Information Assurance (IA) related architecture development, CONOPS development, trade studies, requirements analysis and flow down to hardware/software configuration items as well as requirements validation and verification. This position requires DoD IA expertise to support embedment of cryptographic components within tactical radio platforms. Candidate will analyze and allocate system security requirements, such as those imposed by NSA, and those under DOD Information Assurance Certification and Accreditation Process (RMF), as well as National Information Assurance Partnership (NIAP) Common Criteria and National Institute of Standards and Technology (NIST) FIPS standards. The Candidate will also oversee and prepare NSA security certification documents, such as System Evaluation Document (SED), Key and Certificate Management Plan (KCMP), Software/Hardware Requirements and Design Specifications (SHRS/SHDD), Security Verification (SV) Test Plans and Reports, Physical Configuration Audit (PCA) Plans and Reports. The candidate should have a good understanding of DoD Configuration Management (CM) processes and management of formal Engineering Change Proposals (ECP). The Candidate will interact with mechanical, electrical and SW engineers to make sure designs meet security requirements." Essential Functions: "Must have experience with security requirements analysis and specification generation. Highly motivated, a self starter, and able to operate with little supervision in diverse environments.Must have a successful track record in planning, executing, and tracking personal task assignments.Experience with emerging security standards and evolution of NSA certification processes.Must have experience with certification of secure architectures.Active Secret U.S. Security Clearance or ability to obtain one.US citizenship is required." Qualifications: "Bachelor’s Degree in Engineering discipline and minimum 4 years of developing embedded software-based engineering solutions. Graduate Degree and a minimum of 2 years of prior related experience. In lieu of a degree, minimum of 8 years of prior related experience." Preferred Additional Skills: "Strong verbal and written communication skills.Radio communications or networking experience preferredKnowledge of configuration management tools" Pay: "In compliance with pay transparency requirements, the salary range for this role in NY is $80,500 - $149,500. This is not a guarantee of compensation or salary, as final offer amount may vary based on factors including but not limited to experience and geographic location." Benefits: "L3Harris also offers a variety of benefits, including health and disability insurance, 401(k) match, flexible spending accounts, EAP, education assistance, parental leave, paid time off, and company-paid holidays. The specific programs and options available to an employee may vary depending on date of hire, schedule type, and the applicability of collective bargaining agreements." Schedule: "Job Schedule: 9/80: Employees work 9 out of every 14 days – totaling 80 hours worked – and have every other Friday off" Location: "Job Location: Rochester, NY" - location is substantive but not a heading per examples. Could be placed in a short paragraph maybe under About the role? Or we could add a
with location. The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata but still substantive; we can include in a short
. We must not include boilerplate: EEO, E-Verify, drug-free workplace, etc. Remove those. Now decide sections. We could have:
About the role
- includes company overview and maybe location? But we also have Responsibilities separate. Better: Use sections: About the role (company overview + location?), Responsibilities (Job Description + Essential Functions?), Requirements (security clearance, citizenship?), Qualifications (education/experience), Skills (preferred additional skills), Benefits, Pay, Schedule. But we need to avoid duplication. Essential Functions includes some requirements like security clearance, citizenship, experience. Those could be under Requirements. Responsibilities could be the job description duties. Let's map: About the role: company overview paragraph(s). Could also include location? Might be okay. Responsibilities: the job description duties (the paragraph about IA related architecture development, etc.) plus maybe the interaction with engineers. Requirements: security clearance, US citizenship, experience with security requirements analysis, etc. Actually Essential Functions list includes many "Must have experience..." which are more like requirements. Could be Requirements. Qualifications: education/experience. Skills: preferred additional skills. Benefits: list. Pay: salary range. Schedule: 9/80. We must ensure we don't create sections with filler. All have real content. Now format: Usefor each heading. Use
for prose. Use
- for lists.
We need to preserve all substantive information. Let's extract each piece precisely.
Company overview: multiple sentences. We'll combine into one or two paragraphs.
Location: "Job Location: Rochester, NY". We'll put in a short
maybe under About the role. Responsibilities: The job description paragraph(s). Let's copy exactly: "The Information Security Systems Engineer will be involved in Information Assurance (IA) related architecture development, CONOPS development, trade studies, requirements analysis and flow down to hardware/software configuration items as well as requirements validation and verification. This position requires DoD IA expertise to support embedment of cryptographic components within tactical radio platforms. Candidate will analyze and allocate system security requirements, such as those imposed by NSA, and those under DOD Information Assurance Certification and Accreditation Process (RMF), as well as National Information Assurance Partnership (NIAP) Common Criteria and National Institute of Standards and Technology (NIST) FIPS standards. The Candidate will also oversee and prepare NSA security certification documents, such as System Evaluation Document (SED), Key and Certificate Management Plan (KCMP), Software/Hardware Requirements and Design Specifications (SHRS/SHDD), Security Verification (SV) Test Plans and Reports, Physical Configuration Audit (PCA) Plans and Reports. The candidate should have a good understanding of DoD Configuration Management (CM) processes and management of formal Engineering Change Proposals (ECP). The Candidate will interact with mechanical, electrical and SW engineers to make sure designs meet security requirements." We could split into two paragraphs for readability but it's fine as one. Requirements: Essential Functions list items: - Must have experience with security requirements analysis and specification generation. - Highly motivated, a self