Field Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include About the role section with the role description. The "About Leidos" maybe not needed; but could be considered part of About the role? Probably not; better to omit as it's generic company info not specific to role. Also remove "Securing Your Data", "Commitment to Non-Discrimination", etc. Also remove "Original Posting August 26, 2026", etc. Also remove "Step 10 is ancient history..." marketing fluff? Might be considered boilerplate? It's not required but could be considered part of About the role? It's marketing fluff; maybe we should keep if it's substantive? It's not specific to role; it's generic. Better to drop.
We need to preserve all substantive information: location, clearance, travel requirement, role description, responsibilities list, qualifications, certifications, skills list, pay range, benefits description.
We must not repeat job title. Must not include Job ID/requisition numbers.
We must not create sections with filler like "commensurate with experience". We have actual content.
We need to use - for any list of duties/requirements/benefits. For prose use
.
We need to decide which sections to include:
- About the role: include paragraph(s) describing role: location, clearance, travel, purpose, etc.
- Responsibilities: list of primary responsibilities.
- Requirements: maybe include clearance, travel ability, degree/experience? Could be part of Qualifications. The instruction lists Requirements as a possible heading. We have "Required Qualifications". Could treat as Requirements. But also have "Additional Qualifications/Certifications". Could combine under Qualifications. To avoid thin sections, we can have Qualifications section covering both required and additional. Or we could have Requirements (clearance, travel, degree/experience) and Qualifications (skills, certifications). But we need to avoid too many thin sections. Let's see content:
Required Qualifications:
- Bachelor’s degree and 8-12 years prior relevant field engineering experience or master’s degree with 6-10 years.
- Additional years of relevant experience considered in lieu of degree.
- Active and current TS/SCI clearance.
- Must be able to travel to onsite installations.
- Demonstrated experience with AWS, Networking, VPNs, IaaS, PaaS, SQL, Jenkins, Terraform, Ansible, Jira, Confluence, Artifactory, and Guacamole (admin/troubleshoot).
- Knowledge of and experience working with DevSecOps tool chains.
- Experience in preparing technical documentation.
- Experience working in a team environment with ability to mentor junior team members.
- Ability to configure and troubleshoot cloud, virtual, and physical hardware and software systems.
- Ability to proactively identify and resolve operational, tooling and process inefficiencies.
- One of the positions should have strong Jira/Confluence and agile team participation experience (ideally scrum master training).
- Required Certification: DOD 8140 IAT II (Intermediate); GIAC Security Essentials Certification; GICSP: Global Industrial Cyber Security Professional; SSCP: Systems Security Certified Practitioner.
Additional Qualifications/Certifications:
- Proven experience with military use of commercial/hybrid cloud deployments in operational use.
- DABAOPP1 (maybe a code).
Skills: The list of technologies could be considered Skills. But they are also in Required Qualifications. Could separate.
We could have:
- About the role (paragraph)
- Responsibilities (ul)
- Qualifications (ul) covering education/experience, clearance, travel, experience with tools, DevSecOps, documentation, teamwork, troubleshooting, Jira/Confluence, certifications.
- Skills (ul) maybe list of specific tools: AWS, Networking, VPNs, IaaS, PaaS, SQL, Jenkins, Terraform, Ansible, Jira, Confluence, Artifactory, Guacamole, DevSecOps tool chains.
- Benefits (ul) maybe list: competitive compensation, Health and Wellness programs, Income Protection, Paid Leave, Retirement.
- Pay (p) with range.
We must not include Schedule.
We must not include boilerplate like "About Leidos", "Pay And Benefits" heading? We'll create our own Benefits and Pay sections.
We need to ensure we don't duplicate content. We'll extract.
Let's craft:
About the role
Location: CONUS and OCONUS. Clearance: TS/SCI. Travel Requirement: 75% of the time. The Decision Advantage Business Area within Defense at Leidos has an opening for a highly qualified TS/SCI cleared Field Engineer. This role supports all-domain large-scale weapon systems, Information Technology Systems, and Command and Control Systems to realize the Department of Defense Joint All-Domain Command and Control (JADC2). You will work with the Advanced Battle Management System (ABMS) Digital Infrastructure (DI) Processing Node (PN) team to design and implement solutions delivered at speed, scale, and with necessary security to provide operational advantages to the joint warfighter. The position works closely with Program Managers, domain engineers, and Government counterparts across Government and Industry partners.
That captures location, clearance, travel, role description.
Now Responsibilities:
We have list from "Primary Responsibilities". Let's extract each bullet:
- Remain available to travel (sometimes on short notice) both within CONUS and OCONUS
- Conduct site surveys, site installations and configurations, and site acceptance procedures to field products
- Interact with and maintain channels of communication with site POCs to support and assist with fielded equipment
- Maintain knowledge, skills, and abilities to deploy products and/or special program requests (varies) – note "varies" maybe placeholder; but it's part of text. It says "(varies)" which is placeholder; we should avoid including placeholder? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. For list items, if they contain "(varies)" maybe it's placeholder; but it's part of the sentence. Might be considered filler. Better to keep the sentence but maybe remove the "(varies)"? The instruction says do not invent or summarize away detail. Removing "(varies)" is summarizing? It's just removing placeholder; maybe acceptable. But safer to keep as is? It says never emit a heading followed by filler/placeholder text. It's about headings, not list items. So we can keep the item as is.
- Prepare items required (historical logs, documents, checklists, configurations, login, passwords, presentations) for any assigned engagement
- Document and upload all notes, feedback, requests, suggestions, and errors for all engagements, to include leading up to, during, and after the engagements
- Create out-brief/trip report capturing POCs, completed items, open items, and follow-up actions, and brief report to stakeholders
- While not on-site, remain available to answer questions or provide insight, support, and/or updates as required
- Review assigned Jira tasks, add comments to provide updates, and move tasks to appropriate category daily
- Participate in assigned Scrum meetings and conduct Jira task reviews as scheduled/required
- Collaborate with other program members when the need arises to support tasks/work related to other projects
We'll put each as - .
Now Qualifications: combine required and additional.
We need to list:
- Bachelor’s degree and 8-12 years of prior relevant field engineering experience or master’s degree with 6-10 years of prior relevant experience. Additional years of relevant experience will be considered in lieu of degree.
- Active and current TS/SCI clearance.
- Must be able to travel to onsite installations.
- Demonstrated experience with AWS, Networking, VPNs, IaaS, PaaS, SQL, Jenkins, Terraform, Ansible, Jira, Confluence, Artifactory, and Guacamole (from an administration and troubleshooting perspective).
- Knowledge of and experience working with DevSecOps tool chains.
- Experience in preparing technical documentation.
- Experience working in a team environment with the ability to mentor junior team members.
- Ability to configure and troubleshoot cloud, virtual, and physical hardware and software systems.
- Ability to proactively identify and resolve operational, tooling and process inefficiencies.
- One of the positions should have strong Jira/Confluence and agile team participation experience (ideally scrum master training).
- Required Certification: DOD 8140 IAT II (Intermediate); GIAC Security Essentials Certification; GICSP: Global Industrial Cyber Security Professional; SSCP: Systems Security Certified Practitioner.
- Additional Qualifications/Certifications: Proven experience with military use of commercial/hybrid cloud deployments in operational use. DABAOPP1.
We could split into two lists: Qualifications and Skills. But we already have Skills list of tools. To avoid duplication, maybe put tools under Skills, and keep Qualifications for education/experience, clearance, travel, certifications, DevSecOps, documentation, teamwork, troubleshooting, Jira/Confluence, agile, etc.
Let's decide:
Section Qualifications (education/experience, clearance, travel, certifications, etc.)
Section Skills (specific technologies, DevSecOps, etc.)
But we must not create thin sections. However both will have substantive content.
Let's do:
Qualifications
- Bachelor’s degree and 8-12 years of prior relevant field engineering experience or master’s degree with 6-10 years of prior relevant experience. Additional years of relevant experience will be considered in lieu of degree.
- Active and current TS/SCI clearance.
- Must be able to travel to onsite installations.
- Required Certification: DOD 8140 IAT II (Intermediate); GIAC Security Essentials Certification; GICSP: Global Industrial Cyber Security Professional; SSCP:
. We need to decide which sections to include: - About the role: include paragraph(s) describing role: location, clearance, travel, purpose, etc. - Responsibilities: list of primary responsibilities. - Requirements: maybe include clearance, travel ability, degree/experience? Could be part of Qualifications. The instruction lists Requirements as a possible heading. We have "Required Qualifications". Could treat as Requirements. But also have "Additional Qualifications/Certifications". Could combine under Qualifications. To avoid thin sections, we can have Qualifications section covering both required and additional. Or we could have Requirements (clearance, travel, degree/experience) and Qualifications (skills, certifications). But we need to avoid too many thin sections. Let's see content: Required Qualifications: - Bachelor’s degree and 8-12 years prior relevant field engineering experience or master’s degree with 6-10 years. - Additional years of relevant experience considered in lieu of degree. - Active and current TS/SCI clearance. - Must be able to travel to onsite installations. - Demonstrated experience with AWS, Networking, VPNs, IaaS, PaaS, SQL, Jenkins, Terraform, Ansible, Jira, Confluence, Artifactory, and Guacamole (admin/troubleshoot). - Knowledge of and experience working with DevSecOps tool chains. - Experience in preparing technical documentation. - Experience working in a team environment with ability to mentor junior team members. - Ability to configure and troubleshoot cloud, virtual, and physical hardware and software systems. - Ability to proactively identify and resolve operational, tooling and process inefficiencies. - One of the positions should have strong Jira/Confluence and agile team participation experience (ideally scrum master training). - Required Certification: DOD 8140 IAT II (Intermediate); GIAC Security Essentials Certification; GICSP: Global Industrial Cyber Security Professional; SSCP: Systems Security Certified Practitioner. Additional Qualifications/Certifications: - Proven experience with military use of commercial/hybrid cloud deployments in operational use. - DABAOPP1 (maybe a code). Skills: The list of technologies could be considered Skills. But they are also in Required Qualifications. Could separate. We could have: - About the role (paragraph) - Responsibilities (ul) - Qualifications (ul) covering education/experience, clearance, travel, experience with tools, DevSecOps, documentation, teamwork, troubleshooting, Jira/Confluence, certifications. - Skills (ul) maybe list of specific tools: AWS, Networking, VPNs, IaaS, PaaS, SQL, Jenkins, Terraform, Ansible, Jira, Confluence, Artifactory, Guacamole, DevSecOps tool chains. - Benefits (ul) maybe list: competitive compensation, Health and Wellness programs, Income Protection, Paid Leave, Retirement. - Pay (p) with range. We must not include Schedule. We must not include boilerplate like "About Leidos", "Pay And Benefits" heading? We'll create our own Benefits and Pay sections. We need to ensure we don't duplicate content. We'll extract. Let's craft:
About the role
Location: CONUS and OCONUS. Clearance: TS/SCI. Travel Requirement: 75% of the time. The Decision Advantage Business Area within Defense at Leidos has an opening for a highly qualified TS/SCI cleared Field Engineer. This role supports all-domain large-scale weapon systems, Information Technology Systems, and Command and Control Systems to realize the Department of Defense Joint All-Domain Command and Control (JADC2). You will work with the Advanced Battle Management System (ABMS) Digital Infrastructure (DI) Processing Node (PN) team to design and implement solutions delivered at speed, scale, and with necessary security to provide operational advantages to the joint warfighter. The position works closely with Program Managers, domain engineers, and Government counterparts across Government and Industry partners.
That captures location, clearance, travel, role description. Now Responsibilities: We have list from "Primary Responsibilities". Let's extract each bullet: - Remain available to travel (sometimes on short notice) both within CONUS and OCONUS - Conduct site surveys, site installations and configurations, and site acceptance procedures to field products - Interact with and maintain channels of communication with site POCs to support and assist with fielded equipment - Maintain knowledge, skills, and abilities to deploy products and/or special program requests (varies) – note "varies" maybe placeholder; but it's part of text. It says "(varies)" which is placeholder; we should avoid including placeholder? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. For list items, if they contain "(varies)" maybe it's placeholder; but it's part of the sentence. Might be considered filler. Better to keep the sentence but maybe remove the "(varies)"? The instruction says do not invent or summarize away detail. Removing "(varies)" is summarizing? It's just removing placeholder; maybe acceptable. But safer to keep as is? It says never emit a heading followed by filler/placeholder text. It's about headings, not list items. So we can keep the item as is. - Prepare items required (historical logs, documents, checklists, configurations, login, passwords, presentations) for any assigned engagement - Document and upload all notes, feedback, requests, suggestions, and errors for all engagements, to include leading up to, during, and after the engagements - Create out-brief/trip report capturing POCs, completed items, open items, and follow-up actions, and brief report to stakeholders - While not on-site, remain available to answer questions or provide insight, support, and/or updates as required - Review assigned Jira tasks, add comments to provide updates, and move tasks to appropriate category daily - Participate in assigned Scrum meetings and conduct Jira task reviews as scheduled/required - Collaborate with other program members when the need arises to support tasks/work related to other projects We'll put each asQualifications
- Bachelor’s degree and 8-12 years of prior relevant field engineering experience or master’s degree with 6-10 years of prior relevant experience. Additional years of relevant experience will be considered in lieu of degree.
- Active and current TS/SCI clearance.
- Must be able to travel to onsite installations.
- Required Certification: DOD 8140 IAT II (Intermediate); GIAC Security Essentials Certification; GICSP: Global Industrial Cyber Security Professional; SSCP: