Senior Technical Program Manager, Security & Privacy

TikTok USDS Joint Venture; Seattle (WA); On-site; USD 130,000 - 170,000; Full time

Job summary

TikTok USDS Joint Venture is seeking a Security & Privacy Programs lead to coordinate cross‑functional security and privacy requirements across incident management, security architecture, engineering and product teams.

You will drive remediation from incident containment to enduring engineering changes, aligning teams on problems, shaping plans, and ensuring solutions are tested and supported by clear evidence.

Responsibilities

• Engage deeply in engineering problems: Understand system architectures, API contracts, data flows, dependencies and operational constraints to help teams solve problems, not just track delivery dates.
• Translate ambiguity into executable technical programs: Define scoped workstreams with interfaces, ownership, acceptance criteria, and resource plans, coordinating design, development, testing and rollout.

Job description

Responsibilities

About the team

The Security & Privacy Programs team helps TikTok USDS Joint Venture turn cross‑functional security and privacy requirements into coordinated execution. We work with incident management, security architects, and engineering and functional teams across departments to resolve complex issues that span systems, products, and organizational boundaries.

Our remediation work addresses the gap between containing an incident and implementing the lasting engineering changes needed to prevent it from recurring. We bring technical program leadership to that work: aligning teams on the problem, shaping actionable remediation plans, resolving dependencies, and ensuring that implemented solutions are tested and supported by clear evidence.

Responsibilities:

• Engage deeply in engineering problems: Work directly with engineers to understand system architectures, API contracts, data flows, service dependencies, and operational constraints. Review technical proposals, question assumptions, and assess implementation complexity, integration effort, and failure modes. Use that understanding to help teams solve problems rather than simply track delivery dates.
• Translate ambiguity into executable technical programs: Turn complex requirements and remediation needs into clearly scoped engineering workstreams with agreed interfaces, ownership boundaries, acceptance criteria, and resource plans. Partner with technical leads to sequence design, development, integration, testing, and rollout, making uncertainty and the work needed to resolve it explicit.
• Align stakeholders through technical credibility: Build shared goals across engineering, architecture, business, and security partners within the cross‑functional departments. Use delivery data, sound technical reasoning, and a clear connection to business outcomes to secure decisions and commitments without relying on reporting lines or formal authority.
• Manage the critical path and make balanced trade-offs: Map cross‑team dependencies, identify bottlenecks and schedule uncertainty, and keep the critical path current as technical findings and priorities change. When delays are unavoidable, compare options such as phased delivery, resequencing, reduced scope, or additional capacity against risk, quality, and business