Cybersecurity Architect
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content.
We need to parse the posting.
First, there is "About Peraton" which is company description; we should not include as heading? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not include "About Peraton" as a heading; we can maybe include it as a
under something? But they said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. They didn't forbid company description; but they only gave examples of headings. Likely we should include "About the role" heading and then content from "About The Role". Then responsibilities maybe from that same paragraph? Actually responsibilities are described in that paragraph: ensuring implementation and maintenance of security controls, managing ATO packages, drafting security documentation, etc. So we can put responsibilities under a
Responsibilities
with- .
Requirements: maybe the "Qualifications" section includes required qualifications. They have "Qualifications Required Qualifications:" then a long list. Also "Desired Qualifications". We could combine required and desired under Requirements? Or separate Qualifications and Skills? The instruction: Use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where.
We have content: "About The Role" paragraph. Then "Qualifications Required Qualifications:" then list of required qualifications. Then "Desired Qualifications:" list. Then "Details Target Salary Range:" then benefits statement. Also "This position requires full-time, onsite attendance Monday through Friday in the Baltimore metropolitan area." That's schedule.
Thus we can map:
- About the role: the paragraph after "About The Role". Could also include the initial "About Peraton"? Probably not needed. We'll put the paragraph about the role.
- Responsibilities: extract duties from that paragraph: ensuring implementation and maintenance of security controls in accordance with RMF v5, managing ATO packages, drafting security documentation including Operating Procedures, Cybersecurity Strategy (CSS), System Security Plans (SSP) ATO packages as well as System Security and Privacy Plan (SSPP) in accordance with DoD policies, Department of Airforce (DAF) regulations and our Federal Government customer's guidance. Also must have expert knowledge and demonstrated experience with cybersecurity technologies, risk management, and incident response procedures as well as have a solid working understanding of computer functions, including hardware, software, and operating systems. This includes knowledge of Windows, Unix, and Linux operating systems, along with other applications such as databases, web servers, networking technologies, including routing, switching, and VPNs. It's a bonus if the candidate has experience with cloud computing platforms such as AWS and Azure. The candidate must be able to work autonomously, manage their workload effectively, shift priorities with little to no loss of productivity and communicate effectively with technical and non-technical personnel.
We could separate responsibilities vs requirements. But responsibilities likely the duties; qualifications are the required qualifications.
Thus responsibilities list: bullet points of duties.
Requirements: maybe the "Required Qualifications" list (the long bullet-like sentences). Could be considered requirements.
Qualifications: maybe the "Desired Qualifications"? Or we could treat "Qualifications" as the required qualifications and "Skills" as desired? But they have both headings. Let's assign:
- Requirements: the mandatory requirements (Active CompTIA Security+ and/or CASP+, Active TS clearance with SCI eligibility, Education/Experience, etc.)
- Qualifications: maybe the "Desired Qualifications" (Active CASP+ certification, experience transitioning from RMF v4 to v5, etc.)
- Skills: maybe the technical skills list (knowledge of NIST SP 800-53, etc.) but that overlaps.
Better to follow typical job posting: Responsibilities (duties), Requirements (mandatory qualifications), Qualifications (preferred qualifications), Skills (maybe technical skills). But we have a lot of overlapping content.
We need to preserve all substantive information; not invent or summarize away detail. So we need to include all content from the posting, just organized.
Thus we can create sections:
About the role
[the paragraph about the role]
Responsibilities
- Ensure implementation and maintenance of security controls in accordance with RMF v5
- Manage ATO packages
- Draft security documentation including Operating Procedures, Cybersecurity Strategy (CSS), System Security Plans (SSP) ATO packages as well as System Security and Privacy Plan (SSPP) in accordance with DoD policies, Department of Airforce (DAF) regulations and Federal Government customer guidance
- Apply expert knowledge and demonstrated experience with cybersecurity technologies, risk management, and incident response procedures
- Maintain solid working understanding of computer functions, including hardware, software, and operating systems (Windows, Unix, Linux), databases, web servers, networking technologies (routing, switching, VPNs)
- Possibly work with cloud computing platforms such as AWS and Azure (bonus)
- Work autonomously, manage workload effectively, shift priorities with little to no loss of productivity
- Communicate effectively with technical and non-technical personnel
. - Responsibilities: the duty list (ensuring implementation... managing ATO packages... drafting security documentation...). We'll put as
- .
- Requirements: the "Required Qualifications" list (the long block). We'll break into bullet points.
- Qualifications: the "Desired Qualifications" list.
- Skills: maybe we could put the technical skills from the earlier candidate must have expert knowledge etc. But we already have many overlapping. To avoid duplication, we could put those under Skills. However the instruction says prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications into one? But they ask to use headings for those sections