> Key facts, checked November 2026

>

> - Product Manager, Regulatory in Toronto: $93,500 - $110,000 CAD

> - Senior Product Manager, Advisor Marketplace in Zone 1: $166,000 - $195,000 USD

> - Staff Product Manager, Banking in Zone 1: $191,000 - $225,000 USD

TL;DR

The single most useful number is the $225,000 USD upper bound in the Staff Product Manager, Banking Zone 1 posting, because it gives you a clear posted ceiling for that exact title and location group. For most US senior candidates, the more relevant anchor is the range printed for their own city, not a company-wide average. Treat every figure in this article as posted base pay only and negotiate the full offer rather than one number.

Who This Is For

  • You are applying for a Product Manager, Senior Product Manager, or Staff Product Manager opening covered by the postings checked for this article.
  • You know your job location and want to find the range assigned to that location instead of relying on a generic company-wide figure.
  • You are interviewing in Canada and need to keep CAD figures in CAD while reviewing US postings in USD.
  • You are comparing employers or role titles and need a source-first reference: ProductPlan, What is Product Management makes the basic point that the PM role definition varies by company.

What Robinhood Posted for PM Roles in November 2026

Role Location Posted base range Source link
Product Manager, Regulatory Toronto, Canada Toronto, ON $93,500 - $110,000 CAD Job posting
Senior Product Manager, Advisor Marketplace Menlo Park, CA; New York, NY Zone 1 (Menlo Park, CA; New York, NY; Bellevue, WA; Washington, DC) $166,000 - $195,000 USD<br>Zone 2 (Denver, CO; Westlake, TX; Chicago, IL) $146,000 - $172,000 USD<br>Zone 3 (Lake Mary, FL; Clearwater, FL; Gainesville, FL) $129,000 - $152,000 USD Job posting
Senior Product Manager, Capital Markets Menlo Park, CA; New York, NY Zone 1 (Menlo Park, CA; New York, NY; Bellevue, WA; Washington, DC) $166,000 - $195,000 USD<br>Zone 2 (Denver, CO; Westlake, TX; Chicago, IL) $146,000 - $172,000 USD<br>Zone 3 (Lake Mary, FL; Clearwater, FL; Gainesville, FL) $129,000 - $152,000 USD Job posting
Senior Product Manager, Crypto Wallet Menlo Park, CA; New York, NY Zone 1 (Menlo Park, CA; New York, NY; Bellevue, WA; Washington, DC) $166,000 - $195,000 USD<br>Zone 2 (Denver, CO; Westlake, TX; Chicago, IL) $146,000 - $172,000 USD<br>Zone 3 (Lake Mary, FL; Clearwater, FL; Gainesville, FL) $129,000 - $152,000 USD Job posting
Senior Product Manager, Gold Growth Menlo Park, CA; New York, NY Zone 1 (Menlo Park, CA; New York, NY; Bellevue, WA; Washington, DC) $166,000 - $195,000 USD<br>Zone 2 (Denver, CO; Westlake, TX; Chicago, IL) $146,000 - $172,000 USD<br>Zone 3 (Lake Mary, FL; Clearwater, FL; Gainesville, FL) $129,000 - $152,000 USD Job posting
Senior Product Manager, Money Movement Experiences Menlo Park, CA; New York, NY Zone 1 (Menlo Park, CA; New York, NY; Bellevue, WA; Washington, DC) $166,000 - $195,000 USD<br>Zone 2 (Denver, CO; Westlake, TX; Chicago, IL) $146,000 - $172,000 USD<br>Zone 3 (Lake Mary, FL; Clearwater, FL; Gainesville, FL) $129,000 - $152,000 USD Job posting
Senior Product Manager, Trading Tools Menlo Park, CA; New York, NY Zone 1 (Menlo Park, CA; New York, NY; Bellevue, WA; Washington, DC) $166,000 - $195,000 USD<br>Zone 2 (Denver, CO; Westlake, TX; Chicago, IL) $146,000 - $172,000 USD<br>Zone 3 (Lake Mary, FL; Clearwater, FL; Gainesville, FL) $129,000 - $152,000 USD Job posting
Staff Product Manager, Banking Menlo Park, CA; New York, NY; Washington, DC Zone 1 (Menlo Park, CA; New York, NY; Bellevue, WA; Washington, DC) $191,000 - $225,000 USD<br>Zone 2 (Denver, CO; Westlake, TX; Chicago, IL) $168,000 - $198,000 USD<br>Zone 3 (Lake Mary, FL; Clearwater, FL; Gainesville, FL) $150,000 - $176,000 USD Job posting
Staff Product Manager, Canada Expansion Toronto, Canada Toronto, ON $191,250 - $225,000 CAD Job posting

I read these live postings through the public Greenhouse job board API in early November 2026, and postings change, so I would reopen each source before relying on a number. The most important distinctions in the table are currency and location group: the Toronto figures are in CAD, while the US postings print USD ranges by zone. Every range shown is labeled base pay, and the senior US postings repeat the same three-zone structure while the staff US posting uses a higher three-zone structure.

How to Read a Posted Range

Start with the role title. The postings use Product Manager, Senior Product Manager, and Staff Product Manager, but they do not include a written leveling rubric. My rule of thumb is to treat the title as the level label for that posting and avoid inventing a universal scope definition from it.

Next, read the location wording exactly. The US postings divide named cities into Zone 1, Zone 2, and Zone 3, and each zone has its own base range. I treat those zones as location groupings because the posting defines them by city, and I would ask the recruiter to confirm which zone applies to my working location instead of guessing.

Then separate base pay from the rest of the offer. Plainly, the posting shows base only unless stated otherwise. The pay language points readers to Total Rewards that vary by region and entity, but the quoted ranges are base pay, and the provided posting text does not state an equity amount or a bonus amount. I would therefore not present any range in this article as total compensation.

If the final offer includes stock options, stock option tax treatment is set by IRS rules, so check IRS Topic 427, Stock Options before choosing equity. My opinion is to treat the tax question as a separate decision from the base-pay question, because a larger number on one part of the offer is not automatically the better package.

I use one principle from Harvard Business Review, 15 Rules for Negotiating a Job Offer: negotiate the whole offer, not one number. My rule of thumb is to make one clear base-pay request, then ask which other components are available and whether any of them can move. That keeps the conversation specific without making a claim the posting does not support.

A Negotiation Script You Can Use

I would send the written version before the call so the recruiter can see the request and the details in front of them. Replace every bracketed field, write your target in the same currency as the posting, and link the exact job posting you reviewed.

Word-for-word email

`text

Subject: Product Manager offer: base pay and total rewards

Hi [Recruiter Name],

Thank you for the offer for the [Role Title] position in [City].

I reviewed the posted base pay range for that role and location: [posted range and posting link]. My current base salary is [current base salary], and I am asking whether there is flexibility to bring the base pay closer to [target base salary].

I also want to understand all of the other components of the offer, including equity and bonus if they apply, so I can evaluate the package as a whole. Could we review the complete offer and discuss what can be adjusted?

Thank you,

Johnny Mai

`

60-second phone version

`text

Hi [Recruiter Name], I want to make sure we are aligned on compensation for the [Role Title] role.

I reviewed the posted base range for my location: [posted range]. My current base is [current base salary], and I am asking whether you can move the base toward [target base salary].

I also want to understand every other part of the offer, including equity and bonus if they apply, so I can look at the complete package. What flexibility is there on base, and what other parts of the offer could you adjust?

Thank you.

`

After the call, my opinion is to send a short written summary of what you asked for and what the recruiter said they would take back. That does not create a commitment; it simply gives both sides a clear record of the conversation.

Mistakes to Avoid

My opinion is that these are the five mistakes I would avoid when using posted PM ranges in a negotiation:

  • Treating the band as a guaranteed outcome. A posted range is a reference point, not an offer or a promise about where your salary will land.
  • Talking only about base pay. If the recruiter has flexibility in another component, you will not know if you never ask, and a base-only discussion gives you less information.
  • Comparing CAD and USD as if they were the same number. Keep the currency visible in your notes and do not treat the Toronto figures as direct USD equivalents.
  • Assuming every zone fits your location. The posting names the cities in each zone, so confirm your city rather than selecting a band by habit or reputation.
  • Opening with a demand and no context. Give a clear target, explain the relevant part of your background in a sentence or two, and ask what the recruiter can adjust.

Preparation Checklist

My opinion is to work through this list before you accept a call about compensation:

  • [ ] Save the exact job posting link for the role you are discussing.
  • [ ] Write down the role title and the locations named in the posting.
  • [ ] Record the posted range in its original currency without converting it.
  • [ ] Copy the relevant zone wording exactly, including every city listed in that zone.
  • [ ] Write your current base salary in the same currency as the posted range.
  • [ ] Choose one target base salary and write a short reason for it.
  • [ ] List the equity, bonus, and other offer components you need explained.
  • [ ] Reopen the posting, update any changed numbers, and rehearse both scripts aloud.

FAQ

Q1. Are these Robinhood PM salary ranges base pay or total compensation?

They are posted base pay ranges. Plainly, the posting shows base only unless stated otherwise, and the pay text included here does not state an equity amount or a bonus amount. A full offer discussion should cover the whole package rather than assume these figures represent total compensation.

Q2. Why do the senior product manager postings show different ranges by location?

Each posting assigns named cities to zones and prints a base range for each zone. The text explains the city groupings, but it does not provide a formula for the differences. Confirm your location and zone with the recruiter, and use the matching posted band in your notes.

Q3. Can I compare the Toronto CAD range directly with the US USD ranges?

Not as if they were identical amounts. The Toronto postings are in CAD and the US postings are in USD, and I have not converted them here. My opinion is to evaluate each posting in its stated currency and factor in where you will actually live and work.

Q4. Should I ask for the top of the posted range?

My opinion is to treat the top of the range as a reference point, not an entitlement. I would make a specific base-pay request tied to my background, ask what else can move, and ask for the complete package to be reviewed. A clear question gives the recruiter more to work with than a demand to pay the highest number on the page.

If you want a broader preparation system before the offer conversation, I wrote The 0 to 1 PM Interview Playbook, 2026 Edition (Kindle) to help you prepare the product thinking, stories, and compensation discussion as one connected process.

Related Reading