Principal Cyber Architect

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job description. First, we need to identify sections: The posting includes a description of duties (supporting systems engineering teams, A&A, etc). That's responsibilities. Then required education, experience, & skills (required). Then preferred education, experience, & skills (preferred). Then Pay Information. Then Employee Benefits. Then About BAE Systems Electronic Systems (company description). There's also mention of travel (business travel). Also schedule? Not mentioned. So we may not include Schedule unless present. There's no explicit schedule (like full-time, part-time). It says Full-Time Salary Range, implying full-time. But schedule not given explicitly; we could infer full-time but rule: never create Pay/Schedule/Benefits sections unless posting actually states them. For Schedule, we need explicit statement like "Full-time", "Part-time", "Shift work", etc. It says "Full-Time Salary Range". That indicates full-time but not a schedule section. Might be okay to include Schedule? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states Pay (yes). Benefits (yes). Schedule? It says Full-Time Salary Range, but not a separate schedule statement. I'd argue schedule is implied but not explicitly stated as a section. Safer to omit Schedule section. Now we need headings:

for each section. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove repeated lines (like duplicated responsibilities). Need to deduplicate. We need to include About the role? The posting doesn't have an explicit "About the role" heading but we can create a section with that heading if we have content describing the role. The rule: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings. We need to include a section only when posting has real specific content for it. So we can have About the role (maybe a brief summary). But we must not invent or summarize away detail. We could put a short paragraph summarizing the role based on the description, but that would be summarizing. Better to treat the description as Responsibilities. About the role could be a short paragraph that is essentially the same as responsibilities? Might be considered summarizing. Safer to not include About the role if we don't have explicit content. However the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't mandate we must include About the role. It says include a section ONLY when the posting has real, specific content for it. So we can omit About the role if we don't have a distinct block. Thus sections: Responsibilities, Requirements (maybe combine required and preferred?), Qualifications, Skills, Benefits, Pay. But we need to avoid duplication. The posting has "Required Education, Experience, & Skills" and "Preferred Education, Experience, & Skills". Could combine into Requirements (required) and Qualifications (preferred) or Skills. Let's map: - Responsibilities: list of duties (supporting systems engineering teams, supporting A&A, supporting traditional SE tasks, supporting offensive architecture analysis, supporting DevSecOps integration, supporting development and assessment of system security plans, conducting vulnerability assessments, analyzing static/dynamic code scans, business travel). We'll need to deduplicate repeated lines. - Requirements: Required Education, Experience, & Skills: Bachelor of Science degree in a Cyber, Systems, Software, Electrical, Mechanical or similarly related engineering/technical discipline, and 6+ year(s) related experience or equivalent experience, training and/or certifications. At least one DoDM 8140 (DCWF 652-series) compliant certification: CCSP, CISSP-ISSEP/ISSAP, CSSLP, Cloud+ or equivalent. Understanding of MBSE and experience with Cameo. Also includes some repeated responsibilities lines? Actually after required they repeated some responsibilities lines again (like supporting A&A etc). Those are duplicates; we should not duplicate. - Qualifications: Could be Preferred Education, Experience, & Skills: Other cyber certifications desired (e.g., GISF, CASP+, Cloud+, GSEC, AWS CSA Professional, OSCP, etc.) Understanding of Zero Trust Architecture and ability to model Zero Trust into the overall system architecture. Understanding of offensive security tactics, techniques and procedures. Experience with Cyber FMECA. Experience writing proposals with innovative cost-effective solutions. Experience with offensive architecting, threat modeling and attack vector analysis. Experience with cloud and cross domain solution accreditations. Ability to negotiate effectively with higher level managers, functional managers, customers, industry partners, and teammates. Demonstrated leadership skills (supervisory experience, building teams, building customer relationships). Experience with leading and coordinating security test events to achieve accreditation milestones. Experience with verifying and validating vulnerability resolutions and/or mitigations. Experience with Attack and Threat modeling. Strong mentoring skills. Good planning and organizational skills. Strong oral and written communications skills. Note that some of these are also skills. Could treat them as Skills section. But we have both Qualifications and Skills headings allowed. We could put preferred qualifications under Qualifications, and skills under Skills (like planning, communication). However the preferred list includes many skill-like items. Might be better to have Qualifications for preferred education/experience/certifications, and Skills for abilities like planning, communication, leadership, mentoring, negotiation, etc. But we need to avoid duplication and ensure we preserve all info. Simplify: Have two sections: Requirements (required) and Qualifications (preferred). Then maybe a Skills section for the soft skills (good planning, strong oral/written communications, leadership, mentoring, negotiation). But the preferred list also includes those. Could combine. Given the instruction to prefer a few substantive sections over many thin ones, we could have: Responsibilities, Requirements (combining required and preferred), Benefits, Pay. But we need to capture certifications etc. Might be okay to have Requirements include both required and preferred, but then we lose distinction. However the rule says preserve all substantive information; we can still include both required and preferred within Requirements section, maybe using subheadings? But we cannot add extra headings beyond

  for sections; we could use

  to differentiate. Better: Have sections: Responsibilities, Requirements (required), Qualifications (preferred), Benefits, Pay. That's five sections. Now we need to format lists. Responsibilities: list items: - Supporting systems engineering teams - Supporting Assessment and Authorization (A&A) activities for DoD Systems in accordance with Risk Management Framework - Supporting traditional systems engineering tasks such as CONOPS, requirements development and allocation, cyber design engineering, cyber implementation engineering, verification and validation, and continuous monitoring efforts during deployment, operations and sustainment - Supporting offensive architecture analysis and design of defense-in-depth solutions - Supporting Development Security Operations (DevSecOps) integration - Supporting the development and assessment of system security plans including, security concepts of operation, risk management matrix, security control traceability matrix, security test procedures, and plan of action and milestones - Conducting and analyzing vulnerability assessments to validate system compliance with RMF controls and DISA Security Technical Information Guidelines (STIG) - Analyzing static code scans and dynamic code scans to validate Application Security and Development STIG compliance - This position may require business travel to customer locations in support of customer meetings, product demonstration, integration and/or systems testing. We need to ensure no duplicate lines. The posting had some duplicate lines after required section; we removed. Now Requirements (required): - Bachelor of Science degree in a Cyber, Systems, Software, Electrical, Mechanical or similarly related engineering/technical discipline - 6+ year(s) related experience or equivalent experience, training and/or certifications - At least one DoDM 8140 (DCWF 652-series) compliant certification: CCSP, CISSP-ISSEP/ISSAP, CSSLP, Cloud+ or equivalent - Understanding of MBSE and experience with Cameo We could also include "Understanding of MBSE and experience with Cameo" as a requirement. Now Qualifications (preferred): - Other cyber certifications desired (e.g., GISF, CASP+, Cloud+, GSEC, AWS CSA Professional, OSCP, etc.) - Understanding of Zero Trust Architecture and ability to model Zero Trust into the overall system architecture - Understanding of offensive security tactics, techniques and procedures - Experience with Cyber Failure Mode, Effects, and Criticality Analysis (FMECA) - Experience writing proposals with innovative cost-effective solutions - Experience with offensive architecting, threat modeling and attack vector analysis - Experience with cloud and cross domain solution accreditations - Ability to negotiate effectively with higher level managers, functional managers, customers, industry partners, and teammates - Demonstrated leadership skills (supervisory experience, building teams, building customer relationships) - Experience with leading and coordinating security test events to achieve accreditation milestones - Experience with verifying and validating vulnerability resolutions and/or mitigations - Experience with Attack and Threat modeling - Strong mentoring skills - Good planning and organizational skills - Strong oral and written communications skills Note that "Good planning and organizational skills" and "Strong oral and written communications skills" appear both in required? Actually they appear in preferred list; also earlier in the description after required they repeated "Good planning and organizational skillsStrong oral and written communications skills". We'll include them only once. Now Benefits: The posting includes Employee Benefits paragraph. We need to turn into a list? It says use

  • for any list of duties/requirements/benefits. So we should list benefits as list items. Benefits list: - Health, dental, and vision insurance - Health savings accounts - 401(k) savings plan - Disability coverage - Life and accident insurance - Employee assistance program - Legal plan - Discounts on home, auto, and pet insurance - Paid time off - Paid holidays - Paid parental leave - Military leave - Bereavement leave - Applicable federal and state sick leave - Company recognition program (monetary or non-monetary recognition awards) - Other incentives may be available based on position level and/or job specifics We need to preserve all substantive information; we can break the paragraph into items. Now Pay: The posting includes Pay Information: Full-Time Salary Range: $118095 - $200762. Also note about market pay structures etc. We need to preserve all substantive information; we can include a paragraph with that info. Since it's not a list, we can use

    . We should not include the note about "Please note: This range is based on our market pay structures..." as it's part of pay info; we should keep it. Now we need to output only HTML fragment, no /, no markdown. Thus:

    Responsibilities

    • ...
    ...

    Requirements

    ...

    Qualifications

    ...

    Benefits

    ...

    Pay

    Full-Time Salary Range: $118095 - $200762. Please note: This range is based on our market pay structures. However, individual salaries are determined by a variety of factors including, but not limited to: business considerations, local market conditions, and internal equity, as well as candidate qualifications, such as skills, education, and experience.

    We need to ensure we didn't include Schedule section. Check for any duplicated content: Ensure