Cybersecurity Architect - Principal
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have description summary (About the role). Duties And Responsibilities -> Responsibilities. Basic Qualifications -> Requirements? Could be Requirements. Preferred Qualifications -> Qualifications? Or Skills? The spec: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly.
We have: Description Summary (About the role). Duties And Responsibilities (Responsibilities). Basic Qualifications (Requirements). Preferred Qualifications (Qualifications). Also there are many specific knowledge items; could be Skills. Benefits: mention health insurance, wellness program, life and disability insurance, retirement savings plan, paid leave programs, paid holidays and paid time off (PTO). Also incentive compensation plan. Pay: Compensation Range $93,000 - $189,000 Annual Salary. Also mention incentive compensation plan. Schedule: Not explicitly given; only mention flexible work arrangement, office, remote possibilities. There's mention: "Our Approach to Office Workplace Type Certain positions outside our branch network may be eligible for a flexible work arrangement. We’re combining the best of both worlds: in-office and work from home. Our approach enables our teams to deepen connections, maintain a strong community, and do their best work. Remote roles will also have the opportunity to come together in our offices for moments that matter. Specific work arrangements will be provided by the hiring team." That's schedule/flexible work info. So we can include Schedule section with that content.
We must not include boilerplate like EEO, Tobacco-Free Hiring Practice, Note to Agency Recruiters, etc. Also remove duplicated lines.
We must preserve all substantive information; do not invent or summarize away detail. Must not create sections with filler like "commensurate with experience". We have actual content.
We need to output only HTML fragment, no /, no markdown fences.
Structure: maybe multiple sections each with heading then content:
for prose,
- for lists.
We need to decide what to list as lists: Duties And Responsibilities list items: "Deliver cybersecurity architecture work associated with projects delivery and roadmaps", "Provide technical leadership to the cybersecurity organization", "Perform research and development associated with enabling future cybersecurity capabilities". Also earlier description includes many responsibilities but we can keep as prose? The instruction: Use
- for any list of duties/requirements/benefits. So we should turn those into list.
Basic Qualifications list: "4+ years cybersecurity architecture.", "8+ years of information security experience.", "10+ years of experience delivering technology solutions in large-scale complex organizations.", "Associate's Degree or 4+ additional years of equivalent experience." Could be list.
Preferred Qualifications list: many items. Could be list but might be long; still list.
Skills: maybe we can extract from Preferred Qualifications the skill items: "Extensive knowledge of traditional security controls and technologies, such as: SIEM systems, IDS/IPS, PKI, IDAM systems, antivirus and firewalls.", "Newer offerings such as EDR, threat intelligence platforms, security automation and orchestration, deception technologies and application controls", etc. Could be list.
But we already have Preferred Qualifications as a section; maybe we treat Preferred Qualifications as Qualifications section, and Skills separate? The spec includes both Qualifications and Skills headings. We need to decide what goes where. Could put Basic Qualifications under Requirements, Preferred Qualifications under Qualifications, and then extract skill-specific items under Skills. However the Preferred Qualifications already includes many skill items; we could split: Qualifications: education/experience requirements (like 5+ years experience in architecture, governance, etc). Skills: technical knowledge items.
Let's parse Preferred Qualifications text:
"Extensive knowledge of traditional security controls and technologies, such as: Security Information and Event Management (SIEM) systems, intrusion detection/prevention systems (IDS/IPS), public key infrastructure (PKI), identity and access management (IDAM) systems, antivirus and firewalls.
Newer offerings such as endpoint detection and response (EDR), threat intelligence platforms, security automation and orchestration, deception technologies and application controls
5+ years of experience in architecture, governance, risk management, PCI DSS control governance, application security, encryption, key management, and identity and access management
Experience with a broad range of mobile and wed application design, development, and management principles, practices, and procedures
Experience influencing management on technical and business solutions
Experience in cloud computing technologies, including software-, infrastructure and platform-as-a-service, as well as public, private and hybrid environments
Excellent verbal, written, and interpersonal communication skills
Knowledge and understanding of data protection technologies and practices
Knowledge and understanding of threat analysis and assessment of potential and current information security risk/threats
Strong understanding of application or software security such as: dynamic application security testing, secure code review, and secure static code analysis
Knowledge and understanding of cryptography and key management
Knowledge and understanding of service-oriented architecture and associated security controls
Knowledge and understanding of enterprise authentication and authorization technologies such as LDAP, SAML, XACML, and reverse authenticating proxies.
General understanding of diverse platforms and operating systems, including current and emerging technologies
Certified Information Systems Security Professional (CISSP)
Experience architecting applications for financial services business"
We can separate: Qualifications: maybe the experience items (5+ years experience..., Experience with..., Experience influencing..., Experience in cloud..., etc). Skills: the knowledge items (Extensive knowledge..., Newer offerings..., Knowledge..., Strong understanding..., etc). Also certifications.
But to keep simple, we could put all Preferred Qualifications under Qualifications section as a list, and not create Skills section unless we have distinct skill content. However spec says we should include a section only when posting has real, specific content for it. If we put all under Qualifications, we still have Skills section empty -> we must not emit it. So we need to decide if we have enough to fill Skills meaningfully. We could extract skill items as list under Skills.
Thus we will have sections:
- About the role (from Description Summary)
- Responsibilities (Duties And Responsibilities)
- Requirements (Basic Qualifications)
- Qualifications (Preferred Qualifications experience items maybe)
- Skills (Preferred Qualifications knowledge items)
- Benefits (benefits description)
- Pay (Compensation Range)
- Schedule (flexible work arrangement description)
We must not include headings with empty content.
Now we need to format.
Let's extract About the role prose: The description summary paragraph(s). It's a bit long; we can keep as
preserving all sentences. Responsibilities list: three items. Requirements list: four items. Qualifications list: we need to decide which items go here. Perhaps the items that are experience/years: "5+ years of experience in architecture, governance, risk management, PCI DSS control governance, application security, encryption, key management, and identity and access management", "Experience with a broad range of mobile and wed application design, development, and management principles, practices, and procedures", "Experience influencing management on technical and business solutions", "Experience in cloud computing technologies, including software-, infrastructure and platform-as-a-service, as well as public, private and hybrid environments", "Certified Information Systems Security Professional (CISSP)", "Experience architecting applications for financial services business". Also maybe "Excellent verbal, written, and interpersonal communication skills" could be skill but we could put under Skills. Skills list: items about knowledge: "Extensive knowledge of traditional security controls and technologies, such as: SIEM systems, IDS/IPS, PKI, IDAM systems, antivirus and firewalls.", "Newer offerings such as EDR, threat intelligence platforms, security automation and orchestration, deception technologies and application controls", "Knowledge and understanding of data protection technologies and practices", "Knowledge and understanding of threat analysis and assessment of potential and current information security risk/threats", "Strong understanding of application or software security such as: dynamic application security testing, secure code review, and secure static code analysis", "Knowledge and understanding of cryptography and key management", "Knowledge and understanding of service-oriented architecture and associated security controls", "Knowledge and understanding of enterprise authentication and authorization technologies such as LDAP, SAML, XACML, and reverse authenticating proxies.", "General understanding of diverse platforms and operating systems, including current and emerging technologies". Benefits list: "health insurance coverage, wellness program, life and disability insurance, retirement savings plan, paid leave programs, paid holidays and paid time off (PTO)". Also "applicable incentive compensation plan". Could be list. Pay: "Compensation Range $93,000 - $189,000 Annual Salary". Also mention incentive compensation plan but we already put under benefits; maybe keep in Pay? Actually incentive compensation plan is separate from base compensation; we could mention under Pay as "eligible to participate in an applicable incentive compensation plan". We'll include that. Schedule: description about flexible work arrangement. Now produce HTML. We must not include any extra text outside HTML. Let's craft. We'll open with maybe a but not required. Just output headings and content. We'll use
About the role
then...
. ThenResponsibilities
- ... etc.
Then
Requirements
- ...
Then
Qualifications
- ...
Then
Skills
- ...
Then
Benefits
- ...
Then
Pay
... maybe also list? We'll just
. Then
Schedule
... Make sure to preserve all details exactly as in posting, but we can rephrase slightly? Must not invent or summarize away detail. We can keep the exact sentences. Let's copy the About the role text exactly as given: "Description Summary: The Cybersecurity Architect - Principal reports to the Cybersecurity Architect Senior Manager and frequently interacts with the Chief Information Security Officer, as well as audit and compliance. The Cybersecurity Architect - Principal is responsible for designing security solutions that protect business and customer data, but also allow the business to execute and innovate. The Cybersecurity Architect - Principal works closely with many diverse and dynamic teams, including, but not limited to, security engineering, IT infrastructure, application development, security operations, security audit and end users. This position is also responsible for architecting solutions to secure business-to-business initiatives, third-party relationships, outsourced solutions and vendors. The Cybersecurity Architect - Principal provides expert guidance for addressing current security issues but has the foresight to see where the industry is headed and proactively deliver optimal secure solutions. The architect is expected to think like an adversary and identify how solutions should evolve as the threat landscape changes. The position is 40% security architecture, 50% technical leadership, and 10% research and development. The individual partners with product managers and solution architects to set the security direction of offerings and articulates the value proposition. Also, the position provides guidance to Line of Business CIOs and is the final approver of information security controls on projects. Guides businesses to leverage common information security patterns Partners with subject matter experts to improve information security patterns and services" Note there is a missing period between "patterns" and "Partners". We'll keep as is. Now Responsibilities list items exactly: "Deliver cybersecurity architecture work associated with projects delivery and roadmaps" "Provide technical leadership to the cybersecurity organization" "Perform research and development associated with enabling future cybersecurity capabilities" Now Requirements list items exactly: "4+ years cybersecurity architecture." "8+ years of information security experience." "10+ years of experience delivering technology solutions in large-scale complex organizations." "Associate's Degree or 4+ additional years of equivalent experience." Now
- ... etc.
Then
- for any list of duties/requirements/benefits. So we should turn those into list.
Basic Qualifications list: "4+ years cybersecurity architecture.", "8+ years of information security experience.", "10+ years of experience delivering technology solutions in large-scale complex organizations.", "Associate's Degree or 4+ additional years of equivalent experience." Could be list.
Preferred Qualifications list: many items. Could be list but might be long; still list.
Skills: maybe we can extract from Preferred Qualifications the skill items: "Extensive knowledge of traditional security controls and technologies, such as: SIEM systems, IDS/IPS, PKI, IDAM systems, antivirus and firewalls.", "Newer offerings such as EDR, threat intelligence platforms, security automation and orchestration, deception technologies and application controls", etc. Could be list.
But we already have Preferred Qualifications as a section; maybe we treat Preferred Qualifications as Qualifications section, and Skills separate? The spec includes both Qualifications and Skills headings. We need to decide what goes where. Could put Basic Qualifications under Requirements, Preferred Qualifications under Qualifications, and then extract skill-specific items under Skills. However the Preferred Qualifications already includes many skill items; we could split: Qualifications: education/experience requirements (like 5+ years experience in architecture, governance, etc). Skills: technical knowledge items.
Let's parse Preferred Qualifications text:
"Extensive knowledge of traditional security controls and technologies, such as: Security Information and Event Management (SIEM) systems, intrusion detection/prevention systems (IDS/IPS), public key infrastructure (PKI), identity and access management (IDAM) systems, antivirus and firewalls.
Newer offerings such as endpoint detection and response (EDR), threat intelligence platforms, security automation and orchestration, deception technologies and application controls
5+ years of experience in architecture, governance, risk management, PCI DSS control governance, application security, encryption, key management, and identity and access management
Experience with a broad range of mobile and wed application design, development, and management principles, practices, and procedures
Experience influencing management on technical and business solutions
Experience in cloud computing technologies, including software-, infrastructure and platform-as-a-service, as well as public, private and hybrid environments
Excellent verbal, written, and interpersonal communication skills
Knowledge and understanding of data protection technologies and practices
Knowledge and understanding of threat analysis and assessment of potential and current information security risk/threats
Strong understanding of application or software security such as: dynamic application security testing, secure code review, and secure static code analysis
Knowledge and understanding of cryptography and key management
Knowledge and understanding of service-oriented architecture and associated security controls
Knowledge and understanding of enterprise authentication and authorization technologies such as LDAP, SAML, XACML, and reverse authenticating proxies.
General understanding of diverse platforms and operating systems, including current and emerging technologies
Certified Information Systems Security Professional (CISSP)
Experience architecting applications for financial services business"
We can separate: Qualifications: maybe the experience items (5+ years experience..., Experience with..., Experience influencing..., Experience in cloud..., etc). Skills: the knowledge items (Extensive knowledge..., Newer offerings..., Knowledge..., Strong understanding..., etc). Also certifications.
But to keep simple, we could put all Preferred Qualifications under Qualifications section as a list, and not create Skills section unless we have distinct skill content. However spec says we should include a section only when posting has real, specific content for it. If we put all under Qualifications, we still have Skills section empty -> we must not emit it. So we need to decide if we have enough to fill Skills meaningfully. We could extract skill items as list under Skills.
Thus we will have sections:
- About the role (from Description Summary)
- Responsibilities (Duties And Responsibilities)
- Requirements (Basic Qualifications)
- Qualifications (Preferred Qualifications experience items maybe)
- Skills (Preferred Qualifications knowledge items)
- Benefits (benefits description)
- Pay (Compensation Range)
- Schedule (flexible work arrangement description)
We must not include headings with empty content.
Now we need to format.
Let's extract About the role prose: The description summary paragraph(s). It's a bit long; we can keep as