TL;DR

Iterable promotes product managers on an 18-24 month cycle, with level jumps from PM1 to PM2 typically taking 18 months and PM2 to PM3 requiring 24+ months with demonstrated leadership beyond your product scope. The promotion process runs quarterly with HC reviews in March, June, September, and December. Compensation increases range from 12-20% for level promotions, with equity refresh grants of $50K-$150K vesting over 4 years. Success depends on showing outcomes ownership, not just output delivery.

Who This Is For

This guide is for current product managers at Iterable with 2-7 years of PM experience who are preparing for or actively pursuing a promotion to the next level. It assumes you work at a mid-stage B2B SaaS company (Series C through pre-IPO) with 200-800 employees. If you're a PM1 looking to reach PM2 in the next promotion cycle, or a PM2 gunning for PM3, this provides the specific timeline, criteria, and preparation framework you need. This is not for PMs at large public companies—those processes differ materially.

What Is the Typical PM Promotion Timeline at Iterable

The standard promotion timeline at Iterable follows an 18-24 month cycle per level, with the actual promotion effective date landing in the quarter following your HC review.

The promotion cycle operates on quarterly HC meetings held in March, June, September, and December. Your manager must submit your promotion packet 4-6 weeks before the HC meeting. This means if you're targeting a March promotion, your materials go in by early February. Most PMs at Iterable achieve one level jump every 18-24 months, though high-performers have compressed this to 15 months.

The timeline breaks down as follows: your manager initiates the conversation 60-90 days before the submission deadline. You then spend 2-3 weeks building your promotion packet—quantifying impact, gathering peer feedback, and documenting cross-functional leadership. The HC reviews your packet, and you receive the outcome 5-10 business days after the meeting. If approved, the promotion and compensation change take effect at the start of the next payroll cycle.

The first counter-intuitive truth about Iterable's promotion timeline: it's not when you hit your numbers that matters, it's when your manager starts building the narrative. I've seen PMs who exceeded their goals in Q2 but missed the September HC because their manager hadn't done the stakeholder pre-briefing. The timeline is fixed; your job is to align your narrative construction to it, not your results.

What Are the Level Expectations for PM1, PM2, and PM3 at Iterable

PM1 at Iterable is an individual contributor role requiring 0-3 years of experience. You own a feature area or small product module, execute against defined OKRs, and work closely with engineering and design to ship. The expectation is delivery reliability—you hit your commitments 80% of the time and learn from the misses.

PM2 is a senior IC role requiring 3-5 years of experience. You own a full product area with P&L responsibility or significant metric ownership. You're expected to drive your roadmap independently, mentor junior PMs, and influence cross-functional partners without needing managerial leverage. The shift from PM1 to PM2 is the biggest jump—you go from executing someone else's strategy to building your own.

PM3 is a principal or staff-level role requiring 5-8+ years of experience. You lead product strategy for a major platform capability or line of business. You set OKRs for your area, influence company strategy, and your work directly impacts board-level discussions. Only 15-20% of PMs reach PM3 at Iterable, and many do so by transitioning to a management track.

The second counter-intuitive truth: the difference between PM2 and PM3 isn't more output—it's different output. PM2s who try to double down on shipping more features stall. PM3s demonstrate strategic judgment: they kill features, redirect engineering resources, and influence product decisions outside their direct ownership. The HC looks for evidence that you've expanded your sphere of influence beyond your job description.

How Does Iterable Evaluate PM Performance for Promotion

Iterable uses a structured rubric across four dimensions: product impact, execution excellence, cross-functional leadership, and craft mastery.

Product impact accounts for 40% of the evaluation. This is metric delta—revenue growth, engagement improvement, or efficiency gains directly attributable to your product decisions. The HC wants to see a clear before-and-after with your fingerprints on the causal chain. Vague statements like "improved the user experience" don't move the needle. Specific metrics do: "Led the redesign that increased activation rate from 23% to 41%, driving $2.1M incremental ARR."

Execution excellence is 25% of the evaluation. This measures your ability to ship on time, manage scope, and navigate trade-offs. The HC looks for consistent delivery patterns—not one great quarter followed by a miss, but sustained reliability across multiple release cycles.

Cross-functional leadership is 20% of the evaluation. This isn't about being liked; it's about driving alignment. The HC wants to see evidence that you can get engineering, design, marketing, and sales moving in the same direction without escalating to your manager. Specific examples: you resolved a scope conflict with engineering, you aligned marketing on a launch narrative, you influenced a pricing decision outside your product area.

Craft mastery is 15% of the evaluation. This covers your technical fluency, product sense, and operational rigor. Do you write clear PRDs? Do you understand the technical architecture of your product? Do you run effective discovery?

In a Q3 debrief I observed, a hiring manager pushed back on a PM2 promotion because the candidate had strong execution numbers but no cross-functional leadership evidence. The HC rejected the packet. The lesson: you need evidence in all four dimensions, not just the first two.

What Compensation Increases Accompany PM Promotions at Iterable

PM promotions at Iterable come with meaningful compensation increases, though the structure varies by level and tenure.

Moving from PM1 to PM2 typically increases base salary from $140,000-$160,000 to $170,000-$195,000, a 15-20% jump. Equity refresh grants add $75,000-$100,000 in new options vesting over 4 years. Total compensation increases by $40,000-$60,000 at the point of promotion.

The PM2 to PM3 jump is larger in absolute terms but more variable. Base salary moves to $210,000-$250,000, with equity refresh grants of $100,000-$150,000. Total compensation at the PM3 level ranges from $280,000-$350,000 depending on tenure and performance rating.

Iterable's equity refresh policy grants new options every 18-24 months based on performance. High performers receive larger refresh grants, sometimes doubling the standard amount. The equity component matters more at PM3 level because the vesting schedule creates long-term wealth acceleration.

The third counter-intuitive truth: the promotion raise is less important than the subsequent performance review increase. PMs who focus solely on the promotion bump miss the compounding effect of higher performance ratings on subsequent annual increases. A PM3 with a top rating gets 8-12% annual increases versus 3-5% for meets-expectations PM2s. The level matters more than the promotion event.

What Mistakes Kill PM Promotion Chances at Iterable

The most common promotion-killing mistake is presenting team results as individual results. The HC has access to 360 feedback and will verify your claims. If your promotion packet credits you with a feature that three other PMs contributed to, you'll get caught. This isn't just an integrity issue—it's a judgment signal. The HC asks: if you're exaggerating now, what else are you hiding?

The second mistake is waiting too long to have the promotion conversation. PMs who approach their manager three weeks before the submission deadline signal poor planning. Your manager needs time to build internal consensus, brief key stakeholders, and construct the narrative. The ideal time to start the promotion conversation is 90 days before the HC meeting—during the quarter before you want to promote.

The third mistake is focusing on activity instead of impact. "Shipped 12 features" is an activity metric. "Increased feature adoption from 34% to 52% by redesigning the onboarding flow" is an impact metric. The HC evaluates outcomes, not output. Your packet should be 70% impact statements and 30% context.

How Should I Prepare for a PM Promotion Cycle at Iterable

Preparation starts with逆向 engineering the rubric. Pull the four evaluation dimensions and map your last 18 months of work against each one. Identify gaps—you need evidence in all four areas, not just the ones where you're strongest.

Build your evidence portfolio systematically. For product impact, quantify your contributions with specific metrics. For execution excellence, document your shipping track record with release notes and timeline adherence. For cross-functional leadership, collect specific examples of alignment work: scope negotiations, cross-team projects, stakeholder influence. For craft mastery, gather examples of clear documentation, technical depth, and operational rigor.

Gather external validation before your manager submits. Talk to engineering leads, design partners, and marketing stakeholders. Get informal buy-in on your narrative. This isn't politicking—it's ensuring the HC receives consistent signals from multiple sources.

The final preparation step is the mock HC. Your manager should walk you through a simulated hiring committee, challenging your evidence and testing your narrative. If you can't defend your packet under pressure, you're not ready.

Preparation Checklist

  • Map your 18-month work history against the four evaluation dimensions: product impact (40%), execution excellence (25%), cross-functional leadership (20%), craft mastery (15%)
  • Quantify product impact with specific metrics: revenue delta, engagement improvement, efficiency gains. Replace vague statements like "improved user experience" with "increased activation rate from 23% to 41%"
  • Gather 360 feedback from engineering leads, designers, and cross-functional partners 60 days before the submission deadline
  • Build a promotion packet with 5-7 specific examples across all four dimensions, each following the situation-action-result format
  • Start the promotion conversation with your manager 90 days before the HC meeting, not 30 days before
  • Prepare a mock HC session where your manager challenges your evidence and tests your narrative under pressure
  • Review your equity refresh grant schedule and understand how promotion timing affects your vesting
  • Work through a structured preparation system (the PM Interview Playbook covers promotion narrative construction with real HC debrief examples) to ensure your packet follows the specific format Iterable HCs expect

Mistakes to Avoid

BAD: Presenting team results as individual results. Claiming credit for features built by three other PMs will get you caught in 360 feedback and signal poor judgment to the HC.

GOOD: Clearly attribute team contributions in your packet. Say "led the cross-functional team that built X" rather than "built X." The HC respects accurate attribution more than inflated claims.

BAD: Waiting until three weeks before the deadline to start the promotion conversation. This signals poor planning and doesn't give your manager time to build internal consensus.

GOOD: Initiate the promotion conversation 90 days before the HC meeting. Give your manager time to brief stakeholders, gather input, and construct a compelling narrative.

BAD: Leading with activity metrics ("shipped 12 features") instead of impact metrics ("increased adoption 18 percentage points, driving $1.4M incremental revenue").

GOOD: Frame every accomplishment in terms of measurable outcomes. The HC evaluates delta, not volume.

FAQ

How long does it take to get promoted from PM1 to PM2 at Iterable?

The typical timeline is 18 months, though high-performers have compressed this to 15 months. You need demonstrated impact across all four evaluation dimensions, with particular emphasis on product impact (40%) and execution excellence (25%). The promotion takes effect in the quarter following your HC review—March, June, September, or December.

What percentage increase should I expect with a PM promotion at Iterable?

PM1 to PM2 promotions typically increase base salary by 15-20% ($140K-$160K to $170K-$195K) plus equity refresh grants of $75K-$100K. PM2 to PM3 promotions increase base by 18-25% ($170K-$195K to $210K-$250K) with equity refresh of $100K-$150K. Total compensation increases by $40K-$60K at the PM1-PM2 level and $60K-$100K at the PM2-PM3 level.

What happens if my promotion is rejected at Iterable?

If the HC rejects your promotion, you'll receive specific feedback on which dimensions were underweight. The typical path is to address the gap and resubmit in the next cycle (3-6 months later). Rejection isn't terminal—it's information. The key is understanding exactly what evidence was missing and building it systematically. Most PMs who are rejected on first attempt succeed within two cycles.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.