Role descriptionRole Summary
The Technical Lead / Technical Program Manager will provide end-to-end technical delivery leadership from Architecture and Solution Design through Build, Infrastructure, Testing, Deployment
Production Readiness.
This is a hands-on technical leadership and program execution role, not simply a project tracking function. The individual is expected to understand the architecture, challenge and clarify technical decisions, drive cross-functional teams, remove technical blockers, and maintain ownership through successful delivery.
Roles & Responsibilities
- Engage from the Architecture stage to understand business objectives, solution architecture, AWS services, integration patterns, security requirements, infrastructure needs, NFRs, and operational expectations.
- Translate architecture into executable technical delivery plans, ensuring architecture decisions are decomposed into detailed design, engineering tasks, infrastructure requirements, integration activities, testing needs, and deployment milestones.
- Drive the solution from Architecture 12 Design 12 Build 12 Infrastructure 12 Integration 12 Test 12 Deployment, maintaining end-to-end ownership and continuity across all phases.
- Coordinate Architecture, Application Development, AI/ML, Data, Infrastructure, DevOps, Security, Network, Integration, and Testing teams so that dependent activities are planned and executed in the correct sequence.
- Lead technical design discussions and reviews, ensuring detailed designs remain aligned with the approved architecture, AWS best practices, security requirements, scalability expectations, and operational standards.
- Drive engineering teams toward delivery, converting technical objectives into defined work packages, milestones, dependencies, owners, acceptance criteria, and measurable outcomes.
- Maintain end-to-end dependency management, particularly dependencies between application development, AWS infrastructure, networking/connectivity, IAM/security, environments, data, APIs, external systems, and testing.
- Facilitate technical working sessions and cross-functional forums to resolve architecture questions, interface dependencies, environment issues, infrastructure readiness, defects, and implementation decisions.
- Track technical decisions and ensure closure, maintaining architecture decisions, design actions, technical risks, dependencies, assumptions, issues, and ownership through appropriate RAID and decision logs.
- Ensure environment and infrastructure readiness for development, integration, performance testing, UAT, deployment, and production, coordinating AWS infrastructure and T-Mobile enterprise dependencies.
- Drive integration readiness, ensuring APIs, interfaces, authentication, networking, data flows, upstream/downstream dependencies, and external systems are available and validated when required.
- Partner closely with Test and Quality Engineering teams to ensure architecture and design requirements are converted into functional, integration, performance, resilience, security, and end-to-end test scenarios.
- Lead technical defect triage and resolution across Build, Infrastructure, AWS services, integration, environment, and testing teams when ownership spans multiple technical areas.
- Establish technical delivery governance, including architecture/design checkpoints, build readiness, environment readiness, integration readiness, test-entry/test-exit criteria, deployment readiness, and production-readiness reviews.
- Provide technical status and risk visibility to program leadership, focusing on architecture/design decisions, critical dependencies, technical blockers, environment readiness, integration status, quality, and delivery confidence rather than only schedule reporting.
- Support release and production-readiness activities, including deployment planning, rollback strategy, observability, monitoring, operational documentation, support transition, and post-production stabilization.
- Drive accountability across teams by ensuring every technical deliverable, dependency, risk, and action has a clearly identified owner, target date, and closure criteria.
