IT CYBERSECURITY SPECIALIST (NETWORK/INFOSEC)
Defense Information Systems Agency · Columbus, OH · 6 days ago
Information Technology$122k–$158k/yrPart-time
The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules:
1. Use for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless the posting actually states them
9. Prefer a few substantive sections over many thin ones
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
The posting has:
- Summary/About the role information (first paragraph)
- Duties section
- Requirements section with Conditions of employment, Qualifications (Basic Requirements, Qualifying Experience), Education
- Additional information section
- Benefits mention (but generic federal benefits link)
- Pay information (Locality Pay Rates table)
I need to structure this into appropriate sections.
Let me identify the sections:
1. About the role - from the Summary paragraph
2. Responsibilities - from the Duties section
3. Requirements - from the Requirements section (Conditions of employment, Basic Requirements, Qualifying Experience, Education)
4. Pay - from the Locality Pay Rates
5. Additional information - from the Additional information section
6. Benefits - there's a mention of federal benefits but it's generic. The posting says "A career with the U.S. government provides employees with a comprehensive benefits package..." but then says "Contact the hiring agency for more information on the specific benefits offered." This is somewhat generic but does mention benefits. I should include it since it's mentioned.
Wait, the rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state pay rates (Locality Pay Rates) and mentions benefits. So I should include Pay and Benefits sections.
For Schedule - not mentioned, so no Schedule section.
Now let me structure the HTML:
- About the role:
About the role
with for the summary paragraph
- Responsibilities:
Responsibilities
with - for each duty
- Requirements:
Requirements
with subsections? The rules say use for section headings. I could use for Requirements and then use
and
within. But the posting has Conditions of employment, Basic Requirements, Qualifying Experience, Education. I could make those sub-headings but the rules only mention for main sections. I'll keep Requirements as one section with structured content.
Actually, looking at the rules: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So Qualifications is also a possible heading. The posting has "Qualifications" as a subsection under Requirements. I could make Qualifications a separate section.
Let me think: The posting structure:
- Summary
- Duties
- Requirements (with Conditions of employment, Qualifications, Education)
- Additional information
- Benefits mention
- Pay rates
I'll create:
1. About the role
2. Responsibilities
3. Requirements (including Conditions of employment)
4. Qualifications (the Basic Requirements and Qualifying Experience)
5. Education
6. Pay
7. Additional information
8. Benefits
But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications? The posting has "Requirements Help" then "Conditions of employment" then "Qualifications" then "Basic Requirements" then "Qualifying Experience" then "Education".
I think I'll do:
- About the role
- Responsibilities
- Requirements (covering Conditions of employment)
- Qualifications (covering Basic Requirements and Qualifying Experience)
- Education
- Pay
- Additional information
- Benefits
That seems reasonable.
Now let me extract the content:
About the role: The first paragraph: "This position is being recruited under 10 USC 1599f into the Cyber Excepted Service and does NOT convey eligibility to be converted to the Competitive Service. It has been identified as a position necessary to carry out and support the mission of the US Cyber Command. It is in the Professional Work Category at the Senior Work Level within the CES Occupational Structure. It is located in the DISA HC/Operations Support Office."
Responsibilities: From Duties:
- Applies expert technical knowledge and skill to include enterprise and local network architecture, infrastructure, and standards; wide area network and local area network design concepts, principles and processes
- In a team environment, plans and coordinates systems design, acquisition, testing, installation and support.
- Configures front-end processors, hubs, switches, and routers; monitors network performance; analyzes network traffic patterns; and installs network software fixes and upgrades.
- Diagnoses and resolves network problems.
Requirements (Conditions of employment):
- Must be a U.S. Citizen.
- Males born after 12-31-59 must be registered or exempt from Selective Service.
- This national security position, which may require access to classified information, requires a favorable suitability review and security clearance as a condition of employment. Failure to maintain security eligibility may result in termination.
- In accordance with the DoD 8140 policy series, the position is subject to completing Foundational Qualifications in 9 months and completing Residential Qualification requirements overall in 12 months.
- This is a Mission Essential Position
Qualifications (Basic Requirements):
- Applicants must have IT-related experience demonstrating the following competencies appropriate to, or above, the level of this position. For vacancies below the full-performance level of the position, the basic requirement will be evaluated on a developmental basis. Your resume and work experience should clearly support your ability to meet these competencies and will be evaluated as part of the entire application process.
- Attention to Detail - experience reviewing my own information technology-related work or data and have been asked by others to review their work or data to ensure accuracy, completeness, and consistency with standards
- Customer Service - experience maintaining relationships with customers, assessing current information technology needs of customers, and developing or identifying information technology products and services that are tailored to meet customer needs
- Oral Communication - briefing mid-level management and IT staff on the status of information technology systems, projects, or daily operations, including the communication of technical information to a non-technical audience
- Problem Solving - identifying alternatives to address complex information technology-related issues by gathering and applying information from a variety of sources that provide a number of potential solutions
Qualifying Experience:
- In addition to meeting the basic requirement, applicants must possess qualifying experience. To qualify based on your experience, your resume must describe at least one year of experience that demonstrates the competencies necessary for immediate success in the position. Experience refers to any paid or unpaid experience, including volunteer work and Military service, that would be considered equivalent to work normally performed at the next lower grade level in the federal service.
- For This Position, Qualifying Experience Is Defined As Demonstrating technical operational management experience with one or more of Cisco NX, ACI, or SD-WAN, F5, Palo Alto, Juniper, VMWare, Ansible, technologies and services, along with management experience with Azure or AWS services specifically, two or more of cloud networking, connectivity, traffic management, network security, monitoring and management key components.
- Volunteer Experience: Experience refers to paid and unpaid experience, including volunteer work done through National Service programs (e.g., Peace Corps, AmeriCorps) and other organizations (e.g., professional; philanthropic; religious; spiritual, community, student, social). Volunteer work helps build critical competencies, knowledge, and skills and can provide valuable training and experience that translates to paid employment. You will receive credit for all qualifying experience, including volunteer experience.
- Candidates must describe how they meet the qualifying experience and/or selective placement factor(s) within the body of their resume. All qualifications must be met within 30 days after the closing date of the announcement.
- **Combination of education and experience is not applicable for this position.**
Education:
- There is no substitution of education for the qualifying experience at the GG-13 grade level.
Pay: Locality Pay Rates table with locations and ranges.
Additional information: The paragraph starting "This position is in the Excepted Service..." through "For more information regarding qualifications requirements, click here." and "All applicants are encouraged to apply electronically. If you are unable to apply on-line, you may contact 317-212-0454 for assistance. If selected, the authorized rate of pay may exceed the stated maximum salary rate range under certain circumstances. Candidates should be committed to improving the efficiency of the Federal government, passionate about the ideals of our American republic, and committed to upholding the rule of law and the United States Constitution."
Benefits: "A career with the U.S. government provides employees with a comprehensive benefits package. As a federal employee, you and your family will have access to a range of benefits that are designed to make your federal career very rewarding. Opens in a new windowLearn more about federal benefits. Review our benefits Eligibility for benefits depends on the type of position you hold and whether your position is full-time, part-time or intermittent. Contact the hiring agency for more information on the specific benefits offered."
I need to remove boilerplate: "Opens in a new windowLearn more about federal benefits. Review our benefits" seems like navigation/link text. Also "Help" appears multiple times - those are UI elements. Remove "Help" labels.
Also remove "click here" links - they're navigation.
Remove application instructions: "All applicants are encouraged to apply electronically. If you are unable to apply on-line, you may contact 317-212-0454 for assistance."
But the rule says "remove application instructions". So I should remove that sentence.
Also remove "For more information on the Cyber Excepted Service Personnel System, click here. For more information on veterans' preference, click here. For more information regarding qualifications requirements, click here." These are links.
Now, let me write the HTML.
I'll use for each section,
for prose,
- for lists.
For the pay table, I'll use a
with each location as a list item, or maybe a ? The rules say use - for any list. But a table might be better for pay rates. However, the rules specify
- for lists. I'll use a list with each location and range.
Actually, the pay rates are a table in the original. I could represent as a list of locations with ranges. Or use a but the rules don't mention tables. They say "use
- for any list of duties/requirements/benefits". Pay rates could be considered a list. I'll do a list.
Let me structure:
About the role
...
Responsibilities
- ...
...
Requirements
Conditions of employment:
- ...
...
Qualifications
Basic Requirements:
- ...
...
Qualifying Experience:
- ...
...
Education
...
Pay
- Arlington,
for prose 3. Do NOT repeat the job title as a heading 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting has: - Summary/About the role information (first paragraph) - Duties section - Requirements section with Conditions of employment, Qualifications (Basic Requirements, Qualifying Experience), Education - Additional information section - Benefits mention (but generic federal benefits link) - Pay information (Locality Pay Rates table) I need to structure this into appropriate sections. Let me identify the sections: 1. About the role - from the Summary paragraph 2. Responsibilities - from the Duties section 3. Requirements - from the Requirements section (Conditions of employment, Basic Requirements, Qualifying Experience, Education) 4. Pay - from the Locality Pay Rates 5. Additional information - from the Additional information section 6. Benefits - there's a mention of federal benefits but it's generic. The posting says "A career with the U.S. government provides employees with a comprehensive benefits package..." but then says "Contact the hiring agency for more information on the specific benefits offered." This is somewhat generic but does mention benefits. I should include it since it's mentioned. Wait, the rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state pay rates (Locality Pay Rates) and mentions benefits. So I should include Pay and Benefits sections. For Schedule - not mentioned, so no Schedule section. Now let me structure the HTML: - About the role:
About the role
withfor the summary paragraph - Responsibilities:
Responsibilities
with- for each duty
- Requirements:
Requirements
with subsections? The rules say usefor section headings. I could use
for Requirements and then use
and
- within. But the posting has Conditions of employment, Basic Requirements, Qualifying Experience, Education. I could make those sub-headings but the rules only mention
- for lists.
For the pay table, I'll use a
- with each location as a list item, or maybe a ? The rules say use
- for any list. But a table might be better for pay rates. However, the rules specify
- for lists. I'll use a list with each location and range.
Actually, the pay rates are a table in the original. I could represent as a list of locations with ranges. Or use a but the rules don't mention tables. They say "use
- for any list of duties/requirements/benefits". Pay rates could be considered a list. I'll do a list.
Let me structure:
About the role
...
Responsibilities
- ... ...
Requirements
Conditions of employment:
- ... ...
Qualifications
Basic Requirements:
- ... ...
Qualifying Experience:
- ... ...
Education
...
Pay
- Arlington,
- for any list of duties/requirements/benefits". Pay rates could be considered a list. I'll do a list.
Let me structure:
- for lists. I'll use a list with each location and range.
Actually, the pay rates are a table in the original. I could represent as a list of locations with ranges. Or use a but the rules don't mention tables. They say "use
- for any list. But a table might be better for pay rates. However, the rules specify
for main sections. I'll keep Requirements as one section with structured content. Actually, looking at the rules: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So Qualifications is also a possible heading. The posting has "Qualifications" as a subsection under Requirements. I could make Qualifications a separate
section. Let me think: The posting structure: - Summary - Duties - Requirements (with Conditions of employment, Qualifications, Education) - Additional information - Benefits mention - Pay rates I'll create: 1. About the role 2. Responsibilities 3. Requirements (including Conditions of employment) 4. Qualifications (the Basic Requirements and Qualifying Experience) 5. Education 6. Pay 7. Additional information 8. Benefits But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications? The posting has "Requirements Help" then "Conditions of employment" then "Qualifications" then "Basic Requirements" then "Qualifying Experience" then "Education". I think I'll do: - About the role - Responsibilities - Requirements (covering Conditions of employment) - Qualifications (covering Basic Requirements and Qualifying Experience) - Education - Pay - Additional information - Benefits That seems reasonable. Now let me extract the content: About the role: The first paragraph: "This position is being recruited under 10 USC 1599f into the Cyber Excepted Service and does NOT convey eligibility to be converted to the Competitive Service. It has been identified as a position necessary to carry out and support the mission of the US Cyber Command. It is in the Professional Work Category at the Senior Work Level within the CES Occupational Structure. It is located in the DISA HC/Operations Support Office." Responsibilities: From Duties: - Applies expert technical knowledge and skill to include enterprise and local network architecture, infrastructure, and standards; wide area network and local area network design concepts, principles and processes - In a team environment, plans and coordinates systems design, acquisition, testing, installation and support. - Configures front-end processors, hubs, switches, and routers; monitors network performance; analyzes network traffic patterns; and installs network software fixes and upgrades. - Diagnoses and resolves network problems. Requirements (Conditions of employment): - Must be a U.S. Citizen. - Males born after 12-31-59 must be registered or exempt from Selective Service. - This national security position, which may require access to classified information, requires a favorable suitability review and security clearance as a condition of employment. Failure to maintain security eligibility may result in termination. - In accordance with the DoD 8140 policy series, the position is subject to completing Foundational Qualifications in 9 months and completing Residential Qualification requirements overall in 12 months. - This is a Mission Essential Position Qualifications (Basic Requirements): - Applicants must have IT-related experience demonstrating the following competencies appropriate to, or above, the level of this position. For vacancies below the full-performance level of the position, the basic requirement will be evaluated on a developmental basis. Your resume and work experience should clearly support your ability to meet these competencies and will be evaluated as part of the entire application process. - Attention to Detail - experience reviewing my own information technology-related work or data and have been asked by others to review their work or data to ensure accuracy, completeness, and consistency with standards - Customer Service - experience maintaining relationships with customers, assessing current information technology needs of customers, and developing or identifying information technology products and services that are tailored to meet customer needs - Oral Communication - briefing mid-level management and IT staff on the status of information technology systems, projects, or daily operations, including the communication of technical information to a non-technical audience - Problem Solving - identifying alternatives to address complex information technology-related issues by gathering and applying information from a variety of sources that provide a number of potential solutions Qualifying Experience: - In addition to meeting the basic requirement, applicants must possess qualifying experience. To qualify based on your experience, your resume must describe at least one year of experience that demonstrates the competencies necessary for immediate success in the position. Experience refers to any paid or unpaid experience, including volunteer work and Military service, that would be considered equivalent to work normally performed at the next lower grade level in the federal service. - For This Position, Qualifying Experience Is Defined As Demonstrating technical operational management experience with one or more of Cisco NX, ACI, or SD-WAN, F5, Palo Alto, Juniper, VMWare, Ansible, technologies and services, along with management experience with Azure or AWS services specifically, two or more of cloud networking, connectivity, traffic management, network security, monitoring and management key components. - Volunteer Experience: Experience refers to paid and unpaid experience, including volunteer work done through National Service programs (e.g., Peace Corps, AmeriCorps) and other organizations (e.g., professional; philanthropic; religious; spiritual, community, student, social). Volunteer work helps build critical competencies, knowledge, and skills and can provide valuable training and experience that translates to paid employment. You will receive credit for all qualifying experience, including volunteer experience. - Candidates must describe how they meet the qualifying experience and/or selective placement factor(s) within the body of their resume. All qualifications must be met within 30 days after the closing date of the announcement. - **Combination of education and experience is not applicable for this position.** Education: - There is no substitution of education for the qualifying experience at the GG-13 grade level. Pay: Locality Pay Rates table with locations and ranges. Additional information: The paragraph starting "This position is in the Excepted Service..." through "For more information regarding qualifications requirements, click here." and "All applicants are encouraged to apply electronically. If you are unable to apply on-line, you may contact 317-212-0454 for assistance. If selected, the authorized rate of pay may exceed the stated maximum salary rate range under certain circumstances. Candidates should be committed to improving the efficiency of the Federal government, passionate about the ideals of our American republic, and committed to upholding the rule of law and the United States Constitution." Benefits: "A career with the U.S. government provides employees with a comprehensive benefits package. As a federal employee, you and your family will have access to a range of benefits that are designed to make your federal career very rewarding. Opens in a new windowLearn more about federal benefits. Review our benefits Eligibility for benefits depends on the type of position you hold and whether your position is full-time, part-time or intermittent. Contact the hiring agency for more information on the specific benefits offered." I need to remove boilerplate: "Opens in a new windowLearn more about federal benefits. Review our benefits" seems like navigation/link text. Also "Help" appears multiple times - those are UI elements. Remove "Help" labels. Also remove "click here" links - they're navigation. Remove application instructions: "All applicants are encouraged to apply electronically. If you are unable to apply on-line, you may contact 317-212-0454 for assistance." But the rule says "remove application instructions". So I should remove that sentence. Also remove "For more information on the Cyber Excepted Service Personnel System, click here. For more information on veterans' preference, click here. For more information regarding qualifications requirements, click here." These are links. Now, let me write the HTML. I'll use
for each section,
for prose,
- for lists.
For the pay table, I'll use a