Cybersecurity Engineer (Linux DevSecOps Engineer)

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 posting. First, we have intro about WBD, but not needed? The job title is not repeated. The posting includes "Your New Role:" description, then "Your Role Accountabilities:" list of duties, then "Qualifications & Experiences:" list, then "How We Get Things Done..." (guiding principles) maybe not needed. Then "Championing Inclusion..." EEO boilerplate to remove. Then compensation disclosure: Pay Range: $91,000 - $169,000 per year. Also benefits: "Other rewards may include annual bonuses... In addition, Warner Bros. Discovery provides a variety of benefits to employees, including health insurance coverage, an employee wellness program, life and disability insurance, a retirement savings plan, paid holidays and sick time and vacation." Also hybrid model note: "*Must work a hybrid model (3 days onsite) out of our Silver Spring, DC, or Atlanta office.*" That's schedule/location info. Could be Schedule section. We need sections: About the role (maybe from "Your New Role:" description). Responsibilities (from "Your Role Accountabilities:" list). Qualifications (maybe from "Qualifications & Experiences:" list). Skills (maybe extract specific skills like Linux, scripting, etc). Benefits (benefits description). Pay (pay range). Schedule (hybrid model). We should not create sections with filler. We must not repeat job title as heading. No Job ID. We must use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions. We need to ensure we include all substantive info from posting. Let's extract content. Intro: "Welcome to Warner Bros. Discovery… the stuff dreams are made of.Who We Are… When we say, “the stuff dreams are made of,” we’re not just referring to the world of wizards, dragons and superheroes, or even to the wonders of Planet Earth. Behind WBD’s vast portfolio of iconic content and beloved brands, are the storytellers bringing our characters to life, the creators bringing them to your living rooms and the dreamers creating what’s next…From brilliant creatives, to technology trailblazers, across the globe, WBD offers career defining opportunities, thoughtfully curated benefits, and the tools to explore and grow into your best selves. Here you are supported, here you are celebrated, here you can thrive. *Must work a hybrid model (3 days onsite) out of our Silver Spring, DC, or Atlanta office.*" That's generic company description; maybe we can put under About the role? But About the role should be about the role, not company. However we could include a brief About the role paragraph summarizing the role description: "The WBD Security Engineering team empowers the WBD Global Information and Content Security (GICS) teams by supporting the Security Engineering, Security Architecture, Threat Detection and Response, and other Security teams/functions through the deployment, management, and maintenance of shared, reliable, and extensible security platforms/systems. The Cybersecurity engineer plays a key role on the GICS security engineering team, ensuring that security best practices are followed and that tools and processes that support a secure platform are maintained and kept current. Ideal candidates will have a mixture of security and systems engineering backgrounds to ensure that business processes are configured correctly and that security best practices are designed and implemented." That seems substantive. Then "Your Role Accountabilities:" list bullet points (starting with •). We need to convert to

  • . The bullet points: - Plan, design, engineer and implement security-related technologies - Understanding technical security issues, their implications within WBD business units and able to effectively communicate them to management and other business leaders. - Configure, troubleshoot, and maintain security infrastructure – including software and hardware in cloud environments, as well as on-premises. - Conduct security audits and assessments to regularly determine the effectiveness of security platforms and identify areas of improvement. - Host and operating systems hardening, auditing, monitoring and logging with appropriate security controls and best practices while meeting security best practices and business goals. - Research and explore emerging security technologies and determine their appropriate use within the company. - Prepare, document, and create standard operating procedures and protocols. - Crosstrain and mentor other team members as needed. We need to preserve all. Then "Qualifications & Experiences:" list: - A minimum of 5+ years of hands-on experience in building, designing, and maintaining enterprise security tools - A minimum of 5+ years of hands-on experience in security engineering - 5+ years of successfully implementing advanced cyber security technology in a complex environment - Engineer and administer security platforms including SIEM/SOAR systems, endpoint detection and response, vulnerability management, anomaly detection, and cloud analysis. - Hands on technical experience with networking and computing system architectures, specifically, the security aspects thereof. - Must have 5+ Leveraging DevSecOps and secure architecture design principles to develop security capabilities. - Must have 5+ Linux system administration - Must have 5+ scripting experience (using Python or other equivalent languages) - Thorough understanding of information security principles, techniques, principles, policy frameworks, and best practices - Hands-on Experience in public cloud infrastructures like AWS (Amazon Web Services) - Hands on experience with Kubernetes and helm. - A minimum of 3+ Hands-on Experience with automation technologies (e.g., Ansible, Terraform, etc.) - Not Required but preferred experience: - Security and Cloud certifications are a plus. (CISSP, Splunk Admin, AWS Solution architect) - Hands on technical experience with compliance and regulatory frameworks and how they affect architecture designs and review. - AI Engineering or AI security. We need to keep all. Some lines have weird formatting like "Must have 5+ Leveraging DevSecOps..." maybe missing a word but we keep as is. Then "How We Get Things Done…" maybe not needed; it's about guiding principles, could be omitted as not a specific section? It's not a standard heading; we could ignore. Then EEO boilerplate to remove. Then compensation: "In compliance with local law, we are disclosing the compensation, or a range thereof, for roles in locations where legally required. Actual salaries will vary based on several factors, including but not limited to external market data, internal equity, location, skill set, experience, and/or performance. Base pay is just one component of Warner Bros. Discovery’s total compensation package for employees. Pay Range: $91,000.00 - $169,000.00 salary per year. Other rewards may include annual bonuses, short- and long-term incentives, and program-specific awards." Then benefits: "In addition, Warner Bros. Discovery provides a variety of benefits to employees, including health insurance coverage, an employee wellness program, life and disability insurance, a retirement savings plan, paid holidays and sick time and vacation." Hybrid model note: "*Must work a hybrid model (3 days onsite) out of our Silver Spring, DC, or Atlanta office.*" This is schedule/location. We need to output sections: About the role (maybe from "Your New Role:" paragraph). Responsibilities (list). Qualifications (list). Skills (maybe we can extract specific skills: Linux system administration, scripting (Python), networking, cloud AWS, Kubernetes, helm, automation (Ansible/Terraform), DevSecOps, SIEM/SOAR, endpoint detection, vulnerability management, anomaly detection, etc). But we already have qualifications list includes many skill-like items. The instruction says to prefer a few substantive sections over many thin ones. Could combine Qualifications and Skills? But they ask to use headings for those categories if content exists. We have qualifications content; we could also have Skills section pulling out specific technical skills from qualifications. However that may duplicate content. Better to have Qualifications section covering experience requirements, and Skills section covering specific technical competencies. But we must not invent or summarize away detail; we can extract from qualifications list. Let's decide: We'll have sections: - About the role (paragraph from "Your New Role:"). - Responsibilities (list from "Your Role Accountabilities:"). - Qualifications (list of experience requirements: years of experience, etc). - Skills (list of specific technical skills: Linux system administration, scripting (Python), networking, cloud AWS, Kubernetes, helm, automation (Ansible/Terraform), DevSecOps, SIEM/SOAR, endpoint detection, vulnerability management, anomaly detection, etc). We'll need to ensure we don't lose any info; we can keep the qualifications list as is and maybe not have Skills separate to avoid duplication. But the instruction says use headings for those categories if content exists. It doesn't forbid having both Qualifications and Skills; but we should avoid thin sections. If we put all qualification items under Qualifications, we can still have Skills empty? Better to not create Skills if we don't have distinct content beyond qualifications. However the qualifications list includes many skill-like items; we could treat them as qualifications. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not mandatory to use all. We should include a section only when posting has real, specific content for it. So we need to decide if we have distinct content for Skills beyond qualifications. The qualifications list includes items like "Hands on technical experience with networking and computing system architectures", "Hands-on Experience in public cloud infrastructures like AWS", "Hands on experience with Kubernetes and helm.", "A minimum of 3+ Hands-on Experience with automation technologies (e.g., Ansible, Terraform, etc.)", "Must have 5+ Leveraging DevSecOps and secure architecture design principles", "Must have 5+ Linux system administration", "Must have 5+ scripting experience (using Python or other equivalent languages)". Those are skills. So we could put those under Skills, and keep years-of-experience requirements under Qualifications. But the qualifications list also includes "A minimum of 5+ years of hands-on experience in building, designing, and maintaining enterprise security tools", etc. Those are experience requirements. Thus we can split: Qualifications: years of experience requirements. Skills: specific technical skills. Let's extract years-of-experience lines: - A minimum of 5+ years of hands-on experience in building, designing, and maintaining enterprise security tools - A minimum of 5+ years of hands-on experience in security engineering - 5+ years of successfully implementing advanced cyber security technology in a complex environment Maybe also "Engineer and administer security platforms including SIEM/SOAR systems, endpoint detection and response, vulnerability management, anomaly detection, and cloud analysis." That's more skill/experience. But we can keep that under Skills. Let's decide: Qualifications section: list of the three bullet points about years of experience. Skills section: list of specific technical competencies: - Engineer and administer security platforms including SIEM/SOAR systems, endpoint detection and response, vulnerability management, anomaly detection, and cloud analysis. - Hands on technical experience with networking and computing system architectures, specifically, the security aspects thereof. - Must have 5+ Leveraging DevSecOps and secure architecture design principles to develop security capabilities. - Must have 5+ Linux system administration - Must have 5+ scripting experience (using Python or other equivalent languages) - Thorough understanding of information security principles, techniques, principles, policy frameworks, and best practices - Hands-on Experience in public cloud infrastructures like AWS (Amazon Web Services) - Hands on experience with Kubernetes and helm. - A minimum of 3+ Hands-on Experience with automation technologies (e.g., Ansible, Terraform, etc.) - Not Required but preferred experience: - Security and Cloud certifications are a plus. (CISSP, Splunk Admin, AWS Solution architect) - Hands on technical experience with compliance and regulatory frameworks and how they affect architecture designs and review. - AI Engineering or AI security. We need