LCAT 4-Deployable Communications and Information Systems Future Technologies SME
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, EEO, legal, application instructions, duplicated lines. Preserve all substantive info.
We need to extract sections:
From posting:
- Role Overview: "We are seeking a Deployable Communications and Information Systems (DCIS) Future Technologies Subject Matter Expert. This role involves providing technical advice, conducting technology assessments, and developing recommendations for capability modernization initiatives. The position supports strategic planning and the integration of future technologies into existing DCIS architectures."
That's about the role. So heading: About the role (or Role Overview). Use About the role
then
...
. - Key Responsibilities: list bullet points. We need to use- for any list of duties/requirements/benefits.
Responsibilities list:
- Advise the DCIS Programme Director on future technologies and conduct assessments of current NATO DCIS.
- Develop technical recommendations for capability modernization and participate in architecture reviews.
- Support strategic planning for DCIS capability development and evaluate commercial and government technologies.
- Produce technical evaluation reports, conduct briefings, and assess the integration of new technologies.
- Evaluate interoperability with legacy systems, Next Generation DCIS, and NATO Federated Mission Networking (FMN).
- Support operational testing, review post-exercise findings, and conduct technical risk assessments.
- Provide technical support to workshops and meetings, potentially requiring travel up to 30 days per year.
- Implement best practices to enhance knowledge and information management within the C3 Enterprise.
That's responsibilities.
- Required Qualifications: includes Education and Experience.
We can have a Requirements section? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content.
We have Education and Experience under Required Qualifications. Could split into Qualifications (education) and Requirements (experience) or combine. Probably better: Qualifications heading for education, Requirements heading for experience. But we need to avoid thin sections; we can combine into one Qualifications section that includes both education and experience. However the instruction says prefer a few substantive sections over many thin ones. So we could have a single "Qualifications" section covering education and experience. Or we could have "Requirements" for experience and "Qualifications" for education. Both are substantive enough.
Let's see: Education: A university degree ... Substantial experience with MSP, PRINCE2, or PMI certification will be considered in lieu of a degree.
Experience: multiple bullet points each with minimum 3 years.
Technical Skills: also listed.
Thus we have:
- Qualifications (education)
- Requirements (experience)
- Skills (technical skills)
We also have Benefits section: details about benefits.
Pay: not mentioned. Schedule: not mentioned (though travel up to 30 days per year mentioned under responsibilities, but not schedule). So we should not create Pay or Schedule sections because no specific content.
Thus sections: About the role, Responsibilities, Qualifications, Requirements, Skills, Benefits.
Now we need to extract benefits text:
"Everforth Apex Benefits Overview: Everforth Apex offers a range of supplemental benefits, including medical, dental, vision, life, disability, and other insurance plans that offer an optional layer of financial protection. We offer an ESPP (employee stock purchase program) and a 401K program which allows you to contribute typically within 30 days of starting, with a company match after 12 months of tenure. Everforth Apex also offers a HSA (Health Savings Account on the HDHP plan), a SupportLinc Employee Assistance Program (EAP) with up to 8 free counseling sessions, a corporate discount savings program and other discounts. In terms of professional development, Everforth Apex hosts an on-demand training program, provides access to certification prep and a library of technical and leadership courses/books/seminars once you have 6+ months of tenure, and certification discounts and other perks to associations that include CompTIA and IIBA. Everforth Apex has a dedicated customer service team for our Consultants that can address questions around benefits and other resources, as well as a certified Career Coach. You can access a full list of our benefits, programs, support teams and resources within our ‘Welcome Packet’ as well, which an Everforth Apex team member can provide."
We need to put that as a Benefits section with
- for list items? The benefits are described in prose; we could keep as
but the rule says use
- for any list of duties/requirements/benefits. Benefits is a list of items; we could break into list items. However the instruction: "Use
- for any list of duties/requirements/benefits, and
for prose." So if we have a list of benefits, we should use
- . We can parse the benefits into items: medical, dental, vision, life, disability, other insurance; ESPP; 401K with match after 12 months; HSA; SupportLinc EAP up to 8 free counseling; corporate discount savings program and other discounts; on-demand training program; access to certification prep and library after 6+ months; certification discounts and perks to CompTIA and IIBA; dedicated customer service team; certified Career Coach; Welcome Packet full list.
We could keep as prose but better to follow rule: use list for benefits. We'll create
- with each benefit as
- . Ensure we preserve all substantive info.
Now Responsibilities list we already have as
- .
Requirements (experience) list: multiple bullet points each with "A minimum of 3 years ..." plus "Demonstrated experience in a deployable CIS or Signals capacity in a subject matter expert role." We'll make list.
Qualifications (education) list: maybe just one item: "A university degree in computer science, information technology, computer engineering, electrical engineering, telecommunications, or a related discipline is required. Substantial experience with MSP, PRINCE2, or PMI certification will be considered in lieu of a degree." Could be two items.
Skills list: technical skills bullet points.
Now we need to ensure we don't include boilerplate like EEO, legal, application instructions, duplicated lines, cookie/navigation etc. Also remove "Job#: 3051933", "Location: Norfolk, Virginia (Onsite)", "Clearance : Customer requires all consultants to hold a minimum of an Active Secret". Actually clearance is substantive? It says "Customer requires all consultants to hold a minimum of an Active Secret". That is a requirement (clearance). Should we include? The instruction: "Preserve ALL substantive information". Clearance is substantive. Should we include it under Requirements or Qualifications? Probably under Requirements as a requirement. It mentions "Clearance : Customer requires all consultants to hold a minimum of an Active Secret". Also earlier: "Candidates must be U.S. citizens able to obtain and/or maintain a Department of Defense security clearance as a condition and continuation of employment." That's also substantive. So we need to include citizenship and clearance requirement.
Thus we need to add a requirement: U.S. citizenship and ability to obtain/maintain DoD security clearance; Active Secret clearance minimum.
We can add to Requirements list.
Now also location: Norfolk, Virginia (Onsite) - location is substantive but not a heading; we could include in About the role paragraph maybe. The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Location could be minor metadata; we could include in About the role paragraph as a sentence. But we already have About the role paragraph; we could add location there. However we must not repeat job title as heading. It's fine. We should also include the role overview sentence about "Deployable Communications and Information Systems Future Technologies SME". Already in About the role. Now we need to remove duplicated lines: there are duplicate EEO statements etc. We'll omit. Now produce HTML fragment:
About the role
We are seeking a Deployable Communications and Information Systems (DCIS) Future Technologies Subject Matter Expert. This role involves providing technical advice, conducting technology assessments, and developing recommendations for capability modernization initiatives. The position supports strategic planning and the integration of future technologies into existing DCIS architectures. Location: Norfolk, Virginia (Onsite).
Responsibilities
- Advise the DCIS Programme Director on future technologies and conduct assessments of current NATO DCIS.
- Develop technical recommendations for capability modernization and participate in architecture reviews.
- Support strategic planning for DCIS capability development and evaluate commercial and government technologies.
- Produce technical evaluation reports, conduct briefings, and assess the integration of new technologies.
- Evaluate interoperability with legacy systems, Next Generation DCIS, and NATO Federated Mission Networking (FMN).
- Support operational testing, review post-exercise findings, and conduct technical risk assessments.
- Provide technical support to workshops and meetings, potentially requiring travel up to 30 days per year.
- Implement best practices to enhance knowledge and information management within the C3 Enterprise.
Qualifications
- A university degree in computer science, information technology, computer engineering, electrical engineering, telecommunications, or a related discipline is required.
- Substantial experience with MSP, PRINCE2, or PMI certification will be considered in lieu of a degree.
Requirements
- U.S. citizenship and ability to obtain and/or maintain a Department of Defense security clearance as a condition of employment.
- Minimum of an Active Secret security clearance.
- A minimum of 3 years supporting enterprise or tactical Communications and Information Systems (CIS).
- A minimum of 3 years supporting capability development of CIS or related systems.
- A minimum of 3 years integrating emerging technologies.
- A minimum of 3 years of demonstrated expertise in performing technical analysis, documenting findings, and conducting technical briefings.
- A minimum of 3 years working in a NATO or multi-national military environment.
- Demonstrated experience in a deployable CIS or Signals capacity in a subject matter expert role.
Skills
- A minimum of 3 years of demonstrated expertise with one or more of the following: cloud computing, network automation, enterprise networking, tactical networking, routing and switching, or virtualization.
- Demonstrated experience supporting one or more of the following: satellite communications, cybersecurity, zero trust, or AI-enabled network management.
Benefits
- Medical, dental, vision, life, disability, and other insurance plans (optional layer of financial protection).
- Employee Stock Purchase Program (ESPP).
- 401K program with company match after 12 months of tenure (contributions typically allowed within 30 days of starting).
- Health Savings Account (HSA) on the HDHP plan.
- SupportLinc Employee Assistance Program (EAP) with up to 8 free counseling sessions.
- Corporate discount savings program and other discounts.
- On-demand training program.
- Access to certification prep and a library of technical and leadership courses/books/seminars after 6+ months of tenure.
- Certification discounts and other perks to associations including CompTIA and IIBA.
- Dedicated customer service team for consultants to address benefits and other resources.
- Certified Career Coach.
- Full list of benefits, programs,
- .
Requirements (experience) list: multiple bullet points each with "A minimum of 3 years ..." plus "Demonstrated experience in a deployable CIS or Signals capacity in a subject matter expert role." We'll make list.
Qualifications (education) list: maybe just one item: "A university degree in computer science, information technology, computer engineering, electrical engineering, telecommunications, or a related discipline is required. Substantial experience with MSP, PRINCE2, or PMI certification will be considered in lieu of a degree." Could be two items.
Skills list: technical skills bullet points.
Now we need to ensure we don't include boilerplate like EEO, legal, application instructions, duplicated lines, cookie/navigation etc. Also remove "Job#: 3051933", "Location: Norfolk, Virginia (Onsite)", "Clearance : Customer requires all consultants to hold a minimum of an Active Secret". Actually clearance is substantive? It says "Customer requires all consultants to hold a minimum of an Active Secret". That is a requirement (clearance). Should we include? The instruction: "Preserve ALL substantive information". Clearance is substantive. Should we include it under Requirements or Qualifications? Probably under Requirements as a requirement. It mentions "Clearance : Customer requires all consultants to hold a minimum of an Active Secret". Also earlier: "Candidates must be U.S. citizens able to obtain and/or maintain a Department of Defense security clearance as a condition and continuation of employment." That's also substantive. So we need to include citizenship and clearance requirement.
Thus we need to add a requirement: U.S. citizenship and ability to obtain/maintain DoD security clearance; Active Secret clearance minimum.
We can add to Requirements list.
Now also location: Norfolk, Virginia (Onsite) - location is substantive but not a heading; we could include in About the role paragraph maybe. The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short
- . Ensure we preserve all substantive info.
Now Responsibilities list we already have as
- . We can parse the benefits into items: medical, dental, vision, life, disability, other insurance; ESPP; 401K with match after 12 months; HSA; SupportLinc EAP up to 8 free counseling; corporate discount savings program and other discounts; on-demand training program; access to certification prep and library after 6+ months; certification discounts and perks to CompTIA and IIBA; dedicated customer service team; certified Career Coach; Welcome Packet full list.
We could keep as prose but better to follow rule: use list for benefits. We'll create
- for any list of duties/requirements/benefits, and
- for any list of duties/requirements/benefits. Benefits is a list of items; we could break into list items. However the instruction: "Use
- for list items? The benefits are described in prose; we could keep as