Product Manager

Product Manager, Customer Requests

Pune, India

• On site, full time at our Pune office

Location Pune, India. This is an on-site, full-time role at our Pune office.

Employer TruckX Technologies, Pune. You will work on the Hey Bubba! product.

Employment Full time

Experience 3 or more years in product management. B2B workflow, logistics or supply chain

software preferred.

Reports to Clarissa Luttmann, Co-founder and Chief Product Officer, Hey Bubba, Inc.

About Hey Bubba!

Hey Bubba! builds AI back-office automation for fleets and field services. Our first product is an AI dispatcher for trucking carriers: it searches load boards, contacts brokers, books loads and handles the paperwork, so carriers spend less time on the phone and in their inbox. We work with pilot and enterprise customers in the United States, and we are a small team that ships quickly.

The role

You own what our pilot and enterprise customers ask for. You turn each request into a general requirement, a prototype and a clear handoff to engineering, and you say no to the asks that would not scale. Pilots are arriving faster than one person can scope them. You would take three to four of them from first ask to a shipped, checked feature.

What you will do

• Triage in writing. Answer every customer ask within two working days: build, build in part, or not now, with

the reason and the general version of the idea.

• Write requirements engineers can build from. Behavior, every state (loading, empty, failed), who can

see it and who can change it, and what notifies whom.

• Prototype before the handoff. Build it yourself with Claude, in code or in Paper, and test it with the

customer or the team before engineering starts.

• Keep one request list per pilot. Tagged, estimated and ordered, so the sprint shows what each customer is waiting for.
• Check what shipped. Review the build on staging against your requirement before it counts as done.
• Decline kindly. One-off promises do not reach engineering. You write the version that works for everycarrier, or you decline.

How decisions work

You decide scope inside existing patterns, the order of your pilots' requests, and how to answer asks that duplicate something we already have. For larger changes you bring one recommended option with a reason,not a menu. A few decisions stay with product leadership: new patterns and components, the permissionsmodel, pricing and billing, public claims, and dated commitments to customers. The rules behind this are written down and you get them on your first day.

What we are looking for Must have

• Three or more years as a product manager or product owner in B2B workflow software, logistics or supplychain software, or an operations-heavy SaaS product.
• Requirements you wrote that engineers built without rework. You can show one.
• Daily use of an AI assistant to prototype, analyze or draft. You can describe how, and where it went wrong.
• You have declined a customer request and defended the decision.
• Clear written English and some overlap with United States working hours for customer conversations.

Strong signals

• Freight, dispatch, TMS or brokerage experience.
• You have built a working prototype yourself, not only a specification.
• You have run pilots or implementations with enterprise customers.
• You have worked with customers in the United States.

Not needed

• Visual design polish. We build in a shared design system, clean and functional first.
• Deep engineering skills beyond reading data and an API.
• People management.

How we work

• A small product and engineering team in Pune, working from our office.
• We design and prototype with Claude and Paper, from the real product, rather than handing drawings backand forth.
• In the app we aim for clean and functional first, and keep our highest polish for customer-facing and

marketing material.

• Decisions are written down, so you do not have to ask twice.