In partnership with
Okay, quick gut check: when's the last time your resume made someone stop scrolling? Fall APM season is back! Google, Uber, Instacart, Square, basically every big rotational program and I need to tell you something a little deflating before I get to the good part.
Every resume in that pile is about to look identical. Strong GPA. Relevant coursework. A case competition. A capstone project with a company name someone invented for the assignment. None of it is wrong. None of it is memorable, either.
Why this year is different
Here's what's actually new, and it's the thing I can't stop bringing up when I coach people through this right now: building used to be the hard part. You needed to code, or know someone who could, or burn a summer you didn't have learning Rails.
Not anymore.
I've watched someone go from "I have an idea" to a working, clickable prototype in an afternoon, no code, no cofounder, no summer sacrificed to Stack Overflow. Two years ago, that was a multi-week ask, minimum.
If your APM application is just a resume and a cover letter this fall, you're not behind because you lack the skills. You're behind because the tools sitting right in front of you are still just sitting there, unused.
A built thing does something a bullet point never will. It proves you can take a fuzzy "this is annoying" feeling and turn it into something specific enough to actually ship. That's the whole job, shrunk down to one afternoon. Not "I want to be a PM", a demonstrated instinct for spotting a real problem and doing something about it before anyone asked you to.
Write docs 4x faster. Without hating every second.
Nobody became a developer to write documentation. But the docs still need to get written — PRDs, README updates, architecture decisions, onboarding guides.
Wispr Flow lets you talk through it instead. Speak naturally about what the code does, how it works, and why you built it that way. Flow formats everything into clean, professional text you can paste into Notion, Confluence, or GitHub.
Used by engineering teams at OpenAI, Vercel, and Clay. 89% of messages sent with zero edits. Works system-wide on Mac, Windows, and iPhone.
How to come up with the idea
Not a hypothetical one. Something that's actually annoyed you — recently, specifically, embarrassingly small.
Brainstorm ideas that solve a genuinely frustrating problem.
A tracker for some weird recurring cost only you seem to have. A tiny scheduler for a hobby league. The thing you complain about to your roommate every single week.Build and iterate, fast, with something like Lovable, Claude Code, or Replit.
Don't polish it! Polishing isn't the assignment here. Get something clickable, put it in front of a stranger, wince, repeat.
Show it to real users. Yes, that includes posting it on LinkedIn.
I know. It feels deeply uncool the first time. Post it anyway. Reddit and Product Hunt work too, if you want a slightly less exposed version, and they'll hand you a much ruder crowd, which is genuinely useful. A little cringe is a small price for reactions from people who owe you zero politeness.Prioritize the feedback. Don't take any of it at face value.
Everyone skips this step, and it's the one that actually separates a PM instinct from a builder instinct. A comment isn't feedback yet, it's a clue. "I'd never use this" might mean the feature's wrong. It might just mean you haven't explained the problem yet. Trace every comment back to the job the person's actually trying to get done, and only act on the feedback that survives the trip.
Once it's built and pressure-tested, package it
You've got a real problem, a working thing, and feedback you've actually filtered. Now pitch it. Five parts, in this order, the order is doing work, walking your reader through your thinking the same way you walked yourself through it.
Target users: Not "everyone who struggles with X." One specific person. Who exactly is this for, and how do you know they're real?
Pain point: The actual friction, described the way the person living it would describe it, not the way a job posting would. "I lose track of X and it costs me Y" beats "inefficient workflow," every single time.
Gap in the market: What already exists, and precisely what it doesn't do. Most people go generic here. Name the real alternative. Name what it's missing. Be exact.
AI tools you used: Lovable, Replit, Claude Code, whatever got you from idea to working thing, name them. This isn't a footnote, it's part of the proof. Knowing which tool to reach for is its own product skill.
Success metrics: Even a tiny one. Even "12 people used it, 4 came back the next day." A number beats an adjective, always, everywhere, not just here.
The pitches that stall almost always stall on step one. Vague users make everything downstream vague too. Fix that first.
This week, write down one thing that's genuinely annoyed you in the last month, something small enough that you've never bothered mentioning it to anyone. That's your target user, your pain point, and your gap in the market, all sitting in one sentence. Open Lovable, Replit, or Claude Code this weekend and see how far you get in an afternoon.
1,000+ Claude Prompts Top Professionals Actually Use at Work
Claude can be your analyst, editor, and strategist.
But most professionals are using it to fix grammar.
These 1,000+ Claude prompts take it from grammar tool to your most powerful AI work assistant.
Sign up for Superhuman AI and get:
1,000+ ready-to-use Claude prompts to get real work done in minutes — researched, tested, and used by professionals at Google, Microsoft, and NASA
Superhuman AI newsletter (4 min daily) so you keep learning new AI tools and skills to stay ahead in your career — the prompts are just the beginning
If you're applying to an APM program this fall, hit reply and tell me what you're thinking of building. I want to know what's actually annoying you enough to fix it.
P.S. If you've got an idea but you're stuck on whether it's "good enough" to pitch, that hesitation is exactly the kind of thing worth talking through before you spend a weekend building the wrong thing. Lets book time together! Bring the rough idea, we'll shape it together before you open the tools.