Technical Program Manager Iii, Systems & Hardware

F5 F5 · Enterprise · Hyderabad, Bangalore

This role is for a Technical Program Manager III at F5, focusing on systems and hardware. The primary responsibility is end-to-end planning, execution, and health management of cross-functional programs. The role requires driving outcomes, resolving blockers, managing dependencies, and ensuring release quality. It emphasizes a bias for action, ownership, and proactive problem-solving within a software/technology environment. The role is not directly AI/ML development but operates within a technology company that likely uses AI/ML in its products.

What you'd actually do

  1. Own the program plan end-to-end — define roadmaps, milestones, and dependencies across 2–4 concurrent programs spanning multiple teams.
  2. Maintain a continuous, real-time pulse on program health across schedule, scope, quality, and team capacity — not through weekly snapshots, but through active day-to-day engagement with teams.
  3. Drive blockers to resolution within 48 hours or establish a clear escalation path. Program health should never be a surprise to leadership.
  4. Lead cross-functional syncs and write clear, concise status reports that give stakeholders at all levels the right context to make decisions.
  5. Design and refine program processes — sprint planning, review cadences, escalation paths — tailored to each team's working style.

Skills

Required

  • 4–7 years of experience in program or project management in a software or technology environment
  • Demonstrated track record of driving programs to completion in ambiguous, fast-moving environments
  • Strong written and verbal communication
  • Solid familiarity with Agile, Scrum, or Kanban methodologies
  • Technical fluency sufficient to engage credibly in engineering and architecture discussions
  • Experience with program management tools such as Jira, Asana, Linear, or similar
  • A bias for action

Nice to have

  • PMP, PMI-ACP, or equivalent certification
  • Experience working in [your domain — e.g., cloud infrastructure, fintech, consumer apps]
  • Exposure to OKR frameworks and program-level goal setting
  • Experience managing programs with external vendor or partner dependencies

What the JD emphasized

  • own the end-to-end planning, execution, and health of cross-functional programs
  • actively driving outcomes
  • When blockers appear, you resolve them
  • When plans slip, you replan proactively
  • When risks emerge, you own them through to closure
  • operates with urgency and ownership
  • not someone who waits to be asked
  • Own the program plan end-to-end
  • Actively maintain plans on a weekly basis
  • replan proactively with stakeholders rather than waiting to be directed
  • Manage cross-team dependencies and sequencing
  • Maintain a continuous, real-time pulse on program health
  • active day-to-day engagement with teams
  • take direct action
  • escalate with a clear recommended path forward
  • re-scope with product
  • coordinate engineering resources
  • Do not simply report status
  • Drive blockers to resolution within 48 hours
  • establish a clear escalation path
  • Program health should never be a surprise to leadership
  • Anticipate risks before they become issues
  • develop and track mitigation plans
  • Actively monitor defect and bug queues
  • engaged driver of closure
  • Partner with engineering and QA leads to run structured bug triage
  • ensuring issues are prioritized against release criteria
  • nothing critical slips through without a decision
  • Track bug burn-down trends
  • escalate when defect volume or severity threatens the release timeline or quality bar
  • Own the release readiness picture
  • consolidate bug status, open risks, and outstanding sign-offs
  • clear go/no-go recommendation
  • Drive resolution of release-blocking bugs
  • follow up daily if needed
  • escalate with a recommended path
  • don't close the loop until the issue is resolved or formally accepted as a known risk
  • Lead cross-functional syncs
  • write clear, concise status reports
  • Partner with Engineering Managers and Product Managers to align on scope, sequencing, and tradeoffs
  • surfacing tensions early and facilitating resolution
  • Escalate issues with a point of view, not just an alert
  • Come to every escalation with a recommended solution
  • Design and refine program processes
  • Drive post-mortems and retrospectives with rigor
  • translate findings into concrete process improvements that stick
  • Identify patterns across programs where systemic fixes can reduce recurring friction
  • Demonstrated track record of driving programs to completion in ambiguous, fast-moving environments — not just tracking them
  • Technical fluency sufficient to engage credibly in engineering and architecture discussions
  • A bias for action: you close loops, you follow up, and you treat an unresolved blocker as your personal problem until it's solved
  • Programs you own ship on time with clear stakeholder alignment and no last-minute surprises
  • Blockers you own are resolved within 48 hours or have a clear escalation path with a named owner
  • You never just report a blocker — you drive it
  • You've built trusted, credible relationships across engineering and product
  • Teams come to you early with problems, not after they've escalated
  • You've improved at least one team process that measurably reduces recurring friction, with evidence it has stuck
  • Program health is never a surprise to leadership
  • Stakeholders always know what's green, what's at risk, and what you're doing about it