Director of Software Engineering - Unified Ingress
Director of Software Engineering - Unified Ingress
Posted today
SENIORITY
Manager
About the role
- Own the end-to-end delivery plan for the platform - milestones, dependencies, critical path, and committed dates across all workstreams
- Set and enforce engineering standards - code review, testing, documentation, observability-first design, and production readiness criteria
- Chair technical design reviews for the gateway, control plane, and session management components, and make architectural decisions where the team needs a call
- Partner with enterprise Architecture groups to align the platform to reference architectures, secure design approvals, and represent the platform in architecture forums
- Partner with Infrastructure, Network, Cybersecurity, and Identity (AuthE / Sentry) teams to sequence and unblock shared dependencies including DNS, CDN/WAF, certificates, perimeter policy, and identity provider integration
- Drive the LOB migration program - onboarding sequencing, cutover planning, rollback readiness, and decommissioning of legacy authentication Web Agents and Apache proxies
- Run an efficient delivery cadence - sprint planning, backlog grooming, dependency tracking, risk and issue management, and capacity planning against roadmap commitments
- Required qualifications, capabilities, and skills 12+ years of industry experience, including 4+ years leading engineering teams
- Proven track record managing teams of 15+ engineers across multiple concurrent workstreams, including line management, performance management, hiring, and mentoring
- Strong hands-on technical grounding in ingress and gateway technology - Envoy Proxy (xDS/ADS, ext_authz, HTTP/2, gRPC) and/or Kong API Gateway - sufficient to lead design reviews and challenge implementation decisions credibly
- Working depth in OAuth 2.0 / OpenID Connect (OIDC) / Proof Key for Code Exchange (PKCE) flows, Demonstrating Proof of Possession (DPoP) sender-constrained tokens, mutual Transport Layer Security (mTLS), and session management patterns
- Production Kubernetes experience (Amazon Elastic Kubernetes Service (EKS) and/or on-prem clusters) and GitOps delivery models (ArgoCD, Helm)
- Go development background sufficient to review control-plane code, set engineering standards, and participate in design discussions
- Experience partnering with enterprise Architecture functions - representing designs in architecture review forums, aligning to reference architectures, and negotiating exceptions
- Experience partnering with Infrastructure, Network, and Cybersecurity teams on shared dependencies such as DNS, CDN/WAF, certificate lifecycle, firewall policy, and perimeter change management
- Preferred qualifications, capabilities, and skills
- Financial services or other regulated-industry experience, including regulatory and audit engagement
- Experience running a migration program that decommissions legacy infrastructure while traffic is live
- Familiarity with Open Policy Agent (OPA) and policy-as-code authorization models
- Familiarity with Open
- Telemetry, Dynatrace, and Splunk Security Information and Event Management (SIEM) toolchains
- Background in identity platforms (ForgeRock, Security Assertion Markup Language (SAML) federation, token exchange patterns)
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
