Security Engineer
Verizon · Irving, TX · 3 wk ago
Information Technology$72k–$129k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about Verizon culture. Could be "About the role" or maybe "About Verizon"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We have content for: About the role (intro about Verizon and team). Responsibilities (list). Requirements (maybe "What We're Looking For" includes qualifications). Could split into Requirements and Qualifications? The posting includes "What We're Looking For" with bullet list of qualifications. Could treat as Requirements. Also there is "Where you'll be working" (remote) and "Scheduled Weekly Hours 40" which is schedule. Also "Benefits And Compensation" includes benefits and pay range. So we can have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly Skills? The qualifications include skills but we can incorporate into Requirements. Avoid duplicate.
We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, etc. Also remove application instructions (like "If this role sounds like a fit...").
We need to preserve all substantive info. Let's extract.
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."
That's about Verizon culture. Could be "About the role" or "About Verizon". We'll use About the role.
Next: "What You'll Be Doing Our Dynamic Application Security Testing (DAST) team is a group of talented, creative thinkers who 'act like the enemy.' We focus on ensuring our web applications, mobile applications, and APIs are secure by performing ethical hacking and penetration testing on Verizon's internal and external defenses. In this role, you will operate at the intersection of cybersecurity and automation. You won't just find vulnerabilities; you will build, maintain, and support the suite of tools and automated processes that empower our application teams to independently scan for, identify, and remediate OWASP Top 10 vulnerabilities. Additionally, you will leverage your offensive security skills to support Verizon’s critical incident response and bug bounty programs."
That's description of role; could be part of About the role or separate. But we already have About the role; we could include this as part of About the role. However we also have a separate Responsibilities section later. So maybe we keep About the role as intro + role description. Then Responsibilities list.
Responsibilities list bullet points:
- Integrating dynamic analysis tools (OWASP ZAP, Burp Suite) directly into Jenkins and GitLab CI/CD pipelines to ensure continuous security testing.
- Writing and maintaining custom automation scripts using Python, Java, and Bash to scale our security efforts and eliminate manual bottlenecks.
- Utilizing AI to build new testing capabilities, streamline the triage of bug bounty submissions, and troubleshoot code across our tech stack.
- Deploying, hosting, and maintaining containerized security testing environments using Docker and AWS.
- Partnering with engineering teams to guide them through identifying and remediating OWASP Top 10 vulnerabilities.
- Leveraging your offensive expertise to triage incoming bug bounty submissions and support Verizon’s critical incident response efforts.
- Performing ethical hacking and penetration testing against web applications, mobile apps, and APIs to uncover vulnerabilities before malicious actors do.
Now Requirements/Qualifications: "What We're Looking For You'll need to have: Bachelor’s degree or one or more years of work experience. Even better if you have one or more of the following : 2+ years of hands-on experience in Application Security, Penetration Testing, or a DevSecOps engineering role. Deep understanding of web application architecture, APIs (REST/GraphQL), and mobile application security. Comprehensive knowledge of the OWASP Top 10, CWEs, CVSS scoring, and how to manually validate and exploit these vulnerabilities. Proficiency operating and configuring industry-standard dynamic analysis tools, specifically Burp Suite Professional and OWASP ZAP. Proven experience integrating security tools into modern CI/CD pipelines using Jenkins and GitLab CI. Strong ability to read, write, and maintain automation scripts in Python and Bash. Hands-on experience working with Docker containers and deploying/managing applications in AWS (experience with EC2s/Linux is a plus). Ability to clearly explain complex security vulnerabilities (and why remediating them is important) to software engineers who may not have a security background. Experience using AI assistants (ideally Gemini or Claude Code) for scripting, debugging code, or day to day productivity improvements."
We can treat as Requirements (maybe also Qualifications). We'll output a single section Requirements with list.
Next: "Where you’ll be working In this remote role, you'll work from home with occasional in-person trainings and meetings." That's location/remote. Could be part of About the role or separate. But we have Schedule section for weekly hours. We'll create a Schedule section: "Scheduled Weekly Hours 40". Also location remote could be in About the role or a separate "Work Location" but not in allowed headings. Since only allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We don't have Work Location. Could fold location into About the role or Schedule? Probably About the role can include remote work description. We'll add that to About the role.
Next: Benefits And Compensation section includes benefits list and pay range. We'll split into Benefits and Pay sections.
Benefits list: medical, dental, vision, short and long term disability, basic life insurance, supplemental life insurance, AD&D 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 "Depending on the role, employees have the opportunity to receive compensation in the form of premium pay such as overtime, shift differential, holiday pay, allowances, etc." That's more about pay. Also "Newly hired employees receive up to 15 days of vacation per year, which grows with additional service. For part-timers, your coverage will vary as you may be eligible for some of these benefits depending on your individual circumstances." That's benefits.
Pay: "The salary will vary depending on your location and confirmed job-related skills and experience. This is an incentive based position with the potential to earn more. For part-time roles, your compensation will be adjusted to reflect your hours. The annual salary range for the location(s) listed on this job requisition based on a full-time schedule is: $72,000.00 - $129,000.00."
We need to include Pay section only if posting states them. Yes, salary range given. So we will include Pay with that range.
Schedule: "Scheduled Weekly Hours 40". Also mention remote occasional in-person trainings. We'll include schedule with 40 hours per week.
Now ensure we don't include boilerplate: EEO, equal opportunity, etc. Remove lines about "Equal Employment Opportunity Verizon is an equal opportunity employer..." etc. Also remove "If this role sounds 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 instruction; remove.
Also remove "Want in? Join the #VTeamLife." maybe keep as part of About the role? It's a call to action but not boilerplate; it's substantive? Might be considered marketing but okay to keep. However it's like a tagline; we can keep.
Now produce HTML fragment with
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We have content for: About the role (intro about Verizon and team). Responsibilities (list). Requirements (maybe "What We're Looking For" includes qualifications). Could split into Requirements and Qualifications? The posting includes "What We're Looking For" with bullet list of qualifications. Could treat as Requirements. Also there is "Where you'll be working" (remote) and "Scheduled Weekly Hours 40" which is schedule. Also "Benefits And Compensation" includes benefits and pay range. So we can have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly Skills? The qualifications include skills but we can incorporate into Requirements. Avoid duplicate.
We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, etc. Also remove application instructions (like "If this role sounds like a fit...").
We need to preserve all substantive info. Let's extract.
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."
That's about Verizon culture. Could be "About the role" or "About Verizon". We'll use About the role.
Next: "What You'll Be Doing Our Dynamic Application Security Testing (DAST) team is a group of talented, creative thinkers who 'act like the enemy.' We focus on ensuring our web applications, mobile applications, and APIs are secure by performing ethical hacking and penetration testing on Verizon's internal and external defenses. In this role, you will operate at the intersection of cybersecurity and automation. You won't just find vulnerabilities; you will build, maintain, and support the suite of tools and automated processes that empower our application teams to independently scan for, identify, and remediate OWASP Top 10 vulnerabilities. Additionally, you will leverage your offensive security skills to support Verizon’s critical incident response and bug bounty programs."
That's description of role; could be part of About the role or separate. But we already have About the role; we could include this as part of About the role. However we also have a separate Responsibilities section later. So maybe we keep About the role as intro + role description. Then Responsibilities list.
Responsibilities list bullet points:
- Integrating dynamic analysis tools (OWASP ZAP, Burp Suite) directly into Jenkins and GitLab CI/CD pipelines to ensure continuous security testing.
- Writing and maintaining custom automation scripts using Python, Java, and Bash to scale our security efforts and eliminate manual bottlenecks.
- Utilizing AI to build new testing capabilities, streamline the triage of bug bounty submissions, and troubleshoot code across our tech stack.
- Deploying, hosting, and maintaining containerized security testing environments using Docker and AWS.
- Partnering with engineering teams to guide them through identifying and remediating OWASP Top 10 vulnerabilities.
- Leveraging your offensive expertise to triage incoming bug bounty submissions and support Verizon’s critical incident response efforts.
- Performing ethical hacking and penetration testing against web applications, mobile apps, and APIs to uncover vulnerabilities before malicious actors do.
Now Requirements/Qualifications: "What We're Looking For You'll need to have: Bachelor’s degree or one or more years of work experience. Even better if you have one or more of the following : 2+ years of hands-on experience in Application Security, Penetration Testing, or a DevSecOps engineering role. Deep understanding of web application architecture, APIs (REST/GraphQL), and mobile application security. Comprehensive knowledge of the OWASP Top 10, CWEs, CVSS scoring, and how to manually validate and exploit these vulnerabilities. Proficiency operating and configuring industry-standard dynamic analysis tools, specifically Burp Suite Professional and OWASP ZAP. Proven experience integrating security tools into modern CI/CD pipelines using Jenkins and GitLab CI. Strong ability to read, write, and maintain automation scripts in Python and Bash. Hands-on experience working with Docker containers and deploying/managing applications in AWS (experience with EC2s/Linux is a plus). Ability to clearly explain complex security vulnerabilities (and why remediating them is important) to software engineers who may not have a security background. Experience using AI assistants (ideally Gemini or Claude Code) for scripting, debugging code, or day to day productivity improvements."
We can treat as Requirements (maybe also Qualifications). We'll output a single section Requirements with list.
Next: "Where you’ll be working In this remote role, you'll work from home with occasional in-person trainings and meetings." That's location/remote. Could be part of About the role or separate. But we have Schedule section for weekly hours. We'll create a Schedule section: "Scheduled Weekly Hours 40". Also location remote could be in About the role or a separate "Work Location" but not in allowed headings. Since only allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We don't have Work Location. Could fold location into About the role or Schedule? Probably About the role can include remote work description. We'll add that to About the role.
Next: Benefits And Compensation section includes benefits list and pay range. We'll split into Benefits and Pay sections.
Benefits list: medical, dental, vision, short and long term disability, basic life insurance, supplemental life insurance, AD&D 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 "Depending on the role, employees have the opportunity to receive compensation in the form of premium pay such as overtime, shift differential, holiday pay, allowances, etc." That's more about pay. Also "Newly hired employees receive up to 15 days of vacation per year, which grows with additional service. For part-timers, your coverage will vary as you may be eligible for some of these benefits depending on your individual circumstances." That's benefits.
Pay: "The salary will vary depending on your location and confirmed job-related skills and experience. This is an incentive based position with the potential to earn more. For part-time roles, your compensation will be adjusted to reflect your hours. The annual salary range for the location(s) listed on this job requisition based on a full-time schedule is: $72,000.00 - $129,000.00."
We need to include Pay section only if posting states them. Yes, salary range given. So we will include Pay with that range.
Schedule: "Scheduled Weekly Hours 40". Also mention remote occasional in-person trainings. We'll include schedule with 40 hours per week.
Now ensure we don't include boilerplate: EEO, equal opportunity, etc. Remove lines about "Equal Employment Opportunity Verizon is an equal opportunity employer..." etc. Also remove "If this role sounds 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 instruction; remove.
Also remove "Want in? Join the #VTeamLife." maybe keep as part of About the role? It's a call to action but not boilerplate; it's substantive? Might be considered marketing but okay to keep. However it's like a tagline; we can keep.
Now produce HTML fragment with headings and - for lists,
for prose.
We need to avoid repeating job title as heading. Not using.
Let's craft:
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. Our Dynamic Application Security Testing (DAST) team is a group of talented, creative thinkers who 'act like the enemy.' We focus on ensuring our web applications, mobile applications, and APIs are secure by performing ethical hacking and penetration testing on Verizon's internal and external defenses. In this role, you will operate at the intersection of cybersecurity and automation. You won't just find vulnerabilities; you will build, maintain, and support the suite of tools and automated processes that empower our application teams to independently scan for, identify, and remediate OWASP Top 10 vulnerabilities. Additionally, you will leverage your offensive security skills to support Verizon’s critical incident response and bug bounty programs. This is a remote role with occasional in‑person trainings and meetings.
Responsibilities
- Integrating dynamic analysis tools (OWASP ZAP, Burp Suite) directly into Jenkins and GitLab CI/CD pipelines to ensure continuous security testing.
- Writing and maintaining custom automation scripts using Python, Java, and Bash to scale our security efforts and eliminate manual bottlenecks.
- Utilizing AI to build new testing capabilities, streamline the triage of bug bounty submissions, and troubleshoot code across our tech stack.
- Deploying, hosting, and maintaining containerized security testing environments using Docker and AWS.
- Partnering with engineering teams to guide them through identifying and remediating OWASP Top 10 vulnerabilities.
- Leveraging your offensive expertise to triage incoming bug bounty submissions and support Verizon’s critical incident response efforts.
- Performing ethical hacking and penetration testing against web applications, mobile apps, and APIs to uncover vulnerabilities before malicious actors do.
Requirements
- Bachelor’s degree or one or more years of work experience.
- 2+ years of hands‑on experience in Application Security, Penetration Testing, or a DevSecOps engineering role (preferred).
- Deep understanding of web application architecture, APIs (REST/GraphQL), and mobile application security.
- Comprehensive knowledge of the OWASP Top 10, CWEs, CVSS scoring, and how to manually validate and exploit these vulnerabilities.
- Proficiency operating and configuring industry‑standard dynamic analysis tools, specifically Burp Suite Professional and OWASP ZAP.
- Proven experience integrating security tools into modern CI/CD pipelines using Jenkins and GitLab CI.
- Strong ability to read, write, and maintain automation scripts in Python and Bash.
- Hands‑on experience working with Docker containers and deploying/managing applications in AWS (experience with EC2s/Linux is a plus).
- Ability to clearly explain complex security vulnerabilities (and why remediating them is important) to software engineers who may not have a security background.
- Experience using AI assistants (ideally Gemini or Claude
- for lists,
for prose. We need to avoid repeating job title as heading. Not using. Let's craft:
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. Our Dynamic Application Security Testing (DAST) team is a group of talented, creative thinkers who 'act like the enemy.' We focus on ensuring our web applications, mobile applications, and APIs are secure by performing ethical hacking and penetration testing on Verizon's internal and external defenses. In this role, you will operate at the intersection of cybersecurity and automation. You won't just find vulnerabilities; you will build, maintain, and support the suite of tools and automated processes that empower our application teams to independently scan for, identify, and remediate OWASP Top 10 vulnerabilities. Additionally, you will leverage your offensive security skills to support Verizon’s critical incident response and bug bounty programs. This is a remote role with occasional in‑person trainings and meetings.
Responsibilities
- Integrating dynamic analysis tools (OWASP ZAP, Burp Suite) directly into Jenkins and GitLab CI/CD pipelines to ensure continuous security testing.
- Writing and maintaining custom automation scripts using Python, Java, and Bash to scale our security efforts and eliminate manual bottlenecks.
- Utilizing AI to build new testing capabilities, streamline the triage of bug bounty submissions, and troubleshoot code across our tech stack.
- Deploying, hosting, and maintaining containerized security testing environments using Docker and AWS.
- Partnering with engineering teams to guide them through identifying and remediating OWASP Top 10 vulnerabilities.
- Leveraging your offensive expertise to triage incoming bug bounty submissions and support Verizon’s critical incident response efforts.
- Performing ethical hacking and penetration testing against web applications, mobile apps, and APIs to uncover vulnerabilities before malicious actors do.
Requirements
- Bachelor’s degree or one or more years of work experience.
- 2+ years of hands‑on experience in Application Security, Penetration Testing, or a DevSecOps engineering role (preferred).
- Deep understanding of web application architecture, APIs (REST/GraphQL), and mobile application security.
- Comprehensive knowledge of the OWASP Top 10, CWEs, CVSS scoring, and how to manually validate and exploit these vulnerabilities.
- Proficiency operating and configuring industry‑standard dynamic analysis tools, specifically Burp Suite Professional and OWASP ZAP.
- Proven experience integrating security tools into modern CI/CD pipelines using Jenkins and GitLab CI.
- Strong ability to read, write, and maintain automation scripts in Python and Bash.
- Hands‑on experience working with Docker containers and deploying/managing applications in AWS (experience with EC2s/Linux is a plus).
- Ability to clearly explain complex security vulnerabilities (and why remediating them is important) to software engineers who may not have a security background.
- Experience using AI assistants (ideally Gemini or Claude