Product Manager

RODUCT MANAGER

We are not hiring a Product Manager for one product. We are hiring someone who can be handed almost anything a customer-facing feature this month, an internal ops tool the next, a pricing problem after that and make it land.

That is a specific kind of person. It is not the PM who has spent four years perfecting one roadmap for one surface. It is the PM who has juggled several things at once, under real deadlines, for people who noticed when it slipped and who then went and learned how to do it properly.

If you have spent most of your career in a services or consulting environment and some of it inside a product company, you are exactly who this is written for.

What you will actually do

Own projects end to end, whatever they are

• Take a problem from a vague one-line brief to a shipped, measured outcome discovery, scoping, spec, build, launch, iterate.
• Move between product areas as priorities change. Some quarters that means a customer-facing surface. Some quarters it means an internal tool that saves the ops team twenty hours a week.
• Be the single person accountable for the outcome. Not the coordinator. The owner.

Do your own thinking, with data

• Pull your own numbers. Write your own queries or get there with AI do not wait in a queue for an analyst.
• Size the opportunity before you ask engineering for six weeks. Show the maths.
• Define success up front, instrument it, and report honestly when it does not work.

Work close to the people who use it

• Talk to customers, operations staff, drivers, finance whoever the user is on that project. Regularly, not once a quarter.
• Sit with the team. Unblock them yourself instead of escalating.
• Write clearly. Specs, updates, decision notes — short, unambiguous, and actually read.

Use AI as a daily working tool

• This is a hard requirement, not a bonus. You should already be using AI every day to move faster — and be able to show us how.
• Research and synthesis: competitor teardowns, user-interview analysis, market sizing, spec drafts.
• Data: writing and debugging SQL, cleaning messy exports, building the analysis you would otherwise have queued for.
• Prototyping: putting a clickable or working mock in front of a stakeholder in a day, so the conversation is about the real thing rather than a slide.
• Automation: taking your own repetitive work and getting rid of it.
• And where it fits, building AI into what we ship — knowing what it is genuinely good at and where it will embarrass you.

What you need to have

Must have

• 4–5 years of product management, or a closely adjacent role (business analyst, delivery lead, solution consultant, founder) where you genuinely owned outcomes.
• Experience across both worlds — predominantly services or consulting, with meaningful time inside a product company.
• Demonstrable daily use of AI in your work, with concrete examples you can walk us through.
• Comfort with data: SQL or the ability to get there with AI, spreadsheets at a serious level, and at least one analytics tool.
• A track record of shipping. Specific things, with dates, that you can talk about in detail.
• Clear written English. We are a writing-first team.

Nice to have

• Logistics, supply chain, mobility, fintech or B2B marketplace exposure.
• Having worked with a distributed team across time zones.
• A technical background, or enough of one to argue productively with engineers.
• Something you built for yourself — a side project, an automation, a tool. We will always ask about i