Technical Project Manager (hands-on)
The role involves end-to-end program delivery, which includes shaping delivery plans, defining workstreams and milestones, managing cross-team dependencies, and ensuring transparent progress reporting. Responsibilities also cover owning program mechanics like RAID management, escalation paths, release planning, and maintaining documentation.
- On-site
- Canada
- Posted Mar 10, 2026
- 1 position
More jobs you can apply to directly
Similar opportunities posted by employers hiring on Jobs.ca, with no external application form.
Job summary
Responsibilities Hands-on means end-to-end program delivery: shaping a delivery plan from ambiguous inputs, defining workstreams + milestones + critical path, managing cross-team dependencies, driving decision-making, and ensuring transparent progress via measurable reporting. Owns program mechanics: RAID (risks/actions/issues/dependencies), escalation path, release planning, stakeholder cadence, and “single source of truth” documentation. Technically fluent enough to engage engineering on APIs/integrations, sequencing, architecture constraints, and delivery risks (not necessarily hands-on coding). Experience running multi-squad, multi-quarter programs in a platform/marketplace environment is a plus. Required Qualifications Years of experience: Typically 8–12+ years total experience 3–6+ years in Technical Program Management / Technical Delivery / Program Leadership across multi-squad, multi-quarter initiatives.
What you’ll do
The role involves end-to-end program delivery, which includes shaping delivery plans, defining workstreams and milestones, managing cross-team dependencies, and ensuring transparent progress reporting. Responsibilities also cover owning program mechanics like RAID management, escalation paths, release planning, and maintaining documentation.
Requirements
Candidates typically need 8-12+ years of total experience, with 3-6+ years specifically in Technical Program Management or Program Leadership for multi-squad, multi-quarter initiatives. Technical fluency is required to engage engineering on technical aspects, though hands-on coding is not necessary.
Other relevant skills
Identified from the job description. Confirm important requirements above.
- Program Delivery
- Workstreams
- Milestones
- Critical Path
- Dependency Management
- Decision-Making
- Progress Reporting
- RAID Management
- Escalation Path
- Release Planning
- Stakeholder Cadence
- Documentation
- Technical Fluency
- APIs
- Integrations
- Architecture Constraints
Job areas
- Management & Leadership
- Technology
- Software
- Engineering
- Consulting
Additional details
- Minimum experience
- 10+ years
- Posting language
- English
- Working hours
- 40 hours per week
- Seniority
- Mid-Senior level