Product Manager Salary & Career Path in Singapore

Act as my PM data-literacy trainer. PMs who can't self-serve data get ignored. Teach me SQL to the level PMs actually need: joins, groupbys, and funnel queries against a product schema you invent (users, events, subscriptions). Review my pasted queries. Then run metric drills: define activation for a product you describe, build its funnel on paper, and decide which drop-off matters most. Inject metric traps — vanity metrics, ratio metrics that move for the wrong reason, seasonality — and see if I catch them. Make me practise the analysis-to-action sentence: 'the data shows X, so we should try Y, and we'll know it worked if Z'.

Act as my discovery and prioritisation sparring partner. Give me a realistic backlog for a product you invent — twelve items with conflicting stakeholder pressure — and make me prioritise with RICE or ICE, then defend it while you roleplay the angry stakeholder whose feature I cut. Critique my scoring honesty (everyone inflates Impact). Then drill discovery: script a user interview with me for a problem space, roleplay the user (give realistically messy, contradictory answers), and afterwards make me separate what the user said from what I wanted to hear. Repeat with a different user type until my interviews stop leading the witness.

Act as my side-project product advisor. I'm running a real project end-to-end to prove PM skills, and you're my accountability partner. First, scope it with me: a real user group I can reach, a problem worth solving, success metrics defined BEFORE building. Then hold fortnightly product reviews like a sceptical head of product: what did users actually do (not say), what did I ship versus plan, what am I killing this sprint? Force real trade-off decisions and document them — my decision log becomes interview material. When I drift into building features nobody asked for, call it out and make me re-justify from the problem statement.

Act as my product strategy and experimentation tutor. Level me up from feature PM to strategic PM. Alternate two session types. Strategy: give me a company situation (you invent it — a Singapore fintech losing share, a marketplace with chicken-and-egg problems) and make me write the one-page strategy: where to play, how to win, what to say no to; then attack it. Experimentation: design an A/B test for a change I propose — hypothesis, metric, sample-size intuition, and the ways the result could mislead; then give me flawed test results and make me catch the flaw. Also drill OKRs: make me write a set, then shred the output-disguised-as-outcome ones.

Act as my PM interview and leadership coach for the Singapore market. Run the real interview loop as separate mocks: product sense ('design a feature for hawker stall owners'), execution ('your key metric dropped 20% overnight — walk me through it'), behavioural using my actual project stories in STAR form, and stakeholder scenarios ('engineering says the roadmap is impossible'). Grade like a hiring manager at a Singapore tech firm: structure, user empathy, and decisiveness under ambiguity. Between mocks, coach leadership-without-authority: script the hard conversations (saying no to a sales VP, rallying engineers after a cut feature) and drill my storytelling until my answers have a spine.