Search by job, company or skills

the product highway

Product Manager - Client Delivery

Save
new job description bg glownew job description bg glownew job description bg svg
  • Posted 2 hours ago
  • Be among the first 10 applicants
Early Applicant

Job Description

About TPH

The Product Highway is an AI-native product strategy and engineering firm that partners with businesses from the earliest spark of an idea all the way through to enterprise scale. We grew from zero to multi-million ARR within our first year, working with clients across India, APAC, Europe, and North America.

AI got very good at the how, shipping code faster than ever. But almost nothing has changed in the what: deciding what to build, why, and in what order. That's where we live. We believe software is an approximation of the real world, and what matters isn't lines of code or sprint velocity, it's whether the solution actually maps to how a business works, how customers think, and how value gets created.

From in-house AI project managers to near-universal adoption of tools like Cursor and Claude, we've rethought every conventional process from first principles. AI isn't a feature we offer, it's how we think, build, and deliver.

Why we're hiring

We need someone who owns the product detail, the person who turns high-level product direction into specs engineers can build against, catches the edge case the designer missed, resolves ambiguity before it costs a sprint, and untangles priority conflicts before they stall the team. Someone who knows when a requirement is actually two requirements pretending to be one, and who won't let anything ship that doesn't solve the problem it was meant to solve.

The job is simple to describe and hard to do: make sure the team always knows what to build next, why it matters, and what done looks like.

This isn't a project management role dressed up with a product title. We have delivery managers who track timelines. This is product management, owning the substance of what gets built, not the schedule it gets built on.

You'll work across multiple client engagements simultaneously, embedded deeply enough in each to carry context but not so deep that you lose the ability to context-switch. You report to the CTO and collaborate with the Product Engineer on each engagement, together forming the product layer that sits between the client's business problem and our engineering execution.

Who we're looking for

Regardless of role, every person at TPH shares these traits:

  • End-to-end owners. You own outcomes, not tasks. If something you're responsible for falls through a crack, that's on you, because bugs are easier to fix, misalignment is expensive.
  • Clear, direct communicators. Bad news doesn't get better with age. You surface problems early and communicate with precision.
  • Uncompromising on quality. You have a quality bar that's yours, not your manager's. You won't ship something you wouldn't stand behind, even under deadline pressure.
  • AI-obsessed. You see AI as how work gets done, not a nice-to-have. If you're still doing something manually that AI could handle, you feel that as friction, not normalcy.
  • Structured thinkers. When faced with an ambiguous problem, you break it down, reason through the trade-offs, and arrive at a position. You don't wait for someone to tell you the answer.

What you'll own

Requirements & Specification

  • Turn high-level product direction into detailed, buildable requirements: user stories, acceptance criteria, edge cases, and boundary conditions that leave no room for ambiguity
  • Own the backlog across your engagements. Every item should have a clear problem statement, a defined scope, and a reason it's prioritized where it is. You're not a Jira jockey.
  • Be the person who catches the gap between what the client said and what the team understood, before it becomes a wasted sprint
  • Write specs that engineers respect. Crisp, structured documents that answer the questions engineers actually have.

Sprint Execution & Delivery

  • Own sprint planning and execution across your engagements. You decide what goes into each sprint based on the product roadmap, team capacity, and client priorities.
  • Be the first line of defense when requirements are ambiguous mid-sprint. The engineer shouldn't need to escalate for a clarification you can resolve.
  • Run sprint ceremonies that are actually useful. Working sessions where real decisions get made, not rituals performed for process compliance.
  • Track delivery quality and speed. You care whether the thing we shipped actually works as intended, not just whether the ticket was closed.

Design & Engineering Collaboration

  • Work with designers to ensure what gets designed is buildable, scoped, and solves the right problem. You're the bridge between design intent and engineering reality.
  • Sit with engineers during technical discussions to ensure product context isn't lost when technical trade-offs are being made.
  • Be opinionated about UX even when you're not pushing pixels. You should notice when a flow doesn't make sense, when an interaction model is confusing, or when the design has drifted from the problem we're solving.

Client Communication & Context

  • Be present in client meetings alongside the delivery manager to ensure product decisions are grounded in what you're hearing directly from the client.
  • Maintain a living understanding of each client's business context. You shouldn't need a briefing before every call. You carry the context because you're embedded in the engagement.
  • Surface product risks and scope questions to the Product Engineer before they become client escalations. You're the early warning system.
  • Communicate trade-offs to clients in language they understand. Not we need to refactor the state management layer, but if we take the shortcut now, here's what breaks in three months.

Must-haves

  • 3–5 years in product management at a product company or consulting firm where you owned requirements, worked directly with engineering teams, and shipped real products
  • You've written specs that engineers actually used. Artifacts that shaped what got built, not documentation theater.
  • Strong technical intuition. You understand how software systems work well enough to have productive conversations with engineers and ask the right questions in technical discussions.
  • You can manage a backlog across 2–3 concurrent engagements without dropping context. You have a system for staying on top of multiple moving pieces, and it works.
  • You've worked in environments where requirements were ambiguous and clients changed their minds, and you thrived.
  • Excellent written communication. Your specs, your Slack messages, your emails are clear, structured, and precise. People don't have to ask follow-up questions to understand what you meant.
  • You default to action. When you see a gap, you fill it. When you see ambiguity, you resolve it. You don't wait for someone to assign you the problem.

Strong signals

  • Experience at a high-growth product company or a services/consulting firm where you worked across multiple clients or product lines simultaneously
  • Background in B2B SaaS, enterprise platforms, or marketplace products. Domains where product complexity is real and requirements are non-trivial.
  • You've worked alongside or reported into a senior product leader and know what it means to execute against someone else's product vision while adding your own judgment.
  • Experience in AI-assisted product development. You've seen how AI changes scope estimation, team composition, and delivery timelines, and you've adapted your PM practice accordingly.
  • You've run or participated in discovery sessions, user interviews, or client workshops and can synthesize what you hear into actionable product direction.

AI-native expectations

  • Uses AI tools daily for drafting specs, analyzing requirements, summarizing client conversations, creating test scenarios, and preparing for sprint planning.
  • Can evaluate AI-generated output from engineering. You understand when AI-assisted code needs human refinement and can flag quality gaps before they reach the client.
  • Thinks about AI as a way to operate at 2–3x the breadth a traditional PM could cover. Tracking multiple engagements, maintaining context, and staying on top of details that would otherwise slip.

How to apply

We care less about your resume and more about how you think about product problems.

Please fill out this short form to apply for this role: https://forms.gle/DrXWcKLYufpjbpBm9

More Info

Job Type:
Industry:
Employment Type:

About Company

Job ID: 146430559

Similar Jobs