Product Manager

• Demonstrated ability to define and move metrics, not just track them. We will ask for specific examples where you identified a metric problem before leadership did, framed the root cause, and shipped the fix.

• Strong technical fluency: comfort reading API docs, reasoning about webhooks/queues/dispatch logic, writing SQL for ad-hoc analysis, and joining a technical RCA conversation as a peer.

• Track record of owning enterprise client and partner relationships at a technical level — including running QBRs, negotiating joint SLAs, and managing escalations.

• Experience scaling team practices, not just executing them: you have introduced PRD templates, postmortem culture, or QA gates that outlived your tenure.

• Strong written and verbal English. Bahasa Indonesia is strongly preferred.

• Willingness to be on-call for major releases and Sev-1 incidents. Hard requirement that you can hold the room in a late-evening release call when something is on fire.

Nice to Have

• Prior experience at a delivery, ride-hailing, or on-demand platform with first-hand exposure to dispatch, batching, geofencing, and driver-economics problems (Gojek, Grab, Lalamove, Borzo, Shopee Express, Lazada Logistics, Dunzo, Swiggy, Zomato, etc.).

• Hands-on with Metabase / Looker / Mode for self-serve analytics. Bonus if you have actually built dashboards yourself.

• Prior experience standing up a postmortem / incident-management process from scratch.

What This Role Is Not

• This is not a release-management or scrum-master role. The release calendar is a small fraction of the work.

• This is not an order-taker PM role. We do not want someone who waits for the leadership to write the to-do list.