Technical Program Manager / PM -- Customer & Partner Engineering
Technology
Job Description
OpenInfer is looking for a technical program manager to be the connective tissue between our engineering team and the customers, partners, and hardware ecosystem we work with. It's for someone who can sit down with a partner's engineering team and go deep on technical tradeoffs, then turn around and drive the internal program work needed to actually deliver on what was discussed.
\n
You'll be a face of openInfer in customer and partner conversations and at industry events — and the person who takes those conversations and turns them into a program engineering can execute against.
What You'll Do\n
- \n
- Drive customer and partner-facing technical conversations — scoping integrations, understanding requirements, and building trust with technical stakeholders at our hardware and cloud partners.
- Own and drive engineering programs internally: define milestones, coordinate across engineering workstreams, track progress, unblock the team, and keep stakeholders aligned.
- Translate customer and partner needs into clear technical requirements and roadmap input for engineering.
- Represent openInfer at industry events, conferences, and meetups — talking shop with customers, partners, and the broader AI infra community.
- Build and maintain relationships with technical leads and decision-makers at partner organizations and customers.
- Act as a credible technical voice on inference infrastructure — model serving, GPUs/accelerators, heterogeneous compute — without needing a specialist alongside you.
- Feed field intelligence back to the team: what customers and partners need, what's blocking adoption, where the technical gaps are.
- Travel as needed to customer sites, partner offices, and events.
\n
\n
\n
\n
\n
\n
\n
\n
What We're Looking For\n
- \n
- Mid-level experience (roughly 4–7 years) as a PM, TPM, or similar technical role, ideally in AI/ML infrastructure, cloud, or developer tools.
- Solid technical understanding of AI/ML systems — enough to hold a real conversation about inference, model serving, or infrastructure without needing to be walked through it.
- A track record of running engineering programs: setting milestones, coordinating cross-functional work, and keeping things moving without being told twice.
- Excellent communicator — equally comfortable in a technical whiteboard session with a partner's engineers and in a program status update with your own team.
- Genuinely energized by being customer and partner-facing, and by showing up at events — not just working behind a doc.
- Self-directed and comfortable with ambiguity at an early-stage startup.
\n
\n
\n
\n
\n
\n
\n
