Buyandship Hiring! Full Time Product Manager - Builder in Kowloon Peninsula, Hong Kong - Ricebowl

What you’ll own

• Every product decision for your surface area. Flows, states, edge cases, copy, sequencing, and what ships first versus what gets cut — decided by you, inside an agreed scope and metric.

• The design. You design your own flows and screens. We care about the design itself, not the tool — Figma, HTML, or anything else is fine. On first-run, brand-carrying, or payment surfaces our design team works alongside you; the work stays yours. And you can ask our designers to look at anything, any time, for any reason — early on we expect you to ask often.

• Talking to users. BNS has no UXR function — PMs own user research end-to-end. Interviews, surveys, and testing what you built with people who actually use it.

• Defending your decisions to management. Directly, in the room.

• Shipping narrow. Solve the real problem for real users now — don’t build for every future case. Ship the narrow thing, learn from it, and let engineering generalise whatever survives. Say plainly in your spec where it’s deliberately narrow and what would break if we stretched it.

• What you won’t own: how it’s built. API contracts, call order and state transitions, scaling and performance sit with engineering.

Requirements:

• 0–4 years (T1: 0–2; T2: 1–4) — and zero is a real number here. If you’ve owned product outcomes end-to-end, show us. If you haven’t held the title yet, show us the closest thing you have owned end-to-end: a research project, a product you designed, an analysis someone acted on.

• You design — and this is the one that doesn’t flex. You can produce flows and screens complete enough that an engineer builds from them without interpreting. We look at the design itself: not the file format, and not where you learned it. We’re firm here because the design handoff is the part of our process that already works, and we’re not willing to regress it.

• You settle edge cases before handoff, not during implementation. If a flow has four failure states, all four are in the spec.

• Direct with management. You can take a decision into a room with senior stakeholders, defend it with evidence, and change your mind in public when the evidence says so.

• You talk to users yourself — and you do it without being asked to.

• Builder mode — a hard bar here, not a bonus. The “/ Builder” in the title is the job:

1. You prototype your own ideas with AI tools (Claude Code, Claude Design, Figma Make, or equivalent). The bar is a clickable demo in a day, to make an idea concrete before engineering invests in it — not production-grade.

2. You self-serve your own data questions — funnel, retention, cohort — without queueing a request. Natural-language-to-SQL counts; hand-writing joins is not the bar.

3. You write a 10-row eval set for any AI feature you touch: concrete examples of what good output looks like.

4. And you review what AI produces rather than passing it on. That review is the part we’re hiring for.

• Proficient in Cantonese, Mandarin, and English — our users, suppliers, and team move across all three.

Nice to have:

• A design background — or a data, CS, information-systems, or analytical one. All of them feed this role well, and none is required. They tend to arrive with opposite halves: design backgrounds bring craft and flow thinking; data, CS and analytical backgrounds bring the instinct that a claim might be wrong — which is most of the “verified” bar above — and usually a head start on the builder bar. Expect us to press you hardest on the half you didn’t arrive with — bring evidence for both.

• Shipping small changes yourself via PR — copy, a config value, a flag — with a reviewer. Above the bar, not at it.

• Experience somewhere the design and the product decision already sat with the same person.

• Growth product work, or comfort being measured partly on metrics moved.

• Working with engineering teams of 3–8

The Opportunity for Talent:

Best fit for someone who would rather decide than escalate, who treats an unanswered question in their own spec as a defect, and who wants the design call and the product call to be the same job rather than two.

Buy&Ship is Hong Kong’s leading cross-border shipping platform. Hong Kong shoppers source from Japan, Korea, the US and beyond, and we’re the bridge that makes those purchases land at their door.

This role is unusual in one specific way: you own the product decision and the design, together. Not a PM who briefs a designer, and not a designer who executes someone else’s spec — one person who decides what we build, decides what it looks like, and hands engineering something complete enough to build from without coming back.

The “/ Builder” is literal, and it’s bounded. You prototype to discover — a demo that makes an idea concrete enough to put in front of someone. Production and scaling stay with engineers. You’re not hired to write the shipped code; you’re hired so that fewer wrong things get built.

We work this way because the limit on how fast we ship is no longer how fast code gets written. It’s whether the decisions upstream of the code were actually settled. When they aren’t, engineering stops and comes back — and every one of those round trips costs more than making the decision properly the first time would have.

The role is open at T1 (Associate PM, 0–2 yrs) or T2 (PM, 1–4 yrs). Apply once; we’ll set the level to your experience and capability.

If you’re graduating, or coming from data or design rather than product management — apply. We’re hiring for a profile that is genuinely new: product judgment, design, and real AI fluency in one person. The people who have that combination often haven’t held a PM title yet, and we’d rather find them than wait. What we test is whether you can do the work.