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

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

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

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

Proposal and capture technical leadership: shaping technical volumes, win themes, and orals strategy alongside capture — measured by opportunities won, not proposals submitted

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

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

Customer relationship continuity across the pursuit-to-delivery boundary — the connective tissue that keeps the customer's trust intact as the program moves from "who we're selling to" to "who we're delivering for"

Senior Technical Delivery Leader

Responsibilities

Qualification

Required

Benefits

Company

Accenturefederalservices

More roles at Accenturefederalservices