Cybersecurity Engineer II w/Secret Clearance
for section headings.
Use - for any list of duties/requirements/benefits.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must strip out the EEO paragraph, drug testing, etc. Also "Additional Job Information" maybe not needed? It includes company description; maybe we can keep as part of About the role? But we don't have About the role section unless we have content. The posting includes "Additional Job Information TekSynap is a fast growing high-tech company..." That's about the company; could be considered About the role? But the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could create an About the role section with that company description. However we must only include a section when the posting has real, specific content for it. The posting does have that description. So we can include About the role.
But we must not repeat job title as heading.
We also need to include maybe "Requirements" but we have qualifications; we could treat qualifications as Requirements. But we already have Qualifications. The instruction list includes both Requirements and Qualifications; we can choose to include Qualifications only if we have content. We have qualifications content. So we can include Qualifications.
We also might include Skills if there is explicit skills list; not really.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule.
We need to format each with heading then content.
For lists: Responsibilities: we have a paragraph describing tasks; maybe we can break into bullet list? The instruction: Use - for any list of duties/requirements/benefits. If the responsibilities are described in prose, we can keep as
. But if we can extract list items, we could make list. Safer to keep as
if not explicitly a list. However the responsibilities paragraph includes multiple sentences; we could keep as
.
Qualifications: includes multiple items: experience, certifications, clearance, etc. Could be list. We'll make
- for each distinct requirement.
Benefits: list of benefits: health, dental, vision, 401K, life insurance, short-term and long-term disability plans, vacation time and holidays. We'll make list.
Pay: salary range: we can put
.
Schedule: description: we can put
.
We must preserve all substantive information; not invent or summarize away detail. So we need to include all details from qualifications: Minimum of seven (7) years of relevant IT experience. Demonstrated experience supporting government agencies, customers, or contracts within federal environments. This includes the Intelligence Community (IC), Department of Defense (DoD), Federal Civil agencies, and military organizations. Prior experience supporting the same or similar contract, with an in-depth understanding of the customer environment, requirements, and operational landscape, is highly desirable. Certifications 8140 Requirements: Dod Cyber Workforce Framework (DCWF) Work Role 521 : Cyber Defense Infrastructure Support Specialist — Intermediate. Candidates must satisfy this requirement through one of the following pathways: BA/BS in Information Technology, Cybersecurity, Computer Science, Information Systems, Data Science, or Software Engineering Or Approved DCWF 521 certifications: (at least one of these certifications) Certified Ethical Hacker (CEH) CompTIA Cloud+ CompTIA Cybersecurity Analyst (CySA+) CompTIA PenTest+ CompTIA Security+ GIAC Continuous Monitoring Certification (GMON) GIAC Response and Industrial Defense (GRID) GIAC Security Essentials Certification (GSEC) Systems Security Certified Practitioner (SSCP). Or Approved DCWF Work role 521 Military Training AND DoD Cyber Workforce Framework (DCWF) Work Role 451: System Administrator - Intermediate. Candidates must satisfy this requirement through one of the following pathways: BA/BS in Information Technology, Cybersecurity, Computer Science, Information Systems, Data Science, or Software Engineering Or Approved DCWF 451 certifications: (at least one of these certifications) CompTIA Cloud+ CompTIA Security+ GIAC Global Industrial Cyber Security Professional (GICSP) GIAC Security Essentials Certification (GSEC) Systems Security Certified Practitioner (SSCP) Or Approved DCWF Work Role 451 Military Training. AND Computing Environment Certification: Microsoft Windows Server Archer Certified Administrator Clearance Secret with IT-II (Tier3). Also WORK AUTHORIZATION/SECURITY CLEARANCE U.S. Citizen Secret – IT-I/T5.
We need to preserve all that.
We should not include boilerplate like "Reasonable accommodation may be made..." etc. Those are under WORK ENVIRONMENT and PHYSICAL DEMANDS; those are not in our headings list, but we could omit them as they are not required sections. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The WORK ENVIRONMENT and PHYSICAL DEMANDS might be considered boilerplate? Not exactly; they are job details. But we don't have a heading for them; we could omit them because we only output sections we have headings for. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't say we must include all content; we must preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we need to include all substantive info, even if not under a heading. But we only allowed headings from the list. However we could embed other info under existing sections (like Responsibilities or Qualifications) if appropriate. For WORK ENVIRONMENT and PHYSICAL DEMANDS, we could maybe put under Responsibilities? Not really. But we could create a section like "Work Environment" but not in allowed headings list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map all content into those sections. WORK ENVIRONMENT and PHYSICAL DEMANDS could be considered part of Responsibilities? Not really. But maybe we can treat them as part of Responsibilities or Qualifications? Might be a stretch. However the instruction says preserve ALL substantive information; we cannot drop them. So we need to include them somewhere. Perhaps we can add a section "Work Environment" even though not in examples? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not an exhaustive list. So we can add other headings as needed, as long as we use . So we could add Work Environment and Physical Demands sections. But the instruction also says "Prefer a few substantive sections over many thin ones." So we might want to avoid too many sections. However we need to preserve all info; we could incorporate WORK ENVIRONMENT and PHYSICAL DEMANDS into Responsibilities or Qualifications as extra paragraphs. That would preserve info without extra sections. That seems acceptable: we can add a paragraph under Responsibilities describing work environment and physical demands. That keeps all info.
Thus we will have sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule.
Under Responsibilities we will include the original responsibilities paragraph plus work environment and physical demands paragraphs.
Now we need to strip out boilerplate: EEO, drug testing, etc. Also "Additional Job Information" we used for About the role. Also "We offer our full-time employees a competitive benefits package..." we used for Benefits.
Also "TekSynap is a drug-free workplace..." etc is boilerplate; remove.
Also "By applying to a role at TekSynap you are providing consent..." etc is application instructions; remove.
Also "EQUAL EMPLOYMENT OPPORTUNITY ..." remove.
Also "Please note this job description is not designed to cover..." maybe we can keep? It's a disclaimer; maybe considered boilerplate? It's not EEO but it's a generic disclaimer. Might be considered boilerplate; safer to remove.
Also "This position supports an upcoming government contract proposal and is contingent upon contract award and government approval." That's substantive? It's about contingency; maybe keep under About the role or Responsibilities? It's about the job. Could be included in About the role.
Also "Candidates must meet all stated requirements and may be required to sign a Letter of Commitment (LOC)." That's a requirement; could be under Qualifications.
Also "Additional Job Information TekSynap is a fast growing high-tech company..." we used.
Also "We offer our full-time employees a competitive benefits package..." used.
Also "TekSynap is a drug-free workplace..." remove.
Also "By applying to a role at TekSynap you are providing consent..." remove.
Also "As part of the application process, you agree that TekSynap Corporation may retain and use your name, e-mail, and contact information for purposes related to employment consideration." remove.
Also "EQUAL EMPLOYMENT OPPORTUNITY ..." remove.
Also "If you believe you need a reasonable accommodation..." remove.
Now we need to format.
Let's craft HTML.
We'll start with About the role
then
containing: TekSynap is a fast growing high-tech company that understands both the pace of technology today and the need to have a comprehensive well planned information management environment. “Technology moving at the speed of thought” embodies these principles – the need to nimbly utilize the best that
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could create an About the role section with that company description. However we must only include a section when the posting has real, specific content for it. The posting does have that description. So we can include About the role.
But we must not repeat job title as heading.
We also need to include maybe "Requirements" but we have qualifications; we could treat qualifications as Requirements. But we already have Qualifications. The instruction list includes both Requirements and Qualifications; we can choose to include Qualifications only if we have content. We have qualifications content. So we can include Qualifications.
We also might include Skills if there is explicit skills list; not really.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule.
We need to format each with heading then content.
For lists: Responsibilities: we have a paragraph describing tasks; maybe we can break into bullet list? The instruction: Use - for any list of duties/requirements/benefits. If the responsibilities are described in prose, we can keep as
. But if we can extract list items, we could make list. Safer to keep as
if not explicitly a list. However the responsibilities paragraph includes multiple sentences; we could keep as
.
Qualifications: includes multiple items: experience, certifications, clearance, etc. Could be list. We'll make
- for each distinct requirement.
Benefits: list of benefits: health, dental, vision, 401K, life insurance, short-term and long-term disability plans, vacation time and holidays. We'll make list.
Pay: salary range: we can put
.
Schedule: description: we can put
.
We must preserve all substantive information; not invent or summarize away detail. So we need to include all details from qualifications: Minimum of seven (7) years of relevant IT experience. Demonstrated experience supporting government agencies, customers, or contracts within federal environments. This includes the Intelligence Community (IC), Department of Defense (DoD), Federal Civil agencies, and military organizations. Prior experience supporting the same or similar contract, with an in-depth understanding of the customer environment, requirements, and operational landscape, is highly desirable. Certifications 8140 Requirements: Dod Cyber Workforce Framework (DCWF) Work Role 521 : Cyber Defense Infrastructure Support Specialist — Intermediate. Candidates must satisfy this requirement through one of the following pathways: BA/BS in Information Technology, Cybersecurity, Computer Science, Information Systems, Data Science, or Software Engineering Or Approved DCWF 521 certifications: (at least one of these certifications) Certified Ethical Hacker (CEH) CompTIA Cloud+ CompTIA Cybersecurity Analyst (CySA+) CompTIA PenTest+ CompTIA Security+ GIAC Continuous Monitoring Certification (GMON) GIAC Response and Industrial Defense (GRID) GIAC Security Essentials Certification (GSEC) Systems Security Certified Practitioner (SSCP). Or Approved DCWF Work role 521 Military Training AND DoD Cyber Workforce Framework (DCWF) Work Role 451: System Administrator - Intermediate. Candidates must satisfy this requirement through one of the following pathways: BA/BS in Information Technology, Cybersecurity, Computer Science, Information Systems, Data Science, or Software Engineering Or Approved DCWF 451 certifications: (at least one of these certifications) CompTIA Cloud+ CompTIA Security+ GIAC Global Industrial Cyber Security Professional (GICSP) GIAC Security Essentials Certification (GSEC) Systems Security Certified Practitioner (SSCP) Or Approved DCWF Work Role 451 Military Training. AND Computing Environment Certification: Microsoft Windows Server Archer Certified Administrator Clearance Secret with IT-II (Tier3). Also WORK AUTHORIZATION/SECURITY CLEARANCE U.S. Citizen Secret – IT-I/T5.
We need to preserve all that.
We should not include boilerplate like "Reasonable accommodation may be made..." etc. Those are under WORK ENVIRONMENT and PHYSICAL DEMANDS; those are not in our headings list, but we could omit them as they are not required sections. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The WORK ENVIRONMENT and PHYSICAL DEMANDS might be considered boilerplate? Not exactly; they are job details. But we don't have a heading for them; we could omit them because we only output sections we have headings for. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't say we must include all content; we must preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we need to include all substantive info, even if not under a heading. But we only allowed headings from the list. However we could embed other info under existing sections (like Responsibilities or Qualifications) if appropriate. For WORK ENVIRONMENT and PHYSICAL DEMANDS, we could maybe put under Responsibilities? Not really. But we could create a section like "Work Environment" but not in allowed headings list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map all content into those sections. WORK ENVIRONMENT and PHYSICAL DEMANDS could be considered part of Responsibilities? Not really. But maybe we can treat them as part of Responsibilities or Qualifications? Might be a stretch. However the instruction says preserve ALL substantive information; we cannot drop them. So we need to include them somewhere. Perhaps we can add a section "Work Environment" even though not in examples? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not an exhaustive list. So we can add other headings as needed, as long as we use . So we could add Work Environment and Physical Demands sections. But the instruction also says "Prefer a few substantive sections over many thin ones." So we might want to avoid too many sections. However we need to preserve all info; we could incorporate WORK ENVIRONMENT and PHYSICAL DEMANDS into Responsibilities or Qualifications as extra paragraphs. That would preserve info without extra sections. That seems acceptable: we can add a paragraph under Responsibilities describing work environment and physical demands. That keeps all info.
Thus we will have sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule.
Under Responsibilities we will include the original responsibilities paragraph plus work environment and physical demands paragraphs.
Now we need to strip out boilerplate: EEO, drug testing, etc. Also "Additional Job Information" we used for About the role. Also "We offer our full-time employees a competitive benefits package..." we used for Benefits.
Also "TekSynap is a drug-free workplace..." etc is boilerplate; remove.
Also "By applying to a role at TekSynap you are providing consent..." etc is application instructions; remove.
Also "EQUAL EMPLOYMENT OPPORTUNITY ..." remove.
Also "Please note this job description is not designed to cover..." maybe we can keep? It's a disclaimer; maybe considered boilerplate? It's not EEO but it's a generic disclaimer. Might be considered boilerplate; safer to remove.
Also "This position supports an upcoming government contract proposal and is contingent upon contract award and government approval." That's substantive? It's about contingency; maybe keep under About the role or Responsibilities? It's about the job. Could be included in About the role.
Also "Candidates must meet all stated requirements and may be required to sign a Letter of Commitment (LOC)." That's a requirement; could be under Qualifications.
Also "Additional Job Information TekSynap is a fast growing high-tech company..." we used.
Also "We offer our full-time employees a competitive benefits package..." used.
Also "TekSynap is a drug-free workplace..." remove.
Also "By applying to a role at TekSynap you are providing consent..." remove.
Also "As part of the application process, you agree that TekSynap Corporation may retain and use your name, e-mail, and contact information for purposes related to employment consideration." remove.
Also "EQUAL EMPLOYMENT OPPORTUNITY ..." remove.
Also "If you believe you need a reasonable accommodation..." remove.
Now we need to format.
Let's craft HTML.
We'll start with About the role
then
containing: TekSynap is a fast growing high-tech company that understands both the pace of technology today and the need to have a comprehensive well planned information management environment. “Technology moving at the speed of thought” embodies these principles – the need to nimbly utilize the best that
- for any list of duties/requirements/benefits. If the responsibilities are described in prose, we can keep as
. But if we can extract list items, we could make list. Safer to keep as
if not explicitly a list. However the responsibilities paragraph includes multiple sentences; we could keep as
. Qualifications: includes multiple items: experience, certifications, clearance, etc. Could be list. We'll make
- for each distinct requirement.
Benefits: list of benefits: health, dental, vision, 401K, life insurance, short-term and long-term disability plans, vacation time and holidays. We'll make list.
Pay: salary range: we can put
. Schedule: description: we can put
. We must preserve all substantive information; not invent or summarize away detail. So we need to include all details from qualifications: Minimum of seven (7) years of relevant IT experience. Demonstrated experience supporting government agencies, customers, or contracts within federal environments. This includes the Intelligence Community (IC), Department of Defense (DoD), Federal Civil agencies, and military organizations. Prior experience supporting the same or similar contract, with an in-depth understanding of the customer environment, requirements, and operational landscape, is highly desirable. Certifications 8140 Requirements: Dod Cyber Workforce Framework (DCWF) Work Role 521 : Cyber Defense Infrastructure Support Specialist — Intermediate. Candidates must satisfy this requirement through one of the following pathways: BA/BS in Information Technology, Cybersecurity, Computer Science, Information Systems, Data Science, or Software Engineering Or Approved DCWF 521 certifications: (at least one of these certifications) Certified Ethical Hacker (CEH) CompTIA Cloud+ CompTIA Cybersecurity Analyst (CySA+) CompTIA PenTest+ CompTIA Security+ GIAC Continuous Monitoring Certification (GMON) GIAC Response and Industrial Defense (GRID) GIAC Security Essentials Certification (GSEC) Systems Security Certified Practitioner (SSCP). Or Approved DCWF Work role 521 Military Training AND DoD Cyber Workforce Framework (DCWF) Work Role 451: System Administrator - Intermediate. Candidates must satisfy this requirement through one of the following pathways: BA/BS in Information Technology, Cybersecurity, Computer Science, Information Systems, Data Science, or Software Engineering Or Approved DCWF 451 certifications: (at least one of these certifications) CompTIA Cloud+ CompTIA Security+ GIAC Global Industrial Cyber Security Professional (GICSP) GIAC Security Essentials Certification (GSEC) Systems Security Certified Practitioner (SSCP) Or Approved DCWF Work Role 451 Military Training. AND Computing Environment Certification: Microsoft Windows Server Archer Certified Administrator Clearance Secret with IT-II (Tier3). Also WORK AUTHORIZATION/SECURITY CLEARANCE U.S. Citizen Secret – IT-I/T5. We need to preserve all that. We should not include boilerplate like "Reasonable accommodation may be made..." etc. Those are under WORK ENVIRONMENT and PHYSICAL DEMANDS; those are not in our headings list, but we could omit them as they are not required sections. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The WORK ENVIRONMENT and PHYSICAL DEMANDS might be considered boilerplate? Not exactly; they are job details. But we don't have a heading for them; we could omit them because we only output sections we have headings for. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't say we must include all content; we must preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we need to include all substantive info, even if not under a heading. But we only allowed headings from the list. However we could embed other info under existing sections (like Responsibilities or Qualifications) if appropriate. For WORK ENVIRONMENT and PHYSICAL DEMANDS, we could maybe put under Responsibilities? Not really. But we could create a section like "Work Environment" but not in allowed headings list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map all content into those sections. WORK ENVIRONMENT and PHYSICAL DEMANDS could be considered part of Responsibilities? Not really. But maybe we can treat them as part of Responsibilities or Qualifications? Might be a stretch. However the instruction says preserve ALL substantive information; we cannot drop them. So we need to include them somewhere. Perhaps we can add a section "Work Environment" even though not in examples? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not an exhaustive list. So we can add other headings as needed, as long as we use
. So we could add Work Environment and Physical Demands sections. But the instruction also says "Prefer a few substantive sections over many thin ones." So we might want to avoid too many sections. However we need to preserve all info; we could incorporate WORK ENVIRONMENT and PHYSICAL DEMANDS into Responsibilities or Qualifications as extra paragraphs. That would preserve info without extra sections. That seems acceptable: we can add a paragraph under Responsibilities describing work environment and physical demands. That keeps all info. Thus we will have sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. Under Responsibilities we will include the original responsibilities paragraph plus work environment and physical demands paragraphs. Now we need to strip out boilerplate: EEO, drug testing, etc. Also "Additional Job Information" we used for About the role. Also "We offer our full-time employees a competitive benefits package..." we used for Benefits. Also "TekSynap is a drug-free workplace..." etc is boilerplate; remove. Also "By applying to a role at TekSynap you are providing consent..." etc is application instructions; remove. Also "EQUAL EMPLOYMENT OPPORTUNITY ..." remove. Also "Please note this job description is not designed to cover..." maybe we can keep? It's a disclaimer; maybe considered boilerplate? It's not EEO but it's a generic disclaimer. Might be considered boilerplate; safer to remove. Also "This position supports an upcoming government contract proposal and is contingent upon contract award and government approval." That's substantive? It's about contingency; maybe keep under About the role or Responsibilities? It's about the job. Could be included in About the role. Also "Candidates must meet all stated requirements and may be required to sign a Letter of Commitment (LOC)." That's a requirement; could be under Qualifications. Also "Additional Job Information TekSynap is a fast growing high-tech company..." we used. Also "We offer our full-time employees a competitive benefits package..." used. Also "TekSynap is a drug-free workplace..." remove. Also "By applying to a role at TekSynap you are providing consent..." remove. Also "As part of the application process, you agree that TekSynap Corporation may retain and use your name, e-mail, and contact information for purposes related to employment consideration." remove. Also "EQUAL EMPLOYMENT OPPORTUNITY ..." remove. Also "If you believe you need a reasonable accommodation..." remove. Now we need to format. Let's craft HTML. We'll start with
About the role
thencontaining: TekSynap is a fast growing high-tech company that understands both the pace of technology today and the need to have a comprehensive well planned information management environment. “Technology moving at the speed of thought” embodies these principles – the need to nimbly utilize the best that
- for each distinct requirement.
Benefits: list of benefits: health, dental, vision, 401K, life insurance, short-term and long-term disability plans, vacation time and holidays. We'll make list.
Pay: salary range: we can put