Technical Program Manager

Full Swing Golf•Carlsbad, CA

8d•Hybrid

About The Position

Full Swing is hiring a Technical Program Manager to own delivery for one or more engineering pods. This is an execution and accountability role, not a status-reporting role. You are the person in the room who knows exactly why a date will or won't hold, who has already resolved the dependency that would have blocked it, and who tells leadership the truth about risk before it becomes a surprise. You will partner directly with engineering leads, QA, product, and design to turn ambiguous scope into a sequenced, resourced, credible plan, and then you will drive that plan to completion. You are measured on whether the things you own ship on the date you committed to, not on how well-organized your tracker looks.

Requirements

7+ years as a Technical Program Manager (or equivalent technical project/program management role) inside a software engineering organization. Programs outside of engineering (marketing, sales operations, general business PM) don't translate to this role.
A track record of driving multiple concurrent, cross-team technical programs to on-time delivery in a fast-paced environment, with evidence you can point to specific dates you owned and hit.
Real technical fluency: you can read a system architecture diagram, follow an engineering trade-off discussion, and ask the question that surfaces the actual risk, without needing an engineer to translate for you.
Experience building and defending data-driven forecasting models based on team throughput and historical velocity, and using them to push back on unrealistic dates.
Advanced fluency in Jira and Confluence: cross-project dependency mapping, release/sprint planning, and building your own reporting rather than relying on someone else's dashboard.
Practical experience with agile and/or hybrid delivery models as actually run inside engineering teams, not textbook process knowledge.
A demonstrated bias toward resolving problems directly with the people who own them rather than escalating or documenting first.
Excellent written and verbal communication, calibrated for direct, executive-level candor rather than diplomatic hedging.
Bachelor's degree in Computer Science, Engineering, or a related technical field, or equivalent hands-on experience.

Nice To Haves

Experience as a TPM in a games, simulation, consumer hardware, or interactive entertainment company.
Experience running programs that span multiple concurrent product lines or business units.
Experience partnering directly with QA leadership on release readiness and go/no-go gating criteria.
PMP, SAFe, or equivalent certification is a plus, but real delivery track record matters more than credentials.

Responsibilities

End-to-end delivery for your assigned program(s) or pod(s), from scoping through release and post-release wrap-up.
A single master timeline per program that reflects real engineering capacity and historical throughput, not optimistic guesses.
Cross-team dependency mapping. You surface the dependency that will break the date and get it resolved before it does, not after.
Release forecasts leadership can build on. If a date moves, you're the first to know, the first to say so, and you bring the recovery plan with you.
A risk register that is actually driven to closure, not just maintained as a document.
Program reviews and syncs built around decisions and unblocking, not readouts. If a meeting produces only a status update, it shouldn't be on the calendar.
Direct accountability conversations with engineering, QA, and product owners when commitments slip, delivered constructively but without softening the truth.
Post-release retrospectives that feed real changes back into estimation, sequencing, and how the next program is planned.
Scope and trade-off input alongside Product, Design, and QA when schedule, quality, and scope come into tension.