Principal Cyber Security Architect (Remote Eligible, U.S.)

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect those headings. We need to include sections only when posting has real specific content. Thus we need to decide content for each: - About the role: yes. - Responsibilities: yes. - Requirements: could include required qualifications + eligibility (location/travel). That seems reasonable. - Qualifications: maybe "Desired Characteristics" (preferred). But they also have "Desired Characteristics" list. Could treat that as Qualifications. - Skills: maybe the specific technical skills list within desired characteristics? But the desired characteristics list already includes many skills. Could split: Qualifications = education/experience; Skills = technical skills (tools, protocols, certifications). However the instruction says prefer a few substantive sections over many thin ones. So maybe we combine desired characteristics into either Qualifications or Skills, not both. But we have both headings available; we could use both if content distinct. Let's examine desired characteristics list: - Minimum 4 years of experience working with product security requirements, regulations and/or standards, such as IEC 62443 series of standards or equivalent. - Demonstrated knowledge and understanding cybersecurity tools/solutions (e.g., Firewalls, antivirus, SIEM, IDS/IPS), including experience providing installation/configuration recommendations. - Master's degree in a relevant field. - Wind Turbine product knowledge and/or SCADA product/cyber security knowledge. - Knowledge and understanding of network cyber security practices. - Familiarity with containerization technologies (Docker, Kubernetes) and associated security best practices. - Cyber security certification (ex. GICSP, CEH, CCNA, CISSP). - Experience with cloud security principles and practices. - Experience with secure coding practices in any language. - Experience with penetration testing and vulnerability assessment tools for OT environments. - Strong understanding of operational technologies (e.g., PLCs) and protocols (e.g., Modbus, Profinet, DNP3, OPC [DA, AE, UA], IEC 61850) used in manufacturing, power generation, wind farms, SCADA systems, and other industrial environments or industrial products. - Ability to work independently and collaboratively as necessary with a cross-functional team. - Strong oral and written communication skills. - Demonstrated ability to analyze and resolve problems. - Experience responding to product cyber security vulnerabilities. - Experience responding cybersecurity inquiries. These are a mix of experience, knowledge, skills, certifications, soft skills. We could put them under "Skills" (technical and soft skills). And put "Qualifications" for education/experience basics (Bachelor's, 12 years experience, etc.) plus maybe eligibility. But we also have "Required Qualifications" which is basically education + experience. That could go under Qualifications. Then "Eligibility Requirements" (remote, location preference, travel) could go under Requirements. Thus: - About the role: summary paragraph. - Responsibilities: list of essential responsibilities. - Requirements: eligibility (remote, location preference, travel). Could also include any other mandatory requirements like "Ability and willingness to travel up to 10%..." etc. - Qualifications: required qualifications (Bachelor's degree, 12 years experience, 8+ years OT cybersecurity). Could also include maybe "Minimum 4 years experience with product security requirements..." but that's desired; but we could still put under Qualifications if we want. However to avoid duplication, we keep required qualifications there. - Skills: desired characteristics list (technical skills, certifications, soft skills). - Benefits: list of benefits (medical, dental, vision, prescription drug coverage; Health Coach; Employee Assistance Program; Retirement Savings Plan; tuition assistance; adoption assistance; paid parental leave; disability benefits; life insurance; 12 paid holidays; permissive time off). Also note that GE Vernova sponsors certain employee benefit plans, reserves right to amend, etc. That's boilerplate but still part of benefits description. We should preserve substantive info; the boilerplate about reserving right to amend is maybe legal but still part of benefits. However instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits legal disclaimer might be considered legal boilerplate. But it's part of benefits description; maybe we keep the substantive benefits and drop the legal disclaimer about reserving right to amend, etc. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". The benefits legal disclaimer is legal boilerplate; we should drop it. So we keep the list of benefits. - Pay: The posting includes pay range: $131,700.00 to $219,300.00, geographic differential 110%,120%,130% of salary in certain areas, bonus eligibility: discretionary annual bonus. Also mentions "Application Deadline: October 09, 2026" and "This posting is expected to remain open for at least seven days after it was posted on September 25, 2026." That's not pay/schedule but could be considered metadata; we should drop application instructions and dates. So Pay section: include pay range and geographic differential and bonus eligibility. - Schedule: The posting does not mention schedule (e.g., full-time, hours). No schedule info. So we should not create a Schedule section. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We must not include empty sections. Now format:

About the role

...

Responsibilities

• ...
...

Requirements

...

Qualifications

...

• for any list of duties/requirements/benefits. For qualifications, it's a list of items; we could treat as list. But they said "any list of duties/requirements/benefits". Qualifications is not explicitly mentioned but could be considered requirements. Safer to use
  • for qualifications as well? The instruction: "Use
    • for any list of duties/requirements/benefits". It doesn't forbid using lists for other sections, but we can follow. We'll use
      • for qualifications list. Similarly for Skills: list. Benefits: list. Pay: maybe paragraph. Now need to preserve all substantive information, not invent or summarize away detail. Let's extract exact text. About the role paragraph: We'll copy the summary paragraph exactly as given, but we can trim extra spaces. Summary: "GE Vernova is seeking a highly skilled and experienced Principal Cyber Security Architect to join the Product Security team, focusing on the Wind portfolio of products. This role is responsible for conducting in-depth cyber security assessments of wind farm design and architecture at both the product and component levels. This includes leading these assessments in accordance with GE Vernova’s Secure Development Lifecycle (SDL) process, aligned with IEC 62443-4-1, and reviewing applicable requirements outlined in IEC 62443-4-2 and IEC 62443-3-2 standards. The role involves collaboration with various subsystem teams to identify relevant products and execute these assessments. This position reports to Wind's Product Security Leader, who oversees Wind's Product Security Team. The Product Security Team drives a product cyber security strategy aimed at meeting applicable standards and regulations while leading the industry towards more fundamentally secure wind farms." That's fine. Responsibilities: list each bullet. From text: "Lead and conduct comprehensive cybersecurity assessments of wind turbine components, SCADA systems, Wind Farm software, and digital service platforms following the defined engineering processes. Provide expert guidance on the interpretation and application of security controls following IEC 62443 series of standards (specifically IEC 62443-4-1 and IEC 62443-3-3) during the requirements definition, design development and product validation phases of the development lifecycle. Perform threat modeling and risk assessments for new and existing products and features. Identify and document security vulnerabilities, risks, and non-conformities within products and systems and provide recommendations for remediation. Collaborate closely with product development, engineering, projects, services, and R&D teams to integrate security by design principles throughout the product lifecycle. Propose recommendations and facilitate discussion on high level wind-farm level security improvements that can be driven across