Senior Technical Delivery Leader

<div class="content-intro"><div> <div> </div> <div>At Accenture Federal Services, nothing matters more than helping the US federal government make the nation stronger and safer and life better for people. Our 13,000+ people are united in a shared purpose to pursue the limitless potential of technology and ingenuity for clients across defense, national security, public safety, civilian, and military health organizations. </div> <div> </div> <div>Join Accenture Federal Services, a technology company within global Accenture. Recognized as a Glassdoor Top 100 Best Place to Work, we offer a collaborative and caring community where you feel like you belong and are empowered to grow, learn and thrive through hands-on experience, certifications, industry training and more. </div> <div> </div> <div>Join us to drive positive, lasting change that moves missions and the government forward!</div> <div> </div> </div></div><p><strong>You Are:</strong></p> <p>We are seeking a Senior Technical Delivery Leader to own the technical vision that wins and shapes government mission cloud opportunities, then carries that vision through execution as the up-and-out and down-and-in connective layer between customer stakeholders and delivery teams. This role translates government requirements — mission need, compliance constraints, operational environment — into a credible, executable technical narrative that wins the opportunity, then hands that narrative to architects and engineers as direction, not detail. This is not an architecture role.</p> <p>The Senior Technical Delivery Leader does not design systems, write infrastructure code, or own technical implementation decisions — that authority sits with the Principal Architect and delivery engineering teams. This role owns the vision those teams execute against, and the relationships that make the vision credible to the people paying for it.</p> <p><strong>What You Will Own:</strong></p> <ul> <li>Technical vision and narrative for pursuits and active programs: the story of how government mission requirements translate into an executable, credible technical approach — defensible to customer technical evaluators and executive sponsors alike</li> <li>Up-and-out stakeholder engagement: direct, recurring technical dialogue with customer executives, government technical leads, and capture leadership — the person in the room translating mission need into technical direction</li> <li>Down-and-in technical direction to delivery teams: converting the won vision into clear intent for architects and engineers, without dictating their design — clarity of intent, not a design spec</li> <li>Requirements translation from government mission and compliance context (RMF, DoD Cloud Computing SRG, Impact Levels, edge/hybrid operational constraints) into a technical approach that survives contact with delivery</li> <li>Proposal and capture technical leadership: shaping technical volumes, win themes, and orals strategy alongside capture — measured by opportunities won, not proposals submitted</li> <li>Edge compute and hybrid environment credibility: fluency in disconnected, intermittently-connected, and tactical edge operating constraints, and what they mean for a technical approach — enough depth to be believed by government technical evaluators, not enough to replace the architect who designs it</li> <li>Handoff discipline at the win: a clean transition of vision and customer context to the Principal Architect and delivery leadership at award — the vision holds up because the handoff was real, not because the leader stayed hands-on</li> <li>Customer relationship continuity across the pursuit-to-delivery boundary — the conne