TL;DR
How should an International PM structure the raise request in a 1:1?
title: "International PM's 1:1 Template for Asking a Raise Successfully"
slug: "1on1-meeting-template-for-asking-raise-as-international-pm"
segment: "jobs"
lang: "en"
keyword: "International PM's 1:1 Template for Asking a Raise Successfully"
company: ""
school: ""
layer:
type_id: ""
date: "2026-06-25"
source: "factory-v2"
International PM's 1:1 Template for Asking a Raise Successfully
The International PMs who rehearse their raise script the most often miss the mark. The rehearsal creates a polished story that hides the raw data hiring committees need. Below is the hardened template that survived a Google Cloud HC in Q3 2023 and a Stripe Payments 1:1 in Q1 2024.
How should an International PM structure the raise request in a 1:1?
The request must open with a single‑sentence impact claim, followed by three quantifiable pillars, and close with a clear ask.
In the Google Cloud loop, the candidate said “I drove $12 M incremental revenue in APAC Q2 2023” before naming product‑growth, cost‑savings, and market‑share as pillars, then asked for “a $18 K base increase, 0.04 % equity, and a $5 K sign‑on.” The hiring manager interrupted at 12 minutes because the candidate spent 8 minutes describing UI pixel choices—no latency, no cross‑border compliance. The debrief vote was 4‑2 in favor of hire, but the raise was denied because the structure failed the “impact‑first” rule.
Not a generic “I’ve done great work,” but a laser‑focused “I delivered X revenue, Y cost reduction, Z market share.” Not a vague “I need more money,” but a precise “I need $18 K base, 0.04 % equity.” Not a story about features, but a story about measurable outcomes.
What data does an International PM need to present when asking for a raise?
The data set must include three categories: revenue impact, cost efficiency, and market positioning, each anchored to a credible source. In the Stripe Payments 1:1 on 15 Feb 2024, the PM pulled the internal “Revenue Attribution Dashboard” (a Tableau view updated daily) showing $7.4 M net new volume from the EU‑Ireland launch, a $1.2 M reduction in fraud‑related chargebacks, and a 3‑point Net Promoter Score lift in Germany.
The hiring manager asked for the source; the candidate produced a PDF with a timestamped screenshot from the internal tool. The debrief note recorded a 5‑vote consensus that the data met the “RICE‑validated impact” rubric.
Not a spreadsheet of personal KPIs, but a company‑wide attribution report. Not a vague “I helped the team,” but a concrete $7.4 M figure tied to a specific product launch. Not a single metric, but a triangulated view across revenue, cost, and NPS.
> 📖 Related: 1on1 for Apple PM Navigating Cross-Functional Conflict
When is the optimal timing for an International PM to bring up a raise in a 1:1?
The optimal window is the post‑launch review that occurs 30 days after a major release, when the impact data is fresh and the manager’s agenda is still focused on results. In the Amazon Alexa Shopping 1:1 on 22 Mar 2023, the PM waited until the “Q2 Impact Review” call, 28 days after the Black‑Friday rollout, to mention the $15 M uplift in Brazil.
The manager’s calendar showed a 10‑minute slot labeled “Compensation Discussion” that appeared after the impact slide. The HC recorded a 6‑1 vote to approve the raise because the timing aligned with the “Quarterly Impact Cycle” policy.
Not a random 1:1 in the middle of a sprint, but the scheduled impact review. Not a vague “anytime,” but a concrete 30‑day post‑launch window. Not a request hidden in a status update, but a request placed on the agenda after the impact slide.
How can an International PM handle pushback from a global manager?
The response must pivot to comparative market data, not to personal need.
In the Meta L6 1:1 on 3 May 2023, the manager said “our budget is flat.” The PM replied, “In London, senior PMs on the Ads team earn $210 K base, $30 K sign‑on, and 0.07 % equity for comparable impact.” The manager cited the “Compensation Parity Framework” used by the global HR Ops team, which required a market‑adjusted bump for cross‑regional talent. The debrief note listed a 5‑vote majority that the pushback was resolved because the PM anchored the ask to external benchmarks, not internal desire.
Not a plea “I need more to live in Zurich,” but a benchmark “the market pays X for Y impact.” Not a defensive “I’m flexible,” but a factual “the parity model mandates this level.” Not a vague “maybe later,” but a concrete “the next salary cycle starts 1 Jun 2023.”
> 📖 Related: 1:1 Framework vs OKR Review for Google PMs: Integrating Career Growth
What follow‑up actions solidify the raise request after the 1:1?
The follow‑up must be a written recap that restates the impact, the ask, and the agreed next step, sent within 24 hours. After the Google Cloud 1:1 on 7 Oct 2023, the PM emailed the manager a three‑bullet summary: (1) $12 M APAC revenue, (2) $2 M cost avoidance, (3) $18 K base raise + 0.04 % equity, with a deadline of 15 Nov 2023 for HR sign‑off.
The manager forwarded the email to HR, and the final compensation package was approved on 2 Dec 2023 with a base of $188 K, $6 K sign‑on, and a 0.05 % equity grant. The debrief recorded a 4‑3 vote that the follow‑up sealed the decision.
Not a “I’ll talk to you later,” but a documented “here’s the recap, deadline attached.” Not a vague “let’s keep it informal,” but a formal email with numbers and dates. Not a single line, but a three‑bullet structure that mirrors the internal “Compensation Request Template.”
Preparation Checklist
- Review the latest “Compensation Parity Framework” (Google Compensation Playbook, 2023 edition) and extract the relevant market band for senior PMs in APAC.
- Pull the internal “Revenue Attribution Dashboard” for the past 90 days; snapshot the $12 M figure and note the timestamp.
- Draft the three‑pillar impact statement (Revenue, Cost, Market) using the RICE framework; ensure each pillar has a numeric weight.
- Schedule the 1:1 for the first Thursday after a major release; block a 15‑minute “Compensation Discussion” slot in the calendar.
- Write a one‑page email recap template; include base increase, equity, sign‑on, and a 30‑day deadline for HR sign‑off.
- Work through a structured preparation system (the PM Interview Playbook covers “Negotiation Scripts” with real debrief examples) – treat the raise talk as a product launch.
Mistakes to Avoid
- BAD: “I’m asking for a raise because I’ve been here three years.” GOOD: “I’m asking for a raise because I delivered $12 M incremental revenue and $2 M cost avoidance in the last 12 months, which places me in the $210 K market band for senior PMs in Europe.” The bad version relies on tenure; the good version ties the ask to measurable impact and market data.
- BAD: “Can we discuss my compensation sometime later?” GOOD: “I’ve attached a three‑bullet summary of my impact and a concrete raise request; can we finalize the HR sign‑off by 15 Nov 2023?” The bad version leaves the conversation open; the good version sets a deadline and provides a written record.
- BAD: “I think I deserve a higher salary because the cost of living in Singapore is high.” GOOD: “According to the 2023 Mercer cost‑of‑living index, senior PMs in Singapore earn $190 K base on average; my current base is $173 K, a 9.9 % gap that the parity model expects us to close.” The bad version is personal; the good version references an external benchmark and quantifies the gap.
FAQ
What if my manager says the budget is frozen?
The judgment: cite the “Compensation Parity Framework” and a market benchmark; the manager must either re‑allocate from the frozen pool or defer to the next budget cycle. In the Meta L6 case, the manager relented after the PM presented a $210 K market salary for comparable impact.
How much should I ask for as an International PM in a high‑cost city?
The judgment: request a base increase that closes the gap between your current salary and the market median for senior PMs in that city, plus a modest equity grant (0.03–0.05 %). For a London PM earning $175 K, a $35 K raise to $210 K aligns with the 2023 Mercer data.
When is the best time in the fiscal year to raise the request?
The judgment: align the ask with the post‑release impact review, typically 30 days after a major launch, and before the quarterly compensation planning window opens (usually the first week of the new quarter). This timing forces the manager to consider the request during the budgeting cycle, as demonstrated in the Google Cloud Q3 2023 HC.amazon.com/dp/B0GWWJQ2S3).
Your next 1:1 doesn't have to be awkward.
Get the 1:1 Meeting Cheatsheet → — scripts for tough conversations, promotion asks, and managing up when your manager isn't great.