Write something
Pinned
May 5 •
🎯 START HERE: Read this first
Hey, and welcome. Really glad you're here. This community is for people making the real pivot into PM, not the LinkedIn version, the actual version. The part where you're questioning your background, rewriting your resume for the 5th time, and wondering if you're even qualified. You are. Let's make sure hiring managers see it. --- Here's how to get started: 1. Go to 👋 Introductions and drop a post. Tell us: your current background, what PM role you're targeting, and the one thing you're most stuck on right now. 2. Ask your first question in 🎯 Ask Stef. Post anything you'd normally Google at 11pm while spiraling about your job search. I read everything and answer here. 3. Share your work in 📝 Portfolio & Interview Prep. Post your resume, your interview answers, your cover letters. Get real feedback, not generic advice. 4. Celebrate in 🎉 Booyah! Wins. Everything from "I finally sent that application" to "I got the offer." We celebrate both. --- A few things I want to be upfront about: This is a small community by design. I'm not trying to build an audience here — I'm trying to build a room where people actually get hired. That means real feedback, real conversations, and me actually being here. If you have a question, post it. — Stef
7d •
📋 This Week’s Case Study: The Roadmap Nobody Agrees On
The Scenario: You’re 6 weeks into a new PM role. Three requests are competing for next sprint: - Sales wants a bulk export feature. Two enterprise deals are “blocked” on it (per your AE). - Support wants a fix for a permissions bug. It’s generating repeat tickets but no churn yet. - Your eng lead wants to pay down tech debt in the same area both features touch. You have capacity for one. Everyone thinks their thing is obviously the priority. The Prompt: Walk through how you’d actually decide. Not just which one you’d pick, but how you’d get three stakeholders to trust the call, especially six weeks in when you don’t have credibility built up yet.
0
0
16d •
💼 PM Jobs This Week — as of July 31st, 2026
Fresh roles across entry-to-senior levels | Scanned 2026-07-31 | Roles posted in the last 7 days | Regions: 🇺🇸 US · 🇨🇦 Canada · 🇲🇽 Mexico · 🇬🇧 UK · 🇪🇸 Spain · 🇩🇪 Germany · 🇳🇱 Netherlands · 🇮🇪 Ireland · 🇫🇷 France · 🇸🇪 Sweden ━━━━━━━━━━━━━━━━━━━━ 🟣 PRODUCT-ADJACENT ROLES (for building experience toward PM) Role: Principal Technical Product Manager, Data Platform Company: SandboxAQ Location: 🇨🇦 Canada — Remote Salary: CA$136,000–CA$240,000 Who This Is For: For senior TPMs wanting principal-level data-platform ownership at a fast-growing quantum/AI spinout, fully remote. Apply: https://www.linkedin.com/jobs/view/4435930175 -- Role: Technical Product Manager, Core Platform Company: Caseware Location: 🇨🇦 Toronto, ON — Hybrid Salary: $130,000–$140,000 Who This Is For: For TPMs wanting API/integrations-heavy platform ownership at an AI-powered audit/fintech software company. Apply: https://hiringcafe.com/job/technical-product-manager-core-platform-caseware-toronto-ontario-d6m2ozfvzsqmmtzp ━━━━━━━━━━━━━━━━━━━━ 🟢 ENTRY LEVEL / ASSOCIATE PM (0–3 years) Role: Associate Product Manager Company: Modine Manufacturing Company Location: 🇺🇸 Buena Vista, VA — On-site Who This Is For: A fresh "associate" posting at an established industrial manufacturer — solid first-PM resume line. Apply: https://www.linkedin.com/jobs/view/4430771932 -- Role: Associate Product Manager Company: Littelfuse Location: 🇲🇽 Matamoros, Tamaulipas — On-site Who This Is For: For early-career PMs wanting hardware/electronics exposure at a global component manufacturer in Mexico. Apply: https://www.linkedin.com/jobs/view/4427396725 ━━━━━━━━━━━━━━━━━━━━ 🟡 MID-LEVEL PM (3–6 years) Role: Manager, Product Company: TELUS Digital Location: 🇺🇸 Durham, NC — Hybrid
0
0
21d •
📋 This Week’s Case Study: The Complaint Everyone’s Ignoring
The Scenario: You’re the PM for a project management tool used by small agencies. Over the past three weeks, support tickets mentioning “can’t find my old files” have quadrupled. Nobody flagged it as urgent because each ticket gets resolved individually (a support rep manually helps the user search). Churn hasn’t moved. NPS hasn’t moved. But your Head of Support pulls you aside and says “something’s off, I just can’t prove it yet.” The Prompt: What do you do in your first week with this signal? Walk through how you’d investigate it, what you’d look for, and what “worth building something” would actually look like versus “not yet.” How to Approach It: 1. Clarify the signal. What’s actually being reported? Don’t assume “search is broken.” Find the pattern underneath the pattern. 2. Size it. A quadrupling of a small number can still be a small number. What would make this matter? 3. Decide, don’t default. Not every spike needs a roadmap slot. What’s the smallest next step that tells you more? What a Strong Reply Includes: - A guess at what you’d actually go look at first (tickets, session recordings, a specific report) - One hypothesis for what’s really going on, not five - One honest answer to “and if it turns out to be nothing?”
0
0
23d •
Introducing myself
Hi everyone! I'm Chris, a Senior Producer based in Berlin with 7 years leading cross-functional teams shipping F2P titles across PC, mobile, and console, plus 5 years in digital project management and frontend dev before that. In my recent roles I increasingly used product management thinking as a decision filter, putting the user first to achieve better outcomes (and save my developer's sanity), and realized I want to continue building those skills. Now looking to transition. Right now I'm focused on two things: reframing my CV to showcase product experience, and practicing until PM vocabulary and thinking flow naturally in interviews. Looking forward to learning with you all!
1-30 of 46
powered by
skool.com/stef-the-pm-3369
Break into PM or level up in it. Community and courses built for where you actually are in your product career. Free to join.
Suggested communities
Powered by