Director of Cybersecurity
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, etc. Also remove application instructions. Must not create sections with filler like "commensurate with experience". So we need to parse the job description and decide which sections to include.
We have content: About the role (the initial paragraphs describing opportunity). Responsibilities (the bullet points under "Your Impact" with subheadings: Project Cybersecurity Leadership, Security Governance, Risk, and Compliance, Security Architecture and Technical Assurance, Critical Infrastructure and Operational Technology Security, Incident Response and Security Resilience, Business Development and Client Engagement, Team Leadership). Requirements (Minimum Requirements: Who You Are, Technical Expertise). Qualifications (Preferred Experience, Certifications). Skills (maybe technical expertise list). Benefits (Why Join Us? plus About WSP benefits). Pay (none given). Schedule (none given). So we should not include Pay or Schedule sections because no specific content.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include the details as they appear, but we can format them into lists where appropriate.
We need to avoid duplication. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must cut out the "Why Join Us?" maybe it's okay as it's substantive (benefits). The "About WSP" includes description of company and benefits; we can keep that as part of Benefits section. The EEO statement at end must be removed. Also the "Notice To Third Party Agencies" etc is legal boilerplate; remove.
We must not include headings for sections with no real content. So we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly also "Preferred Experience" under Qualifications, "Certifications" under Qualifications.
We need to decide how to structure. For Responsibilities, we have multiple subheadings with paragraphs. Could make each subheading as a
? But spec only says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow spec: use for section headings. It didn't say we cannot use other headings, but to be safe we can just use for each major section and inside use
and
- . For subpoints we can use
- as well.
Thus:
About the role
... (the opportunity paragraph(s))...
Then Responsibilities: we can have a with each responsibility area as - containing maybe a heading? But spec says use
- for any list of duties/requirements/benefits. So we can list each duty as a list item. We need to preserve all substantive information; we can break down each duty into its own list item with the description.
Thus:
Responsibilities
- Lead cybersecurity planning and execution for major infrastructure, transportation, utility, energy, aviation, water, and public sector programs. Develop project-specific cybersecurity strategies, architectures, roadmaps, and implementation plans. Integrate cybersecurity requirements into project delivery processes, procurement packages, technical specifications, and solution designs. Collaborate with multidisciplinary engineering, program management, and technology delivery teams. Serve as the primary cybersecurity advisor for project executives, program managers, and client stakeholders. Support project pursuits, proposals, presentations, and client interviews.
- Conduct cybersecurity risk assessments and maturity evaluations. Develop and maintain security policies, standards, procedures, and governance frameworks. Lead compliance initiatives supporting federal, state, and industry requirements. Perform gap assessments and remediation planning against established cybersecurity frameworks. Support audits and independent security assessments. Develop Plans of Action and Milestones (POA&M) and track remediation activities.
- Review and approve cybersecurity architecture for cloud, enterprise, operational technology, and PMIS environments. Evaluate technology platforms, integrations, and vendor solutions from a cybersecurity perspective. Define identity management, access control, network segmentation, encryption, monitoring, and incident response requirements. Support secure system design reviews and cybersecurity validation activities. Guide implementation of security controls across project technology ecosystems.
- Support cybersecurity initiatives involving: Industrial Control Systems (ICS) SCADA environments Operational Technology (OT) Intelligent Transportation Systems (ITS) Connected and Autonomous Vehicle infrastructure Utility control systems Airport and transit technologies Lead cybersecurity assessments of critical infrastructure environments. Develop security strategies that balance operational reliability and cyber resilience.
- Develop and maintain incident response plans and recovery procedures. Support cybersecurity incident investigations and response activities. Conduct tabletop exercises, simulations, and security preparedness reviews. Develop business continuity and disaster recovery recommendations.
- Identify cybersecurity opportunities across infrastructure markets. Support strategic pursuits and proposal development activities. Participate in conference presentations, thought leadership initiatives, and client workshops. Build trusted relationships with executive leadership and client stakeholders.
- Mentor cybersecurity professionals, project managers, and technical staff. Support recruiting, workforce development, and technical training initiatives. Foster a culture of cybersecurity awareness and continuous improvement. Provide technical quality reviews and subject matter expertise across project portfolios.
Then Requirements: we have Minimum Requirements: Who You Are (education, experience) and Technical Expertise (list). We'll make a for each? Could combine.
We'll do:
Requirements
- Bachelor's degree in Cybersecurity, Information Security, Computer Science, Engineering, Information Systems, or related discipline, or equivalent. Master's degree preferred.
- 15+ years of cybersecurity experience.
- 5+ years leading cybersecurity programs, projects, or consulting engagements.
- Demonstrated experience supporting infrastructure, transportation, aviation, utility, energy, water, or government projects.
- Experience serving in client-facing consulting or advisory roles.
- Proven ability to lead multidisciplinary project teams.
- Technical Expertise: Experience with several of the following: FISMA, NIST Cybersecurity Framework (CSF), NIST 800-53, NIST 800-171, FedRAMP, ISO 27001, CIS Critical Security Controls, NERC-CIP, PCI-DSS, HIPAA/HITRUST, Zero Trust Architecture, Cloud Security (Azure, AWS, Google Cloud), OT/ICS Security, Vulnerability Management, Security Operations and Monitoring, Identity and Access Management, Security Architecture Reviews, Risk Management and Compliance Programs.
Then Qualifications: Preferred Experience and Certifications.
Qualifications
- Preferred Experience: Candidates with experience supporting one or more of the following will be strongly preferred: Utility transmission and distribution programs, Energy generation facilities, Airport technology systems, Rail and transit programs, Intelligent transportation systems, Major capital project delivery organizations, PMIS and construction technology platforms, Smart infrastructure and connected mobility initiatives, Cloud-hosted enterprise applications supporting public agencies.
- Certifications: One or more of the following certifications is highly desirable: CISSP, CISM, CGRC (formerly CAP), CCSP, CRISC, GIAC Certifications, Security+, ISO 27001 Lead Auditor, Certified Ethical Hacker (CEH).
Then Skills: maybe we can combine technical expertise as Skills section. But we already included technical expertise under Requirements. Could also make a Skills section listing the same. But to avoid duplication, we could make a Skills section that lists the technical expertise list. However spec says prefer a few substantive sections over many thin ones. We already have Requirements covering technical expertise. Could we move technical expertise to Skills? But Requirements already includes education/experience; we could keep technical expertise under Skills. Let's think: The Minimum Requirements section includes "Technical Expertise" as a bullet. That could be considered Skills. But we can keep it under Requirements as it's part of minimum requirements. The spec says use sections like Skills if there is content. We have content for Skills (the list of technical expertise). So we could create a Skills section with that list, and keep Requirements focused on education/experience/leadership. That would avoid duplication.
Thus:
Requirements: education, years experience, leading programs, infrastructure experience, client-facing, lead multidisciplinary teams.
Skills: list of technical expertise.
Qualifications: preferred experience, certifications.
Benefits: Why Join Us? and About WSP benefits.
We must not include Pay or Schedule.
Now we need to preserve all substantive information. Let's extract the About the role paragraph: The first paragraph after "Job Description This Opportunity". Actually the text: "Job Description This Opportunity We are seeking an experienced Director of Cybersecurity to lead the planning, design, implementation, and assurance of cybersecurity programs across major infrastructure, transportation, energy, utilities, aviation, and public sector projects. This is a hand on/seller-doer role. Unlike traditional corporate IT security roles, this position is embedded directly within project delivery teams, partnering with clients, engineers, program managers, technology specialists, and executive stakeholders to ensure cybersecurity requirements are designed, implemented, validated, and maintained throughout the project lifecycle. The successful candidate will serve as a technical leader, trusted advisor, and project delivery professional, providing cybersecurity expertise for digital transformation initiatives, operational technology (OT) environments, cloud implementations, Project Management Information Systems (PMIS), critical infrastructure programs, and enterprise technology deployments. This role combines technical cybersecurity expertise, client engagement, project management, regulatory compliance, risk management, and strategic advisory services."
We need to preserve that as prose in . Also there is "Your Impact" heading but we turned into Responsibilities.
Now Benefits: "Why Join Us? You will help secure some of the nation's most important infrastructure programs while working directly with project delivery teams, owners, engineers, and technology professionals. This role offers the opportunity to influence large-scale digital transformation initiatives, critical infrastructure modernization efforts, and emerging smart infrastructure programs while shaping cybersecurity strategy from project conception through operation." Then About WSP: "ABOUT US WSP USA is the U.S. operating company of WSP, one of the world's leading engineering and professional services firms. Dedicated to serving local communities, we are engineers, planners, technical experts, strategic advisors and construction management professionals. WSP USA designs lasting solutions in the buildings, transportation, energy, water and environment markets. With more than 15,000 employees in over 300 offices across the U.S., we partner with our clients to help communities prosper. www.wsp.com WSP provides a flexible and agile workplace model while meeting client needs. Employees are also afforded a comprehensive suite of benefits including medical, dental, vision, disability, life, and retirement savings focused on providing health and financial stability throughout the employee’s career. At WSP, we want to give our employees the challenges they seek to grow their careers and knowledge base. Your daily contributions to your team will be essential in meeting client objectives, goals and challenges."
We should combine these into Benefits section as prose and maybe a list of benefits. The benefits list: medical, dental, vision, disability, life, and retirement savings. Could make a
for that.
We must not include the EEO statement at end. Also remove "Are you ready to get started?" maybe it's a call to action; could be considered application instruction? It's not exactly instruction to apply but it's a prompt. Might be considered boilerplate; safer to remove. Also remove "WSP USA (and all of its U
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include the details as they appear, but we can format them into lists where appropriate. We need to avoid duplication. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must cut out the "Why Join Us?" maybe it's okay as it's substantive (benefits). The "About WSP" includes description of company and benefits; we can keep that as part of Benefits section. The EEO statement at end must be removed. Also the "Notice To Third Party Agencies" etc is legal boilerplate; remove. We must not include headings for sections with no real content. So we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly also "Preferred Experience" under Qualifications, "Certifications" under Qualifications. We need to decide how to structure. For Responsibilities, we have multiple subheadings with paragraphs. Could make each subheading as a
? But spec only says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow spec: use
for section headings. It didn't say we cannot use other headings, but to be safe we can just use
for each major section and inside use
and
- . For subpoints we can use
- as well.
Thus:
About the role
... (the opportunity paragraph(s))...
Then Responsibilities: we can have a- with each responsibility area as
- containing maybe a heading? But spec says use
- for any list of duties/requirements/benefits. So we can list each duty as a list item. We need to preserve all substantive information; we can break down each duty into its own list item with the description.
Thus:
Responsibilities
- Lead cybersecurity planning and execution for major infrastructure, transportation, utility, energy, aviation, water, and public sector programs. Develop project-specific cybersecurity strategies, architectures, roadmaps, and implementation plans. Integrate cybersecurity requirements into project delivery processes, procurement packages, technical specifications, and solution designs. Collaborate with multidisciplinary engineering, program management, and technology delivery teams. Serve as the primary cybersecurity advisor for project executives, program managers, and client stakeholders. Support project pursuits, proposals, presentations, and client interviews.
- Conduct cybersecurity risk assessments and maturity evaluations. Develop and maintain security policies, standards, procedures, and governance frameworks. Lead compliance initiatives supporting federal, state, and industry requirements. Perform gap assessments and remediation planning against established cybersecurity frameworks. Support audits and independent security assessments. Develop Plans of Action and Milestones (POA&M) and track remediation activities.
- Review and approve cybersecurity architecture for cloud, enterprise, operational technology, and PMIS environments. Evaluate technology platforms, integrations, and vendor solutions from a cybersecurity perspective. Define identity management, access control, network segmentation, encryption, monitoring, and incident response requirements. Support secure system design reviews and cybersecurity validation activities. Guide implementation of security controls across project technology ecosystems.
- Support cybersecurity initiatives involving: Industrial Control Systems (ICS) SCADA environments Operational Technology (OT) Intelligent Transportation Systems (ITS) Connected and Autonomous Vehicle infrastructure Utility control systems Airport and transit technologies Lead cybersecurity assessments of critical infrastructure environments. Develop security strategies that balance operational reliability and cyber resilience.
- Develop and maintain incident response plans and recovery procedures. Support cybersecurity incident investigations and response activities. Conduct tabletop exercises, simulations, and security preparedness reviews. Develop business continuity and disaster recovery recommendations.
- Identify cybersecurity opportunities across infrastructure markets. Support strategic pursuits and proposal development activities. Participate in conference presentations, thought leadership initiatives, and client workshops. Build trusted relationships with executive leadership and client stakeholders.
- Mentor cybersecurity professionals, project managers, and technical staff. Support recruiting, workforce development, and technical training initiatives. Foster a culture of cybersecurity awareness and continuous improvement. Provide technical quality reviews and subject matter expertise across project portfolios.
- for each? Could combine.
We'll do:
- Bachelor's degree in Cybersecurity, Information Security, Computer Science, Engineering, Information Systems, or related discipline, or equivalent. Master's degree preferred.
- 15+ years of cybersecurity experience.
- 5+ years leading cybersecurity programs, projects, or consulting engagements.
- Demonstrated experience supporting infrastructure, transportation, aviation, utility, energy, water, or government projects.
- Experience serving in client-facing consulting or advisory roles.
- Proven ability to lead multidisciplinary project teams.
- Technical Expertise: Experience with several of the following: FISMA, NIST Cybersecurity Framework (CSF), NIST 800-53, NIST 800-171, FedRAMP, ISO 27001, CIS Critical Security Controls, NERC-CIP, PCI-DSS, HIPAA/HITRUST, Zero Trust Architecture, Cloud Security (Azure, AWS, Google Cloud), OT/ICS Security, Vulnerability Management, Security Operations and Monitoring, Identity and Access Management, Security Architecture Reviews, Risk Management and Compliance Programs.
- Preferred Experience: Candidates with experience supporting one or more of the following will be strongly preferred: Utility transmission and distribution programs, Energy generation facilities, Airport technology systems, Rail and transit programs, Intelligent transportation systems, Major capital project delivery organizations, PMIS and construction technology platforms, Smart infrastructure and connected mobility initiatives, Cloud-hosted enterprise applications supporting public agencies.
- Certifications: One or more of the following certifications is highly desirable: CISSP, CISM, CGRC (formerly CAP), CCSP, CRISC, GIAC Certifications, Security+, ISO 27001 Lead Auditor, Certified Ethical Hacker (CEH).
Requirements
Qualifications
. Also there is "Your Impact" heading but we turned into Responsibilities. Now Benefits: "Why Join Us? You will help secure some of the nation's most important infrastructure programs while working directly with project delivery teams, owners, engineers, and technology professionals. This role offers the opportunity to influence large-scale digital transformation initiatives, critical infrastructure modernization efforts, and emerging smart infrastructure programs while shaping cybersecurity strategy from project conception through operation." Then About WSP: "ABOUT US WSP USA is the U.S. operating company of WSP, one of the world's leading engineering and professional services firms. Dedicated to serving local communities, we are engineers, planners, technical experts, strategic advisors and construction management professionals. WSP USA designs lasting solutions in the buildings, transportation, energy, water and environment markets. With more than 15,000 employees in over 300 offices across the U.S., we partner with our clients to help communities prosper. www.wsp.com WSP provides a flexible and agile workplace model while meeting client needs. Employees are also afforded a comprehensive suite of benefits including medical, dental, vision, disability, life, and retirement savings focused on providing health and financial stability throughout the employee’s career. At WSP, we want to give our employees the challenges they seek to grow their careers and knowledge base. Your daily contributions to your team will be essential in meeting client objectives, goals and challenges." We should combine these into Benefits section as prose and maybe a list of benefits. The benefits list: medical, dental, vision, disability, life, and retirement savings. Could make a
- for that.
We must not include the EEO statement at end. Also remove "Are you ready to get started?" maybe it's a call to action; could be considered application instruction? It's not exactly instruction to apply but it's a prompt. Might be considered boilerplate; safer to remove. Also remove "WSP USA (and all of its U
- for any list of duties/requirements/benefits. So we can list each duty as a list item. We need to preserve all substantive information; we can break down each duty into its own list item with the description.
Thus:
- containing maybe a heading? But spec says use
- as well.
Thus:
- . For subpoints we can use