Agentic Identity Security Consultant

We Are Accenture Security helps organizations prepare, protect, detect, respond, and recover along with all points of the security lifecycle. Cybersecurity challenges are different for every business in every industry. Leveraging our global resources and advanced technologies, we create integrated, turnkey solutions tailored to our client's needs across their entire value chain. Whether we’re defending against known cyberattacks, detecting and responding to the unknown, or running an entire security operations center, we will help companies build cyber resilience to grow with confidence. Our team of the security sector’s brightest people uses the coolest tech to out-hack the hackers and help clients build resilience from within. We blend risk strategy, digital identity, cyber defense, application security, and managed service solutions to rethink the entire security lifecycle. Do you have the deep functional and technical experience to help implement security solutions that align with our clients’ business objectives? Do you have the expertise to design and deliver solutions for establishing system user's credentials, and processes for applying those credentials to access enterprise systems and applications? If so, read on and apply. Accenture ’s more than 2,000 security professionals deliver holistic and proactive security solutions in 47 countries, and we’d love to discuss our open Identity and Access Management (I&AM) Security role with you You Are An engineer who has stayed an engineer. You came up building things, and you have no interest in a career track that takes that away. You're resourceful about how you get there. You know which problems call for a library, which call for a vendor product, and which call for writing the thing yourself. You read the spec instead of guessing what it says. You've debugged something at 2am because you wanted to know why it broke, not because anyone asked. You've shipped code that other people depended on and that you were on the hook for when it broke. You go one layer deeper than the assignment required. You can explain a hard technical idea to someone who doesn't share your background without either condescending or hiding behind jargon. You almost certainly haven't done this specific work before. Very few people have, which is most of why it's interesting. The Work The Forward Deployed Engineer, Agentic Identity Platform is a hands-on technical role. How much of any given week you spend writing code will vary by engagement, but you'll be expected to understand the systems you work on at implementation depth, and to be able to build in them when the work calls for it. If your recent experience is limited to producing architecture decks, running vendor implementations, or coordinating offshore delivery, this is probably not the right fit, and we would rather tell you now than in the third interview. Enterprises are deploying AI agents faster than anyone has figured out how to secure them. An agent authenticates to twelve systems, spawns subagents, calls tools on behalf of a user who left the company last month and holds credentials nobody inventoried. The identity primitives that industry spent twenty years building for humans and service accounts don't cleanly extend to actors that are autonomous, ephemeral, and delegating authority to each other. We're building the platforms that solve this: agent registries, delegated authorization models, runtime attribution, and policy engines that make decisions in single-digit milliseconds. Some of it ships to Fortune 100 clients. Some of it becomes the reference architecture the industry copies. There's no vendor product to install because in several of these areas the product doesn't exist yet. You'd be a Forward Deployed Engineer, which means you write the code and you're in the room, possibly virtually, with the client while it runs in their environment. Specifically: Build and ship services in the agentic identity stack: authorization engines, agent registries, credential brokers, and authentication layers for MCP servers Own a component end to end: design, implementation, deployment, and what happens when it fails at 3am Reverse-engineer how identity actually works in a client environment, then design what it should be Prototype against emerging standards and vendor betas, often before documentation exists Build the internal tooling and reference implementations the rest of the practice reuses Explain your design to a client's engineers and defend the parts they push back on Most people arrive without the identity background, including people who are strong at all of it now. If you have some of it, tell us. If not, we'll teach you, and you'll learn it faster here than anywhere else because you'll be implementing the specs rather than reading about them. What We'd Like to See Optional, and not part of how we evaluate candidates. If you'd like to include a link to code you've written, an open-source contribution, or a te