Cybersecurity Engineer II
for section headings.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to not repeat job title as heading.
We need to not put Job ID/requisition numbers as headings.
We need to include a section only when posting has real specific content.
We need to avoid filler like "commensurate with experience", etc.
We need to prefer few substantive sections over many thin ones.
Thus we can combine some sections.
Potential sections:
- About the role (intro paragraph)
- Responsibilities (list from What You'll Do)
- Requirements / Qualifications (maybe combine What You'll Bring, Preferred Certifications, Technical Experience)
- Benefits (list from Total Rewards)
- Pay (pay range)
- Schedule? Not mentioned; maybe not include.
We could also have Skills section (Technical Experience) but could be part of Requirements.
We need to decide.
Let's extract specifics.
About the role paragraph: as above.
Responsibilities list:
- Monitor, investigate, and respond to cybersecurity threats, incidents, and alerts.
- Lead Level 2 security investigations and coordinate incident response activities.
- Conduct vulnerability assessments, risk analyses, and remediation efforts.
- Support security frameworks and compliance initiatives, including NIST, ISO 27001, CIS Controls, and SOC 2.
- Analyze SIEM, EDR/XDR, firewall, IDS/IPS, and cloud security logs.
- Collaborate with infrastructure, application, and cloud teams to ensure secure configurations.
- Develop and maintain cybersecurity policies, procedures, and response playbooks.
- Support audits, risk assessments, disaster recovery, and business continuity activities.
- Deliver security metrics, reports, and recommendations to leadership.
- Drive security awareness and best practices across the organization.
That's a list.
Requirements/Qualifications:
From "What You'll Bring":
- 3–6 years of cybersecurity, information security, SOC, or incident response experience.
- Must be willing to work on-site for the role.
- Bachelor's degree in Cybersecurity, Information Technology, Computer Science, or related field preferred.
- Strong knowledge of network security, endpoint protection, identity and access management, threat detection, vulnerability management, and security operations.
- Experience with cloud security in AWS, Azure, or Google Cloud.
- Strong analytical, communication, and problem-solving skills.
- Ability to translate technical findings into actionable business recommendations.
Preferred Certifications: list: CISSP, CISM, Security+, CySA+, CEH, GIAC, Microsoft Security, or AWS Security certifications.
Technical Experience: Experience with SIEM platforms (Splunk, Sentinel, QRadar), EDR/XDR tools, vulnerability scanners (Nessus, Qualys, Rapid7), cloud security solutions, endpoint security, threat intelligence platforms, and scripting tools such as PowerShell, Python, or Bash.
We could combine these into a Requirements section with sublists? But we only allowed
- for any list. Could have multiple
inside section.
We could have sections: Requirements (including experience, education, certifications, technical skills). Could also have Skills section separate.
But we need to avoid many thin sections. Perhaps combine Requirements and Skills into one "Qualifications" section.
But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can choose to include About the role, Responsibilities, Qualifications, Benefits, Pay.
We need to ensure we don't create empty sections.
Let's decide:
- About the role: intro paragraph.
- Responsibilities: list of duties.
- Qualifications: combine experience, education, certifications, technical experience.
- Benefits: list from Total Rewards.
- Pay: pay range.
We'll omit Skills separate.
Now we need to strip boilerplate: remove EEO statements, application instructions, etc.
We need to keep the pay range paragraph.
Benefits list: from "Our Total Rewards package outlines all the benefits and support you’ll enjoy as part of the Schneider Electric team: Care for Yourself and Your Family. We ensure you feel secure with benefits that help you and your family thrive: medical (with member reward points), dental, vision, and basic life insurance, Benefit Bucks, flexible work arrangements, paid family leaves, well-being programs, 12 holidays per year, and 15 days of paid time off per year. Invest and Plan Your Future. We help you plan and invest for the future with competitive pay and programs including base salary, incentives, company share ownership, and 401(k) with match. Grow Your Skills and Career. We support development through performance discussions, global opportunities, the Schneider Career Hub, and learning platforms like Coursera. Team Up in the Workplace. We encourage collaboration, recognition, sharing your voice, and an inclusive workplace. Support Your Community. We make a difference through volunteer leave, programs with the Schneider Electric Foundation, youth education initiatives, and military leave benefits."
We need to turn that into a list of benefits. Could break into bullet points: medical, dental, vision, basic life insurance, Benefit Bucks, flexible work arrangements, paid family leaves, well-being programs, 12 holidays per year, 15 days PTO, base salary, incentives, company share ownership, 401(k) match, performance discussions, global opportunities, Schneider Career Hub, learning platforms like Coursera, collaboration, recognition, sharing voice, inclusive workplace, volunteer leave, programs with Schneider Electric Foundation, youth education initiatives, military leave benefits.
But we need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the details as they appear, but we can format as list items.
We should not lose any detail. So we could keep the sentences but convert to list items maybe splitting by periods. However we must not invent or summarize away detail; we can keep the same sentences but as list items.
Better to keep the prose as for benefits? The rule: Use
- for any list of duties/requirements/benefits, and
for prose. So benefits should be a list.
Thus we need to extract each benefit item as a list item. We need to ensure we don't lose any detail.
Let's parse the benefits paragraph:
"Care for Yourself and Your Family. We ensure you feel secure with benefits that help you and your family thrive: medical (with member reward points), dental, vision, and basic life insurance, Benefit Bucks, flexible work arrangements, paid family leaves, well-being programs, 12 holidays per year, and 15 days of paid time off per year."
So items: medical (with member reward points), dental, vision, basic life insurance, Benefit Bucks, flexible work arrangements, paid family leaves, well-being programs, 12 holidays per year, 15 days of paid time off per year.
Next: "Invest and Plan Your Future. We help you plan and invest for the future with competitive pay and programs including base salary, incentives, company share ownership, and 401(k) with match."
Items: base salary, incentives, company share ownership, 401(k) with match.
Next: "Grow Your Skills and Career. We support development through performance discussions, global opportunities, the Schneider Career Hub, and learning platforms like Coursera."
Items: performance discussions, global opportunities, Schneider Career Hub, learning platforms like Coursera.
Next: "Team Up in the Workplace. We encourage collaboration, recognition, sharing your voice, and an inclusive workplace."
Items: collaboration, recognition, sharing your voice, inclusive workplace.
Next: "Support Your Community. We make a difference through volunteer leave, programs with the Schneider Electric Foundation, youth education initiatives, and military leave benefits."
Items: volunteer leave, programs with the Schneider Electric Foundation, youth education initiatives, military leave benefits.
Thus we can create a
with those items.
Now Pay section: we have pay range: "For this U.S. based position, the expected pay range is USD 86,400 - USD 129,600 per year. This pay range includes base pay and short-term incentives. The compensation range for this full-time position applies to candidates located within the United States. Our pay ranges are determined by reviewing roles of similar responsibility and level. Within the pay range, individual pay is determined by several factors including performance, knowledge, job-related skills, experience, and relevant education or training."
We need to keep all that. Could be a .
Now we need to remove boilerplate: EEO statements, application instructions, etc. Also remove duplicated lines.
We need to ensure we don't include any of the following: "You must submit an online application to be considered for any position with us. This position will be posted until filled." etc. Also remove the lines about Schneider Electric values, IMPACT, etc. Those are maybe considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The IMPACT values section might be considered culture but not boilerplate; but it's somewhat generic. However it's part of "Why Join Us?" earlier. The "Why Join Us?" paragraph: "This is an opportunity to make a measurable impact on our organization's security strategy and resilience. You'll work with cross-functional leaders, drive meaningful security initiatives, and help build a stronger, more secure future while advancing your career in a collaborative and innovative environment. Bring your cybersecurity passion to a team that's ready to welcome you — apply today!" That includes application instruction at end "apply today!" which is application instruction; we should remove that. Also the earlier "Why Join Us?" maybe we can keep the first sentence as part of About the role? But we already have About the role intro. Could incorporate that into About the role? But we must not duplicate.
We have already an About the role paragraph from the start. The "Why Join Us?" paragraph is somewhat similar but we could omit because it's somewhat promotional and includes application instruction. Safer to omit.
Thus we will not include a separate "Why Join Us?" section.
Now we need to ensure we didn't inadvertently include any EEO statements: later there is a big block about Schneider Electric being an Equal Opportunity Employer, etc. Must remove.
Also remove the lines about Trust Charter, etc.
Now we need to output HTML fragment.
for prose. We need to not repeat job title as heading. We need to not put Job ID/requisition numbers as headings. We need to include a section only when posting has real specific content. We need to avoid filler like "commensurate with experience", etc. We need to prefer few substantive sections over many thin ones. Thus we can combine some sections. Potential sections: - About the role (intro paragraph) - Responsibilities (list from What You'll Do) - Requirements / Qualifications (maybe combine What You'll Bring, Preferred Certifications, Technical Experience) - Benefits (list from Total Rewards) - Pay (pay range) - Schedule? Not mentioned; maybe not include. We could also have Skills section (Technical Experience) but could be part of Requirements. We need to decide. Let's extract specifics. About the role paragraph: as above. Responsibilities list: - Monitor, investigate, and respond to cybersecurity threats, incidents, and alerts. - Lead Level 2 security investigations and coordinate incident response activities. - Conduct vulnerability assessments, risk analyses, and remediation efforts. - Support security frameworks and compliance initiatives, including NIST, ISO 27001, CIS Controls, and SOC 2. - Analyze SIEM, EDR/XDR, firewall, IDS/IPS, and cloud security logs. - Collaborate with infrastructure, application, and cloud teams to ensure secure configurations. - Develop and maintain cybersecurity policies, procedures, and response playbooks. - Support audits, risk assessments, disaster recovery, and business continuity activities. - Deliver security metrics, reports, and recommendations to leadership. - Drive security awareness and best practices across the organization. That's a list. Requirements/Qualifications: From "What You'll Bring": - 3–6 years of cybersecurity, information security, SOC, or incident response experience. - Must be willing to work on-site for the role. - Bachelor's degree in Cybersecurity, Information Technology, Computer Science, or related field preferred. - Strong knowledge of network security, endpoint protection, identity and access management, threat detection, vulnerability management, and security operations. - Experience with cloud security in AWS, Azure, or Google Cloud. - Strong analytical, communication, and problem-solving skills. - Ability to translate technical findings into actionable business recommendations. Preferred Certifications: list: CISSP, CISM, Security+, CySA+, CEH, GIAC, Microsoft Security, or AWS Security certifications. Technical Experience: Experience with SIEM platforms (Splunk, Sentinel, QRadar), EDR/XDR tools, vulnerability scanners (Nessus, Qualys, Rapid7), cloud security solutions, endpoint security, threat intelligence platforms, and scripting tools such as PowerShell, Python, or Bash. We could combine these into a Requirements section with sublists? But we only allowed
- for any list. Could have multiple
- inside section.
We could have sections: Requirements (including experience, education, certifications, technical skills). Could also have Skills section separate.
But we need to avoid many thin sections. Perhaps combine Requirements and Skills into one "Qualifications" section.
But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can choose to include About the role, Responsibilities, Qualifications, Benefits, Pay.
We need to ensure we don't create empty sections.
Let's decide:
- About the role: intro paragraph.
- Responsibilities: list of duties.
- Qualifications: combine experience, education, certifications, technical experience.
- Benefits: list from Total Rewards.
- Pay: pay range.
We'll omit Skills separate.
Now we need to strip boilerplate: remove EEO statements, application instructions, etc.
We need to keep the pay range paragraph.
Benefits list: from "Our Total Rewards package outlines all the benefits and support you’ll enjoy as part of the Schneider Electric team: Care for Yourself and Your Family. We ensure you feel secure with benefits that help you and your family thrive: medical (with member reward points), dental, vision, and basic life insurance, Benefit Bucks, flexible work arrangements, paid family leaves, well-being programs, 12 holidays per year, and 15 days of paid time off per year. Invest and Plan Your Future. We help you plan and invest for the future with competitive pay and programs including base salary, incentives, company share ownership, and 401(k) with match. Grow Your Skills and Career. We support development through performance discussions, global opportunities, the Schneider Career Hub, and learning platforms like Coursera. Team Up in the Workplace. We encourage collaboration, recognition, sharing your voice, and an inclusive workplace. Support Your Community. We make a difference through volunteer leave, programs with the Schneider Electric Foundation, youth education initiatives, and military leave benefits."
We need to turn that into a list of benefits. Could break into bullet points: medical, dental, vision, basic life insurance, Benefit Bucks, flexible work arrangements, paid family leaves, well-being programs, 12 holidays per year, 15 days PTO, base salary, incentives, company share ownership, 401(k) match, performance discussions, global opportunities, Schneider Career Hub, learning platforms like Coursera, collaboration, recognition, sharing voice, inclusive workplace, volunteer leave, programs with Schneider Electric Foundation, youth education initiatives, military leave benefits.
But we need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the details as they appear, but we can format as list items.
We should not lose any detail. So we could keep the sentences but convert to list items maybe splitting by periods. However we must not invent or summarize away detail; we can keep the same sentences but as list items.
Better to keep the prose as
- for any list of duties/requirements/benefits, and
for prose. So benefits should be a list. Thus we need to extract each benefit item as a list item. We need to ensure we don't lose any detail. Let's parse the benefits paragraph: "Care for Yourself and Your Family. We ensure you feel secure with benefits that help you and your family thrive: medical (with member reward points), dental, vision, and basic life insurance, Benefit Bucks, flexible work arrangements, paid family leaves, well-being programs, 12 holidays per year, and 15 days of paid time off per year." So items: medical (with member reward points), dental, vision, basic life insurance, Benefit Bucks, flexible work arrangements, paid family leaves, well-being programs, 12 holidays per year, 15 days of paid time off per year. Next: "Invest and Plan Your Future. We help you plan and invest for the future with competitive pay and programs including base salary, incentives, company share ownership, and 401(k) with match." Items: base salary, incentives, company share ownership, 401(k) with match. Next: "Grow Your Skills and Career. We support development through performance discussions, global opportunities, the Schneider Career Hub, and learning platforms like Coursera." Items: performance discussions, global opportunities, Schneider Career Hub, learning platforms like Coursera. Next: "Team Up in the Workplace. We encourage collaboration, recognition, sharing your voice, and an inclusive workplace." Items: collaboration, recognition, sharing your voice, inclusive workplace. Next: "Support Your Community. We make a difference through volunteer leave, programs with the Schneider Electric Foundation, youth education initiatives, and military leave benefits." Items: volunteer leave, programs with the Schneider Electric Foundation, youth education initiatives, military leave benefits. Thus we can create a
- with those items.
Now Pay section: we have pay range: "For this U.S. based position, the expected pay range is USD 86,400 - USD 129,600 per year. This pay range includes base pay and short-term incentives. The compensation range for this full-time position applies to candidates located within the United States. Our pay ranges are determined by reviewing roles of similar responsibility and level. Within the pay range, individual pay is determined by several factors including performance, knowledge, job-related skills, experience, and relevant education or training."
We need to keep all that. Could be a
. Now we need to remove boilerplate: EEO statements, application instructions, etc. Also remove duplicated lines. We need to ensure we don't include any of the following: "You must submit an online application to be considered for any position with us. This position will be posted until filled." etc. Also remove the lines about Schneider Electric values, IMPACT, etc. Those are maybe considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The IMPACT values section might be considered culture but not boilerplate; but it's somewhat generic. However it's part of "Why Join Us?" earlier. The "Why Join Us?" paragraph: "This is an opportunity to make a measurable impact on our organization's security strategy and resilience. You'll work with cross-functional leaders, drive meaningful security initiatives, and help build a stronger, more secure future while advancing your career in a collaborative and innovative environment. Bring your cybersecurity passion to a team that's ready to welcome you — apply today!" That includes application instruction at end "apply today!" which is application instruction; we should remove that. Also the earlier "Why Join Us?" maybe we can keep the first sentence as part of About the role? But we already have About the role intro. Could incorporate that into About the role? But we must not duplicate. We have already an About the role paragraph from the start. The "Why Join Us?" paragraph is somewhat similar but we could omit because it's somewhat promotional and includes application instruction. Safer to omit. Thus we will not include a separate "Why Join Us?" section. Now we need to ensure we didn't inadvertently include any EEO statements: later there is a big block about Schneider Electric being an Equal Opportunity Employer, etc. Must remove. Also remove the lines about Trust Charter, etc. Now we need to output HTML fragment.
for benefits? The rule: Use
- for any list of duties/requirements/benefits, and