Forward-Deployed Identity Platform Lead

Accenture

Philadelphia (Philadelphia County)

On-site

USD 90,000 - 250,000

Full time

6 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

Benefits offered by this job

Medical insurance

Dental insurance

Vision insurance

Life insurance

401(k) plan

Bonus opportunities

Paid holidays

Paid time off

Job summary

Accenture is seeking a Forward Deployed Engineer for the Agentic Identity Platform. In this client-facing role you will read, review, and make design calls based on real system behavior, not just decks, and you’ll be the senior technical voice in the room.

Requirements: 8+ years shipping production software; 4+ years in Python/Go/Rust/TypeScript/Java/C++; 4+ years designing concurrent or distributed systems; 3+ years deploying cloud infra (AWS/Azure/GCP); 2+ years of technical leadership.

Qualifications

Minimum of 8 years of professional experience building and shipping production software.
Hands‑on technical work within the last 24 months.
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.

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.