Cybersecurity Platform and Identity Security Engineer

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.

You’ll be a senior individual contributor on a platform team that builds and secures the internal microservices powering enterprise identity operations at Verizon - Active Directory management, access provisioning, privileged account lifecycle, and the services that tie it all together.

You won’t just be handed tickets. You’ll own services, investigate problems from first principles, and ship solutions that hold up under scrutiny from both an engineering and a security lens. Responsibilities may include:

• Build and maintain microservices within a shared .NET framework (Micro.Framework, Shared Services, Web Tools).

• Implement feature work, bug fixes, and platform upgrades across a large service fleet - async pattern improvements, framework version migrations, NuGet dependency updates.

• Contribute to breaking-change analysis when shared libraries evolve: understand downstream impact, validate that consumer contracts hold.

• Build and maintain SCIM provisioning integrations that automate identity lifecycle events (create, update, deprovision) across enterprise systems.

• Develop and manage API proxies, policies, Automation, and traffic management in Apigee for services exposed internally and externally.

• Implement security remediations identified through assessment, spanning application-layer vulnerabilities and security configuration hardening.

• Apply cloud-native secrets management patterns:
  Key Vault integration, Managed Identity, encrypted connections, and proper JWT validation.

• Write secure code by default - parameterized queries, input validation at system boundaries, least-privilege service accounts.

• Participate in white-box security reviews of internal services - reading code with an attacker's eye, identifying common application-layer vulnerabilities.

• Document findings with enough specificity to be actionable: file paths, line numbers, CVSS context, reproduction steps.

• Translate security findings into working code fixes, not just recommendations.

• Use AI coding assistants actively in your daily workflow - for large refactors, codebase comprehension, documentation, and repetitive pattern application across multiple services.

• Know where AI output needs validation and when to course-correct.

You’ve built enough software to have opinions about what breaks in production, and you’ve been around enough security incidents (or near-misses) to take credential hygiene seriously without being told twice. You can read unfamiliar code and quickly build a mental model of what it does, what it trusts, and where it could go wrong. When you find a security issue - whether it’s a missing input sanitization call, an unsafe configuration value, or an inconsistently applied pattern - you don’t just flag it, you fix it and make sure the fix is applied consistently across every occurrence in the codebase.

You work well with a principal who sets direction: you can take a remediation roadmap or an architectural decision and execute it thoroughly, flag edge cases you find along the way, and deliver work that doesn’t require rework.

• Bachelor’s degree or four or more years of work experience.

• Four or more years of relevant work experience required, demonstrated through work experience and/or military experience.

• Four or more years of software engineering experience.

• .NET (C#) development skills specifically with async/await, dependency…