> Markdown version of [/jobs/ext/4617727-technical-program-manager](https://www.wearedevelopers.com/jobs/ext/4617727-technical-program-manager). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Technical Program Manager

- **Company:** Simbe Robotics, Inc.
- **Location:** United States
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, Data Infrastructure, Middleware, Embedded Software, Backend, Data Management, Data Pipelines
- **Published:** November 7, 2026
- **Apply:** https://startup.jobs/principal-staff-technical-program-manager-engineering-simbe-robotics-2-10701151

## About the Role

* Hands-on technical experience: you've personally built, integrated, or debugged a complex product that spans physical hardware and robotics software, not just managed a team that did.
 * Depth in at least one of hardware/robotics software (ROS or comparable middleware) or cloud/data platforms, real fluency across the others.
 * Comfort driving a room of engineers who don't report to you. You guide decisions and shape estimates through technical insight and collaborative problem-solving.
 * A track record on programs where a hardware or software slip has real-world consequences, a customer site, a fleet in the field, a fixed external date, not just an internal roadmap
 * The instinct to build only as much process as removes friction. This role exists because delivery today depends heavily on a small number of people going above and beyond. The job is to build the systems and cadence that make that unnecessary, not to add processes that slow down people who are already delivering.

## Description

* The cross-functional schedule for Simbe's highest-stakes programs: new Tally generation launches, fleet-wide software/hardware migrations, and large retail rollouts with hard external dates
 * Integration checkpoints wherever domains meet: hardware-to-ROS (on-robot software), CV model deployment onto the robot (edge inference, with real-time and compute constraints on the robot itself) alongside cloud-side model updates and data pipeline flow, and backend-to-retailer-facing reporting. For each, you define what "done" means, who owns it, and what happens when it slips
 * Deployment readiness end to end: a program isn't complete when engineering ships it, it's complete when it's live and stable in stores. You own the handoff from build to field.
 * Visibility into risk before it's a crisis: dependency mapping, a standing cross-functional review cadence, and a top-risks list that leadership actually trusts because you can defend it technically

Your first 30 days

 * Build a single dependency graph spanning hardware, embedded software, cloud/data platform, and AI/CV for the two highest-priority programs
 * Identify and document the top risks to the nearest hard external date, with enough specificity that engineering leads agree it's accurate
 * Stand up a lightweight cross-functional review cadence with real inputs from each function, not a status meeting