Senior Technical Program Manager

Job Description

Location: Remote - United States

\n

Travel: Approximately once per quarter

\n

Compensation: Target total annual cash compensation of approximately $140,000 - $185,000 + equity

\n

\n

About the Role:

\n

\n

We’re partnering with a fast-growing technology company to hire a Senior Technical Program Manager who can bring structure, predictability, and accountability to a complex technical operation.

\n

This is not a traditional software TPM or Scrum Master role focused primarily on managing Jira boards, sprint ceremonies, or software releases.

\n

The company operates at the intersection of hardware, software, engineering, field operations, and physical infrastructure. Customer deployments require people, equipment, contractors, engineering work, and schedules to come together at the right time. When they don’t, the consequences happen in the real world - engineers arrive on site before hardware is ready, contractors have different expectations about scope, or technical dependencies delay a customer deployment.

\n

We’re looking for someone who sees those problems coming.

\n

You’ll create a reliable operating rhythm across technical deployments, resource planning, engineering priorities, and field operations. You’ll identify missing dependencies, clarify ownership, challenge unrealistic timelines, and make sure teams are truly ready before commitments are made.

\n

The ideal person has successfully brought order to a fast-growing, somewhat chaotic technical organization before - and genuinely enjoys doing it.

\n

\n

What You’ll Own:

\n

Technical Resource & Capacity Planning

\n

Create visibility into technical resources and commitments across customer deployments, field support, R&D, and other technical initiatives.

\n

Forecast field engineering needs and identify capacity constraints before they become problems.

\n

Coordinate resources across multiple concurrent projects and competing priorities.

\n

Identify scheduling conflicts, dependencies, and resource gaps early.

\n

Work with project managers and technical leaders to establish realistic timelines.

\n

Escalate tradeoffs when competing priorities require leadership decisions.

\n

\n

Deployment Readiness:

\n

\n

Establish a reliable process for determining whether technical deployments are actually ready to proceed.

\n

Coordinate hardware, software, networking, field engineering, contractor, and other external dependencies.

\n

Ensure prerequisites are confirmed before technical resources are mobilized.

\n

Track technical milestones and dependencies against customer delivery schedules.

\n

Identify readiness risks and communicate them clearly to the appropriate stakeholders.

\n

Coordinate technical changes, releases, and rollouts that impact customer deployments.

\n

Reduce avoidable surprises, wasted field time, and last-minute escalations.

\n

\n

Program & Technical Operations:

\n

\n

Build practical systems for tracking commitments, ownership, dependencies, risks, and timelines.

\n

Create a single reliable view of technical work across multiple projects and teams.

\n

Identify broken or missing processes and implement solutions without waiting for detailed direction.

\n

Surface cross-functional dependencies and competing priorities.

\n

Establish planning and coordination cadences that improve visibility and accountability.

\n

Continuously improve processes based on recurring bottlenecks and lessons from previous deployments.

\n

\n

R&D & Technology Rollouts:

\n

\n

Coordinate technical initiatives that impact current or future field deployments.

\n

Support the evaluation and rollout of new hardware, sensors, gateways, software capabilities, and other technologies.

\n

Coordinate testing, pilots, acceptance criteria, and production-readiness reviews.

\n

Help transition validated technologies from R&D into repeatable deployment processes.

\n

Balance longer-term R&D initiatives against immediate customer and field-support needs.

\n

\n

What We’re Looking For:

\n

\n

You are an exceptional organizer who naturally sees the details other people miss.

\n

You can look across multiple projects, teams, schedules, and dependencies and quickly identify where something is likely to break. You don’t simply collect status updates - you clarify ownership, follow through, anticipate problems, and drive work toward completion.

\n

You’re also comfortable operating without a perfect playbook. When a process is missing or broken, your instinct is to understand the problem, build something practical, and make it work.

\n

Most importantly, you know how to create accountability without creating unnecessary bureaucracy. You can challenge an engineer’s timeline, negotiate priorities with an experienced project manager, coordinate with contractors, and escalate a risk to leadership while maintaining strong relationships across the organization.

\n

\n

Qualifications:

\n

\n

Significant experience owning complex technical programs, projects, deployments, or operations.

\n

Demonstrated success bringing structure and predictability to an ambiguous or fast-growing organization.

\n

Exceptional organization, follow-through, and attention to dependencies.

\n

Strong resource planning, scheduling, risk management, and prioritization skills.

\n

Experience coordinating work across multiple technical and operational teams.

\n

Ability to independently identify problems, create processes, and drive adoption.

\n

Technical fluency sufficient to understand hardware, software, networking, and field-deployment dependencies and ask the right questions.

\n

Excellent written and verbal communication skills.

\n

Strong interpersonal judgment and the ability to hold experienced stakeholders accountable without creating unnecessary friction.

\n

Comfort managing multiple concurrent priorities in an environment where plans can change quickly.

\n

\n

Particularly Relevant Backgrounds:

\n

\n

We’re especially interested in candidates who have worked in environments involving:

\n

IoT or connected hardware

\n

Data center or infrastructure deployments

\n

Telecommunications or networking

\n

Field engineering or field operations

\n

Building technology, controls, or operational technology

\n

Hardware and software integration

\n

Distributed technical teams

\n

Complex enterprise technology deployments

\n

You do not need to be an engineer. You won’t be expected to write code, design hardware, or configure networking equipment.

\n

You do need enough technical fluency to recognize when important questions haven’t been answered and enough operational judgment to make sure they are answered before a project moves forward.

\n

\n

What This Role Is Not:

\n

\n

This is not primarily a Scrum Master role.

\n

If most of your experience has centered on facilitating sprint ceremonies, maintaining Jira boards, managing software backlogs, or coordinating standard software releases, this role is unlikely to be the right fit.

\n

We’re looking for someone who has managed complexity in the real world - where people, hardware, engineering work, schedules, contractors, customer commitments, and physical deployments all have to come together successfully.

\n

\n

What Success Looks Like:

\n

\n

Within your first several months, the organization should have substantially better visibility into technical commitments, resource capacity, deployment readiness, and cross-team dependencies.

\n

Technical teams should know what they’ve committed to and when. Project teams should have confidence in whether Technology will actually be ready. Field engineers should arrive at deployments with the necessary prerequisites in place. Leadership should spend significantly less time resolving routine coordination issues.

\n

Ultimately, your job is to make complex technical execution feel predictable.

\n

\n