Technical Program Manager

About the role

Platform work at SoSafe carries outsized leverage. One well-run migration touches a dozen services at once. One adopted shared library saves every team that builds on it from solving the same problem twice. One monitoring signal catches a problem before a customer ever sees it. The work often goes unnoticed when it's going well, but its absence is felt across half of Product Development within a week.

We're hiring a Technical Program Manager to embed into one of our platform teams and bring order to that complexity. You'll partner closely with the Product Manager, Engineering Manager, and their Tech Leads to drive the when and how of the roadmap: sequencing the work, surfacing risk early, holding cross-team commitments together, and making sure what ships lands cleanly across every team that depends on it.

This role owns program outcomes, not status reports. You'll think in systems, work in mechanisms, and earn trust by removing friction the team didn't know was costing them time.

Here's how you'll make a difference

• Own end-to-end delivery for programs that touch a dozen services at once: an architecture migration, a compliance remediation, a legacy system sunset.
• Partner with Product Management and GTM stakeholders on platform changes with customer-facing impact, keeping rollouts, communications, and external commitments in lockstep with engineering delivery.
• Drive adoption of shared platform capabilities that other teams are supposed to build on, closing the gap between "we shipped it" and teams actually using it.
• Manage multi-team migrations where downstream consumers, external commitments, and legacy constraints all need to land in the right order. A missed dependency here costs months, not days.
• Run the mechanics that keep a dozen concurrent programs honest: dependency maps, risk logs, decision records, and the recurring check-ins nobody wants to run but everybody needs.
• Bring rigor to how delivery health gets measured, incident counts, adoption rates, time-to-land, and use it to drive change instead of producing another report.

What makes you a great fit

• You've run complex, cross-functional technical programs and can point to ones where the technical decisions were yours to shape, not just to track.
• You hold your own in deep engineering conversations. You don't need to write the code, but you need to understand what's being argued about and why it matters.
• You bring structure to ambiguity without over-engineering it. Your default is the lightest mechanism that solves the problem.
• You've worked where the consumers of your output are other engineering teams, whether that's infrastructure, data pipelines, or internal APIs.
• You've managed a migration or sunset with real downstream impact, and you know how to land it without breaking trust.
• You communicate directly. Short sentences, clear asks, no filler. You write decisions down and make sure the right people see them.
• You're comfortable in Jira, Confluence, and the rest of a modern engineering toolchain, and you have opinions about how they should be used.

Nice to have

• Background in infrastructure, data engineering, or applied AI/ML platforms.
• Experience inside a SaaS company through a phase of platform consolidation or modernization.
• Familiarity with SLOs or monitoring practice as a delivery signal, not just an SRE artifact.

What success looks like

• 3 months. You're embedded with the team's engineering leadership, have a clear read on every active program, and have started reshaping how the group plans, tracks, and communicates delivery.
• 6 months. You're the trusted operating partner for the group. Initiatives that were drifting are landing predictably, and the cross-team dependencies that used to surprise us are surfacing weeks earlier.
• 12 months. The team is delivering with a rhythm other groups want to copy. The mechanisms you built are running themselves, and you're picking the next compounding problem to solve.