Network Security Engineer II

We need to output HTML fragment with sections: About the role? The posting includes description: "When you join Verizon..." etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, legal, application instructions, etc. Keep substantive info. We need to parse content: - Intro paragraph about Verizon culture: "When you join Verizon You want more out of a career..." This is about the role/company. Could be "About the role" or maybe "About Verizon". Use "About the role" heading. - Then "What You’ll Be Doing..." is responsibilities. So Responsibilities section with bullet list. - Then "What We’re Looking For..." includes must have and even better if you also have... That's qualifications/requirements/skills. We need to decide sections: Requirements, Qualifications, Skills. The instruction: Use headings for those categories if content exists. We can split: Requirements (must have), Qualifications (maybe education/experience), Skills (certifications, technical). But we need to avoid thin sections. Perhaps combine into Requirements and Skills. However we must follow instruction: Use headings for those categories if content exists. We can include Requirements (must have), Qualifications (education/experience), Skills (certifications, technical). But ensure each has substantive content. Let's extract: Must have: - Bachelor’s degree or one or more years of relevant work experience. - One or more years of relevant work experience, demonstrated through one or a combination of work and/or military experience, or specialized training. - Knowledge of incident response lifecycles (NIST or SANS) and experience with automation playbooks using SOAR platforms to automate triage and response actions. - Experience with risk-based alerting, managing notable events, asset/identity correlation, and defining/tuning correlation searches. - Ability to work both independently and in collaboration with cross-functional teams. - Strong analytical skills and attention to detail Even better if you also have… (list many): - Security certifications such as CompTIA Security+, CISSP, CCIP, CISM, CCSP, OSCP, Ethical Hacking (CEH, OSCP). - Experience with Splunk SPL (Search Processing Language) searches, including macros, data models, and lookups for efficient threat hunting and investigation. - Experience with Identity and Access Management (IAM) solutions. - Ability to build consensus and a common understanding of security objectives, goals, and execution steps. - Experience with network protocols and information security with networking certifications such as PCNSE, CCNP or CCNA. - Experience with networks, 4G/5G wireless network functions or virtualization technologies like Openstack and Kubernetes. - Experience with scripting languages like Python and/or automation tools like Ansible. - Experience in UNIX or Linux systems engineering expertise with a variety of variants. - Experience with encryption for data in transit (e.g., IPsec, or TLS) and at rest. - Effective written, interpersonal, and verbal communication skills. Also later: "Where you’ll be working In this hybrid role, you'll have a defined work location that includes working from home and a minimum of three days per week in the office, which will be set by your manager. Employees are responsible for maintaining compliance with hybrid work policies." That's schedule/hybrid info. Also "Scheduled Weekly Hours 40". So we have schedule info: hybrid, min 3 days office, 40 hours weekly. So we can create Schedule section. Benefits: "Benefits And Compensation" section includes benefits description. Also compensation/salary range: $72,000 - $129,000. So we need Benefits and Pay sections. According to instruction: include Pay and Schedule sections only if posting actually states them. Yes we have salary range and schedule. So include Pay and Schedule. Benefits: list of benefits: medical, dental, vision, short and long term disability, basic life insurance, supplemental life insurance, AD&D insurance, identity theft protection, pet insurance and group home & auto insurance. matched 401(k) savings plan, up to 8 company paid holidays per year and up to 6 personal days per year, paid parental leave, adoption assistance and tuition assistance, plus other incentives. Also mention premium pay etc. We'll keep substantive. Pay: salary range $72,000 - $129,000. Also mention incentive based position, potential to earn more, premium pay etc. We'll include that. Schedule: hybrid role, defined work location includes working from home and minimum of three days per week in office, set by manager. Employees responsible for maintaining compliance with hybrid work policies. Scheduled Weekly Hours 40. Now About the role: we can use the introductory paragraph about Verizon culture and mission. Could also include "The GN&T Network Security team is looking for a highly motivated and experienced Cybersecurity Engineer..." but that's more about role. Actually "What You’ll Be Doing..." is responsibilities. So About the role could be the initial paragraph about Verizon and the VTeamLife. Let's use that. Now we need to output HTML fragment only, no /. Use

for each section heading. Use

• for lists. Use

  for prose. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, legal, application instructions, etc. Also remove "Equal Employment Opportunity" etc. Also remove "If Verizon and this role sound like a fit for you, we encourage you to apply even if you don’t meet every “even better” qualification listed above." That's application encouragement, maybe considered boilerplate? It's not exactly legal but it's encouraging to apply. The instruction says remove application instructions. This line is encouraging to apply, maybe considered application instruction. Safer to remove it. Also remove "Where you’ll be working" we kept as schedule. Good. Now structure:

  About the role

  When you join Verizon You want more out of a career. A place to share your ideas freely — even if they’re daring or different. Where the true you can learn, grow, and thrive. At Verizon, we power and empower how people live, work and play by connecting them to what brings them joy. We do what we love — driving innovation, creativity, and impact in the world. Our V Team is a community of people who anticipate, lead, and believe that listening is where learning begins. In crisis and in celebration, we come together — lifting our communities and building trust in how we show up, everywhere & always. Want in? Join the #VTeamLife.

  Responsibilities

  • The GN&T Network Security team is looking for a highly motivated and experienced Cybersecurity Engineer to join the Network Security Defense team.
  • The Defense teams are responsible for owning the security lifecycle and effectiveness across the Core, Edge, and Access networks, as well as all systems and network functions within GN&T.
  • In this role, you will be critical in advancing our security posture through real-time Threat Monitoring & Detection using SIEM tools like Splunk, leading Incident Response efforts during a breach, and managing the continuous Vulnerability Management lifecycle across networks and applications.
  • The position also requires expertise in defining and implementing robust Security Architecture, including firewalls, encryption, centralized Identity and Access Management, and Multi-Factor Authentication (MFA).
  • A strong candidate will also possess advanced Threat Hunting skills, including Advanced Networking & Protocol Analysis, Endpoint & Memory Forensics, Data Science & Querying, and demonstrable experience in Automation & Scripting to enhance our Cybersecurity tooling.
  • Maintain formal guidelines, policies, and procedures to ensure smooth and error-free operations.
  • Support our partners across the Operations, Engineering, and Planning organizations to ensure secure design patterns are embedded into new deployments and major changes.
  • Work with lead engineers on strategic technical challenges.
  • Communicate clearly and effectively, articulate complex technical concepts to diverse internal and external audiences.
  • Support network security incident response activities, including triage, containment, eradication, and recovery for disruptive threats.
  • Serve as a support engineer for security-related investigations, providing analysis and input during active incidents.
  • Support root cause analysis and produce clear incident reports outlining timeline, impact, evidence, and remediation recommendations.
  • Explore proactive threat hunting across the identity, endpoint, and network telemetry to uncover adversary behavior and reduce dwell time.
  • Conduct threat detections using SIEM (Security Information and Event Management) to improve alert fidelity and reduce false positives.
  • Work on continuous improvement of network visibility and telemetry collection to strengthen detection and response capabilities.
  • Perform regular security control assessments, validating configuration effectiveness, and closing gaps discovered during incidents or hunts.
  But note the first bullet duplicates the intro sentence about looking for engineer; maybe we can keep but it's okay. Now Requirements (must have):

  Requirements

  • Bachelor’s degree or one or more years of relevant work experience.
  • One or more years of relevant work experience, demonstrated through one or a combination of work and/or military experience, or specialized training.
  • Knowledge of incident response lifecycles (NIST or SANS) and experience with automation playbooks using SOAR platforms to automate triage and response actions.
  • Experience with risk-based alerting, managing notable events, asset/identity correlation, and defining/tuning correlation searches.
  • Ability to work both independently and in collaboration with cross-functional teams.
  • Strong analytical skills and attention to detail.
  Qualifications (education/experience) maybe redundant with Requirements. Could combine but we need to decide. Perhaps we treat Requirements as must-have, Qualifications as education/experience (but we already have that). Could instead have Qualifications for certifications etc. But we have Skills for technical. Let's think: The instruction says use headings for those categories if content exists. It doesn't require us to use all; we can choose which to include. To avoid thin sections, we could combine Requirements and Qualifications into one section called Requirements (or Qualifications). But we need to follow the heading names exactly? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we can use those headings if we have content. It doesn't forbid using only some. So we can choose to use Requirements and Skills, and maybe Benefits, Pay, Schedule. Qualifications could be omitted if we think it's thin. However we have education/experience content; we could put that under Requirements. Then Skills can contain certifications, technical skills, etc. That seems reasonable. Thus:

  Requirements

  (includes education/experience, must-have)

  Skills

  (includes certifications, technical skills, etc.) Now Benefits:

  Benefits

  • Medical, dental, vision, short and long term disability, basic life insurance, supplemental life insurance, AD&D insurance, identity theft protection, pet insurance and group home & auto insurance.
  • Matched 401(k) savings plan.
  • Up to 8 company paid holidays per year and up to 6 personal days per year.
  • Paid parental leave, adoption assistance and tuition assistance.
  • Other incentives as part of award‑winning total rewards package.
  • Depending on the role, employees may receive premium pay such as overtime, shift differential, holiday pay, allowances, etc.
  • Newly hired employees receive up to 15 days of vacation per year, which grows with additional service.
  • For part‑timers, coverage varies based on