Technical Program Manager ndash 18-month project Roles Responsibilities This TPM will be responsible for running (2) Teams. The Build Ship and Cloud Engineering teams. In general, will have some scrum masterPO responsibilities. We are looking for a PM who is internal facing similar to a Scrum Master who can handle cross team collaboration projects. Must know how to work with Development and Scrum Teams, developers in general. (The Developers are the end customers) Familiarity with CICD, Github, Jenkins, Artifactory and deployment (spinnaker) This is a languageknowledge thing (we don’t need experts here) Requirements bull You will engage with all of technology to understand their needs and distill those into actionable items. bull Be committed to quality as a top priority – you pay attention to what you make and take pride in your craft. bull You will get people passionate about the value of things like moving to the cloud, adopting Kubernetes, or venturing into chaos engineering. bull You’ll work alongside engineers that are solving complex challenges as we evolve how we build, deploy, and run software across Hulu. bull You’ll always be looking down the road to identify and minimize risks before they become a problem. bull You’ll be a communication powerhouse to ensure the entire organization knows what the team is working on and what to expect. bull You’ll have a point of view, but won’t overpower the room or have an ego. bull Partner with product and engineering to help craft schedules, roadmaps, and other artifacts. General Experience working with teams that power live streaming or VOD content. Should have exp with AWS. Turning team requests into potential backlog priorities – doing discovery and requirements gathering Ordering and maintaining the priority of the backlog by Interfacing with Product Management, Stakeholders and other TPMs Maintain communication with Product Management about team bandwidth and how much is being dedicated to Technical Debt and other non Product backlog stories Projecting team story target completion timing based on sprints Owning the end-to–end quality of the team story delivered (every story has a clear what, why and acceptance criteria) Being the customer proxy for story completion and ensuring all acceptance criteria are met before accepting the story Manage cross team dependencies and technicalarchitectural decisions needed to complete team stories Keep Product Management and Stakeholders up to date with team status, change in direction and capacity reallocation Incident Management by holding team incident retros and ensure follow-ups are completed