Drimva

JPMorgan Chase

Sr Lead Security Engineer - Role Core

$176K–$260K

Plano, TX +1 · Senior · Full-time · Posted Jul 6, 2026

Location
Plano, TX
Seattle, WA
Experience
5+ years building high-performance API-first services and integrating tooling.
Education
Formal training and certification.

About the job

Leads software security engineering for secure, scalable technology products, including API-first services, security testing, and AI-assisted security workflows.

What you'll do

  • Provide technical direction, develop and review production code, and guide design and operational decisions.
  • Advocate for firmwide SDLC frameworks and practices, and influence adoption of relevant technologies.
  • Use enterprise-authorized AI to support security risk analysis, documentation, testing, and control validation, with attention to validation, sensitive data, traceability, and auditability.

What they ask for

  • Formal training and certification, plus 5+ years of experience building high-performance API-first services and integrating tooling.
  • Hands-on experience in system design, application development, testing, and operational stability; advanced in two or more of C#, C++, Go, Python, and Java.
  • Deep knowledge of HTTP/HTTPS, SSL/TLS inspection, traffic interception, and API gateway patterns; proven ability to build scalable distributed systems in a cloud-native environment.
  • Experience using enterprise-authorized AI in security engineering workflows and validating recommendations against security, resiliency, and auditability expectations.

Nice to have

  • API Gateway Development or custom proxy development.
  • SSE, CASB, or SIEM integration experience.

Pay

$175,750.00-$260,000.00 USD base salary

Tools

C#, C++, Go, Python, Java, HTTP/HTTPS, SSL/TLS, API gateway

AI focus

Uses enterprise-authorized AI for security risk analysis and documentation, security testing, and control validation; validates outputs and recommendations and handles sensitive data appropriately.

Model-written summary · the original posting is authoritative

First seen Oct 28, 2026 · Last verified Nov 5, 2026 (UTC)