Principal Red Team Operator

We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about Verizon culture, then description of role. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. We need to preserve all substantive info. Let's parse content: Intro: "When you join Verizon You want more out of a career..." This is about company culture. Could be "About the role"? Actually "About the role" maybe includes description of role and company. The intro is more about Verizon culture. Could fit under "About the role" or maybe we can have "About the role" covering role description and company context. Then: "As an experienced Red Team Operator..." description of role responsibilities. That could go under Responsibilities. Then bullet list: Key Responsibilities with items: Adversary Emulation, Vulnerability Exploitation, Post-Engagement Reporting, Collaboration, Threat Intelligence, Continuous Improvement. Then "***This role can be located in any US based Verizon hub location.***" That's location info; maybe schedule? Not schedule. Could be part of About the role? Might be omitted as minor metadata? It's location; maybe we can put in a short p under About the role. Then "What we’re looking for... You’ll Need To Have ..." That's requirements/qualifications. List: Bachelor’s degree or four or more years of work experience. Six or more years of relevant experience required... Strong understanding of 4G/5G protocols... etc. Then "Even better if you have one or more of the following:" list of preferred qualifications. Then "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 encouragement; could be part of Requirements. Then "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. So we can have Schedule section. Then "Scheduled Weekly Hours 40" That's schedule detail. Then "Equal Employment Opportunity Verizon is an equal opportunity employer..." That's boilerplate EEO; remove. Then "Benefits And Compensation Our benefits are designed..." That's benefits section. Include details: health and wellness, 401(k), holidays, personal days, parental leave, etc. Also mention compensation: premium pay, overtime, etc. Salary range: $120,500 - $231,000. Also mention part-time adjustments. Thus we need sections: About the role (intro + role description + location?), Responsibilities (key responsibilities), Requirements (basic qualifications), Qualifications (maybe "Even better if you have..."), Skills (maybe combine with qualifications? But we have separate headings: Requirements, Qualifications, Skills. We need to decide what goes where. The posting includes "You’ll Need To Have" (basic requirements) and "Even better if you have one or more of the following:" (preferred qualifications). Also there is list of skills: Strong Linux skills, Strong coding and scripting skills, etc. Those could go under Skills. Thus we can map: - About the role: company culture intro + role overview + location note. - Responsibilities: the Key Responsibilities list. - Requirements: Bachelor’s degree or four or more years work experience; Six or more years relevant experience; Strong understanding of 4G/5G protocols and interfaces; Strong understanding of 4G/5G core network architecture; etc. (these are required). Also maybe "Strong understanding of network equipment and networking protocols is required." That's from earlier. - Qualifications: the "Even better if you have one or more of the following:" list (degree in engineering, cyber security or computer science; Knowledge of 3GPP standards; Industry Knowledge: Strong foundational knowledge in enterprise networking technologies and protocols; Strong Linux skills; Strong coding and scripting skills; Ability to vet exploit code; Knowledge of network architecture and cloud environments; Problem Solving: Ability to think like an attacker; Soft Skills: Strong communication and teamwork skills; Certifications such as OSCP...; Familiarity with security challenges...). Some of those overlap with skills; but we can still put them under Qualifications. - Skills: maybe we can extract specific skill items: Strong Linux skills, Strong coding and scripting skills (Python, Bash, PowerShell), Ability to vet exploit code, Knowledge of network architecture and cloud environments (Kubernetes, OpenStack, OpenShift), Problem solving (think like attacker), Soft skills (communication, teamwork), Certifications (OSCP etc). But we already have many in Qualifications. To avoid duplication, we could treat Qualifications as the "Even better" list, and Skills as the specific technical skills (Linux, coding, cloud, etc). However the posting lumps many together. We need to follow instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But we have headings defined; we can include only those with real content. Could include Requirements and Qualifications both, but ensure not thin. We could make: - About the role - Responsibilities - Requirements (includes basic qualifications) - Skills (includes technical skills, certifications, soft skills) - Benefits - Pay (salary range) - Schedule (hybrid, weekly hours) We might omit Qualifications if we merge into Requirements or Skills. But we need to follow headings list; we can omit sections if no real specific content. The posting does have "Even better if you have one or more of the following:" which is qualifications. So we could have a Qualifications section for that. Thus we have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now craft HTML. We'll need

About the role

then

...

possibly multiple paragraphs. We need to preserve all substantive info; not invent or summarize away detail. So we need to keep specifics like list items exactly. We'll need to use

• for any list of duties/requirements/benefits. Thus: About the role: include intro paragraphs about Verizon culture, role description, location note. We can split into multiple

  elements. Responsibilities:

  Responsibilities

  then
  with each responsibility. Requirements:

  Requirements

  then
  with each requirement. Qualifications:

  Qualifications

  then
  with each "even better" item. Skills:

  Skills

  then
  with skill items (Linux, coding/scripting, exploit code vetting, cloud/network architecture, problem solving, communication/teamwork, certifications, familiarity with security challenges). Might be overlapping with Qualifications but okay. Benefits:

  Benefits

  then
  with benefit items. Pay:

  Pay

  then

  with salary range and note about premium pay etc. Schedule:

  Schedule

  then

  with hybrid details and weekly hours. We must not include boilerplate like EEO. Now let's extract exact text. Intro: "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." We need to keep punctuation and spacing. We'll combine into a paragraph. Then role description: "As an experienced Red Team Operator in the telecommunications industry, you will play a critical role in proactively identifying vulnerabilities and security gaps within Verizon’s infrastructure, applications, and processes. This role focuses on emulating real-world adversarial techniques to evaluate and improve Verizon’s defensive capabilities, ensuring the security of customer data and network infrastructure. You will collaborate closely with internal teams to simulate advanced persistent threats (APTs) and execute red team engagements tailored to the unique challenges of the telecommunications sector. This position requires a deep understanding of telco-specific systems, such as enterprise-scale complex networks, 4G & 5G wireless network infrastructure, cloud technology, and more. Strong understanding of network equipment and networking protocols is required. With the right mindset, this is a great opportunity to leverage deep mobile network experience to shift into an offensive cybersecurity role." We can put that in About the role after intro. Location note: "***This role can be located in any US based Verizon hub location.***" We'll include as a short p. Now Responsibilities list: - Adversary Emulation: Conduct red team exercises that emulate realistic threats targeting telco-specific systems, including wireline/wireless network infrastructure and supporting systems. - Vulnerability Exploitation: Identify, exploit, and report vulnerabilities in critical telco systems and infrastructure - Post-Engagement Reporting: Deliver comprehensive technical reports and executive summaries that outline findings, exploit paths, and remediation recommendations - Collaboration: Work closely with blue team to develop detection and prevention strategies informed by red team exercises - Threat Intelligence: Stay updated on the latest attack techniques, tactics, and procedures (TTPs) relevant to the telecommunications industry - Continuous Improvement: Provide insights to enhance the organization’s security posture through collaboration with peers in both security and operations. We'll keep exactly. Now Requirements: - Bachelor’s degree or four or more years of work experience. - Six or more years of relevant experience required, demonstrated through one or a combination of work and/or military experience, or specialized training. - Strong understanding of 4G/5G protocols and interfaces to include GTP, Diameter, SS7, S1-MME, S1-U, and S11, HTTP/2 Service-Based Architecture - Strong understanding of 4G/5G core network architecture, and supporting systems. - Strong understanding of network equipment and networking protocols is required. (maybe duplicate; we can include once.) We could combine the last as part of earlier but keep. Now Qualifications (even better): - A degree in engineering, cyber security or computer science. - Knowledge of 3GPP standards relevant to EPC, 4GCore, 5GSA, 5GCore, and 5G/ LTE radio access, VoLTE/VoNR - Industry Knowledge: Strong foundational knowledge in enterprise networking technologies and protocols (routers, switches, VPN, load balancers, TCP/IP, Internet numbering – IP, ASN, CIDR, subnetting, etc) - Strong Linux skills - Strong coding and scripting skills (Python, Bash, PowerShell, etc.) - Ability to vet exploit code to understand what it does. - Knowledge of network architecture and cloud environments (e.g., Kubernetes, OpenStack, OpenShift) - Problem Solving: Ability to think like an attacker and devise innovative attack scenarios targeting telco environments - Soft Skills: Strong communication and teamwork skills, with the ability to effectively interact with technical and non-technical stakeholders - Certifications such as OSCP, OSCE, or OSEP or GIAC certifications like GPEN, GXPN, or GWAPT - Familiarity with security challenges in running Internet-scale networks, wireless core components, cloud, and edge computing Now Skills