Supv IT Cybersecurity Specialist (SYSADMIN/INFOSEC)
Defense Information Systems Agency · Columbus, OH · 1 mo ago
Information TechnologyPart-time
We need to output HTML fragment with sections only if real content. Let's parse the posting.
We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections have content.
From posting:
- Summary: description about position being recruited under 10 USC 1599f, Cyber Excepted Service, mission of US Cyber Command, supervision/management work category senior work level, located in DISA (HC3A24). That's about the role. So we can have
About the role
with paragraph(s) summarizing. - Duties: "Help Responsible for the overall management of functions and staff required to support the installation, configuration, troubleshooting and maintenance of hardware and software to ensure the availability and functionality of information systems.Manages and directs accomplishment of highly critical mission and functions of the organization supported.Continually keeps abreast of *state-of-the-art* advanced technology. Studies appropriate journals, participates in computer users technical seminars, maintains contacts with vendor personnel, and takes other actions as appropriate to maintain." That's duties. SoResponsibilities
with- items.
- Requirements: includes Conditions of employment (US Citizen, selective service, security clearance, DoD 8140 policy, drug testing, recall/call back, varying shifts). Also maybe "Qualifications" separate. The posting has a "Requirements Help" then Conditions of employment list. So we can put Requirements section with those items.
- Qualifications: includes Basic Requirements (education or experience), Qualifying Experience, Education details. So we can have
Qualifications
with paragraphs/lists. - Skills: Not explicitly listed but maybe implied in qualifications (Attention to Detail, Customer Service, Oral Communication, Problem Solving). Those are competencies. Could be considered Skills. The instruction: Use Skills section only if posting has real specific content. The posting lists those under Basic Requirements as "Attention to Detail - experience..." etc. Those are skills/competencies. So we could create a Skills section with those bullet points. - Benefits: The posting includes a paragraph about benefits: "A career with the U.S. government provides employees with a comprehensive benefits package..." and link. So we have benefits content. SoBenefits
with paragraph. - Pay: Not explicitly stated. There's mention: "If selected, the authorized rate of pay may exceed the stated maximum salary rate range under certain circumstances." No actual pay range. So we should NOT create Pay section because no specific pay info. - Schedule: There's mention of shift work, recall/call back 7 days/24 hours, varying work shifts. That's schedule info. So we can have Schedule section with those details. We must not repeat job title as heading. No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO etc. The posting includes many lines like "Additional Information", "Because this position is in the Cyber Excepted Service..." etc. Some of that is extra but may contain relevant info like veterans preference, telework, probation period, drug testing, recall, etc. Some of that may be considered additional info but not fitting into sections. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all substantive info, but we can place it in appropriate sections. For example, veterans preference, probation period, telework availability, moving costs, recruitment incentives, etc. Those are not covered by standard headings but could be placed under Additional Information? But we are only allowed to use the given headings. However instruction: "Prefer a few substantive sections over many thin ones." It doesn't forbid adding other headings? It says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings if we have content. It doesn't say we cannot add other headings, but likely we should stick to those. Additional info like veterans preference, probation period, telework, moving costs, recruitment incentives could be placed under Benefits? Not exactly. Could be under Requirements? Not really. Could be under Qualifications? Not. Could be under About the role? Could be additional details about the position. Might be okay to include them in About the role paragraph as extra detail. But we must preserve all substantive info; we can embed them in paragraphs. Thus we will craft sections: About the role: paragraph summarizing mission, supervision/management, senior work level, located in DISA (HC3A24), recruited under 10 USC 1599f, Cyber Excepted Service, does not convey eligibility to competitive service, etc. Responsibilities: bullet list of duties. Requirements: bullet list of conditions of employment: US Citizen, males born after 12-31-59 selective service, security clearance suitability review, DoD 8140 policy (foundational qualifications in 9 months, residential qualification in 12 months), drug testing position, subject to recall/call back during off-shift hours 7 days/24 hours, maybe subject to varying work shifts and rotations for mission support. Qualifications: we need to include basic requirements (education or experience), qualifying experience definition, education details (accredited institution, foreign education evaluation). Also maybe mention that qualifying experience must be within 30 days after closing date. Also mention that education cannot substitute for qualifying experience at GG-13. Also mention that all qualifications must be met within 30 days after closing date. Also mention that there is no substitution of education for qualifying experience at GG-13. Also mention that education must be from accredited college/university, foreign education evaluated. We can structure as paragraphs and lists. Skills: bullet list of Attention to Detail, Customer Service, Oral Communication, Problem Solving (as described). Benefits: paragraph about comprehensive benefits package, link to learn more, eligibility depends on type of position, contact hiring agency for specifics. Schedule: bullet list about shift work maybe required, recall/call back during off-shift hours 7 days/24 hours, varying work shifts, subject to recall or call back during off-shift hours 7 days/24 hours if required by upper management, shift work maybe required. We must avoid duplication: recall/call back appears both in Requirements and Schedule; we can keep in both if relevant but maybe combine. But we should not duplicate lines; but it's okay if same info appears in two sections? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". Duplicated lines likely means identical lines repeated in the source; we should not repeat them in output. So we should avoid repeating the same sentence verbatim in multiple places. We can mention recall/call back in Requirements (as condition) and Schedule (as schedule detail) but that's duplication of same fact. Might be considered duplicated lines. Better to place it only once, maybe under Requirements (as condition) and not repeat in Schedule; but Schedule should still convey schedule info: we can mention shift work maybe required, varying work shifts, etc. The recall/call back is a condition of employment but also schedule. We could mention it under Requirements and not repeat in Schedule; but then Schedule would be thin. However we can still have Schedule with shift work maybe required, varying work shifts, and note that recall/call back may be required (but that repeats). Might be okay if we rephrase differently. To avoid duplication, we can mention recall/call back only under Requirements and under Schedule just mention shift work maybe required, varying work shifts. That's acceptable. Now we need to ensure we don't include placeholder text like "commensurate with experience", "not specified", etc. We don't have those. We must not include application instructions, EEO, etc. Remove lines like "All applicants are encouraged to apply electronically..." etc. That's boilerplate; we should drop. Also remove "If you are unable to apply on-line, you may contact 317-212-0454 for assistance." etc. Also remove "Moving costs MAY be paid." etc. That's maybe substantive? It's about relocation incentives. Could be considered Benefits? Might be considered additional info but not in given headings. Could be placed under Benefits as extra detail. But it's not a guarantee; it's "MAY be paid". Might be considered substantive. We'll include it under Benefits as a note. Also "Recruitment, relocation, or retention incentives MAY be authorized." Could be under Benefits. Also "Tax Cuts and Jobs Act of 2017 makes certain reimbursements/payments taxable." That's also benefits/relocation info. We'll include those under Benefits. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. We'll need to escape any special characters like asterisks for *state-of-the-art*; we can keep italics? HTML: we can use state-of-the-art. The original had asterisks for emphasis. We'll convert to . Also need to preserve bullet points. Let's draft. About the role:
This position is being recruited under 10 U.S.C. § 1599f into the Cyber Excepted Service and does not convey eligibility to be converted to the Competitive Service. It supports the mission of U.S. Cyber Command, is in the Supervision/Management Work Category at the Senior Work Level within the CES Occupational Structure, and is located in DISA (HC3A24).
Responsibilities:- Responsible for the overall management of functions and staff required to support the installation, configuration, troubleshooting, and maintenance of hardware and software to ensure the availability and functionality of information systems.
- Manages and directs accomplishment of highly critical mission and functions of the organization supported.
- Keeps abreast of state‑of‑the‑art advanced technology by studying appropriate journals, participating in computer‑user technical seminars, maintaining contacts with vendor personnel, and taking other appropriate actions.
- Must be a U.S. Citizen.
- Males born after December 31, 1959 must be registered or exempt from Selective Service.
- Position requires a favorable suitability review and security clearance; failure to maintain eligibility may result in termination.
- Subject to DoD 8140 policy series: must complete Foundational Qualifications within 9 months and Residential Qualification requirements within 12 months.
- This is a drug‑testing position.
- Subject to recall or call‑back during off‑shift hours, 7 days a week, 24 hours a day.
- May be subject to varying work shifts and shift rotations to meet mission support requirements of 7 days/24 hours.