Senior Forward‑Deployed Identity Security Leader

Accenture

Chicago (IL)

On-site

USD 87,000 - 254,000

Full time

4 hours ago

Be an early applicant

Application generator

Turn this role into an interview — a resume and cover letter built around what this employer wants.

Get past ATS filters

Job summary

Accenture is seeking a Forward Deployed Engineer for the Agentic Identity Platform in the United States. You will lead technical design on engagements, review implementations, and set direction while staying hands-on when needed.

Expect to engage with Fortune 100 clients, prototype, and build reference architectures for cutting-edge identity and AI agent systems. You will drive build-versus-buy decisions, prototype against emerging standards, and mentor engineers on your team, with travel as

Qualifications

Minimum of 8 years of professional experience building and shipping production software.
Hands-on technical work within the last 24 months, counting development, prototyping, code review, or technical design review.
Minimum of 4 years of professional development in at least one of Python, Go, Rust, TypeScript, Java, or C++.
Minimum of 4 years designing and building concurrent or distributed systems that ran in production.
Minimum of 3 years of hands-on experience deploying and operating cloud infrastructure on AWS, Azure, or GCP, including containers and CI/CD pipelines.
Minimum of 2 years of technical leadership of at least 2 engineers, including code review and design review responsibility.
Bachelor's degree in Computer Science (or equivalent) OR (minimum 12 years) work experience. (If Associate's Degree, must have minimum 6 years work experience)

Responsibilities

Own the technical design for an engagement, including the decisions you'll be held to when they're wrong.
Stay close enough to the agentic identity stack to review the implementation critically and prototype in it when that's the fastest way to settle a question
Set the technical direction the engineers on your engagement follow, and review their code
Reverse-engineer how identity actually works in a client environment, then design what it should be
Make the build-versus-buy calls and document why, in a form that survives your leaving the project
Prototype against emerging standards and vendor betas, often before documentation exists
Build the reference implementations and technical content that become how the practice does this work
Grow the engineers around you, primarily by working alongside them rather than reviewing from a distance