Your Main Duties in Flying with Us: • B2B Corporate features, end to end. From the customer problem, to the PRD, to sprint delivery, to UAT and acceptance sign-off, to reading the launch metrics. You are the accountable owner, not a helper on someone else’s feature • Finance-grade PRDs and tickets. Cost Center capture, invoice splitting, and cross-entity billing have to reconcile. Your PRD has to be clear enough that engineering builds with little back and forth. On this platform, roughly right is not enough • The corporate booking flow. Travel Policy, Travel Plan, approval chains, the B2B Corporate Booking Form, and Cost Center capture • Problem framing and discovery. You turn a vague request from a corporate client or a sales pipeline lead into a clear problem statement, empathize the people who feel the pain, and decide what is worth building • Roadmap and prioritization. You own a feature-level roadmap and prioritize on data, impact, and business context, then explain the call to the people who wanted their request first • Cross-team orchestration. A single corporate release routinely touches Order, Payment, Invoice and Billing, Refund, Loyalty, the Internal Dashboard team, Data and Analytics, Legal, and Customer Services. You drive them to decisions and keep the release moving • Metrics and experiments. You define success metrics and write the tracker spec before build so the feature is measurable on launch day, then read the data yourself to decide whether it worked or what to do next • Quality and compliance. You own UAT scope and acceptance sign-off, and you treat finance correctness and data-privacy handling (for example PII in activity logs under UU PDP) as your job, not someone else’s
• Proven end-to-end ownership. You have owned at least one product or feature from problem to launch on your own, not just supported someone else’s. This usually comes with about a year of PM or feature-owner PM work, but we weight what you shipped over the month count • PRD craft (required). You write clear, structured PRDs and tickets that engineers build from with little clarification, covering edge cases and full user flows, not only the happy path. This is the single most important screen for this role • Analytics rigor (required). You pull and read quantitative and qualitative data yourself, set success metrics, write the tracker spec, and use the data to back or challenge a decision. You do not outsource the numbers • Problem framing. You turn an ambiguous request into a clear problem statement and a prioritized plan, and you interview users to get there • Cross-team drive. You have aligned several teams on one release and driven them to a decision, not just collected their comments
This job post is uploaded by kerjaaaorg. Contact us at halo@kerjaaa.org to submit your job openings, find inaccuracy, notice a fraud or to takedown this post.
