Product Manager B2B / Product Consultant

About the role

You carry a module from the client's business process all the way to acceptance, and it stays yours end to end. You map the process, find the real problem behind the stated ask, write the business rules and the numbered acceptance criteria engineers build against, and prove at UAT that the problem is solved. You carry two engagements at a time, and the record you keep is the one everyone downstream works from.

• Key responsibilities
• Map the client's current-state process, identify the bottlenecks in it, and name the real problem behind the stated ask.
• Write the business requirements and the business rules for your module.

Write the numbered, testable acceptance criteria in Given/When/Then form that live in the specification appendix, so an engineer can build from them without coming back to ask.

• Explore the client's data, check it for quality, and map what each field means inside their process.
• Keep the traceability from requirement to implementation to test, so every build traces back to a need.

Write UAT scenarios from the process map and the problem statement, then validate that the client's problem is solved rather than only that features function.

• Deliver the standard operating procedures and the training when your module ships.
• Join engineers' story kickoffs and walk them through the edge cases before they write code.

Draft the weekly client report for the Senior Product Consultant to approve, carrying the client's operating reality up to the product layer.

• Keep the meeting notes, the decision log, and the change-request log as the record everyone works from.
• About you
• 2 to 4 years in product management, business analysis, or delivery consulting, or equivalent demonstrable skill.
• Ability to turn a messy client ask into a current-state process map that shows where the real problem sits.
• Ability to write numbered, testable acceptance criteria in Given/When/Then form that an engineer can build from directly.

Comfortable in a client's data: checks it for quality, spots the empty, duplicated, and malformed, and maps what each field means in the business process.

• Ability to write UAT scenarios that test whether the client's problem is solved, and holds the pass or fail line on them.
• Ability to keep a clean record under pressure: decisions, changes, and the reasoning behind both.

Ability to talk to engineers about trade-offs without oversimplifying the build, and recognizes excellent interface work from merely acceptable work well enough to spec for it.

• Works in Bahasa Indonesia and English with client stakeholders.
• Uses AI as leverage across the whole job and verifies its output before it reaches a client or an engineer.
• Work you can show: specifications, process maps, prototypes, or interfaces you shaped.