What are you seeing in the PMs who are actually getting hired right now? What has changed about the role? And how do you assess for it differently than you used to?

We’ve been asked some version of this in almost every intro conversation this year. What has changed is the kind of evidence a founder will accept as proof that you can do the job. Most candidates are still preparing to prove the old thing.

This article goes into what founders are testing for instead. Let’s jump in.

Founders Now Test Judgment, Not Process

For most of the last decade, a PM interview tested process. Could you structure an ambiguous prompt, name a framework, define a metric, and sequence a roadmap. That worked when running the process was the scarce part of the job.

It is not scarce anymore. Atlassian surveyed more than a thousand product professionals for its first State of Product report and found that the areas where AI saves PMs the most time are concentrated in documentation, market research, and analysis. Those are the exact artifacts PM interviews used to grade.

So founders moved the test. Productboard’s CPO survey found 59% of product professionals now rank strategy and business acumen as the most important skills for the next 2-3 years. Atlassian described the shift as moving from owner of the roadmap to architect of impact. Marty Cagan has been making the same argument for two years, which is that AI removes the performative parts of product management and leaves judgment as the only thing left to evaluate.

The founder we met in that office described exactly what he screens for. He wants a PM who thinks about their product surface the way a CEO thinks about the business. He was direct that the tactical work is being automated and that he needs someone operating above it. Then he defined product taste as something you acquire by closing loops. Form a hypothesis, ship it, find out whether it worked, and let that train your instincts over time. He screens for whether a candidate has closed that loop repeatedly over whether they can describe the concept well.

And when it comes to working with a higher velocity engineering team, the important PM skills move to decision quality, positioning, and to whether anyone is willing to kill something that is already half built. ProductPlan’s 2026 read named this scarce skill as the confident no, which is only worth something if you can hold it with evidence.

You can ship almost anything now, so shipping fast stopped being a differentiator. The PMs getting hired are the ones who can explain what they chose not to build and why the product is better for it.

What Has Changed In The Evaluation Process

The skills founders want haven’t changed. What counts as proof of those skills has. Three shifts show up across almost every product search we run right now.

Growth Intensity Beats Brand Names

Founders still use recognizable companies as a top of funnel filter. What changed is how fast the logo is disregarded once the conversation starts.

In that same founder conversation, one of the executives pushed back on her own target company list in real time. Her argument was that great people end up at companies with bad outcomes, and that what she actually wanted was someone who had lived through running out of resources because the business was growing too fast. She said she would take a PM from a startup that failed but grew hard over a PM from a recognizable, slower company. Nobody in the room disagreed.

What they are buying is evidence that you have operated without a full supporting cast, under real ambiguity, with growth pressure forcing the tradeoffs. Plenty of candidates say they want early stage. Founders have gotten very good at telling the difference between wanting it and having done it.

The AI Question Is Now About Where You Didn’t Use It

Last year, the AI question was whether you had shipped anything with a model. That question is dead because everyone now answers yes.

Founders now ask where you decided not to use it. They want to hear about evals, what failure modes you designed for, how you measured quality on a probabilistic system, and where you kept a human in the loop on purpose. The founder in that meeting said the candidate he is trying to screen out is the one who is completely AI-pilled and outsources thinking. The candidate he wants knows precisely where their own leverage is highest.

GTM Is Now Part Of The Role

At the senior level, founders are scoping product roles to include go-to-market ownership. In that intro conversation, the entire difference between the two levels they were hiring came down to commercial reach. The more senior seat owned pricing, packaging, positioning, and messaging for what it shipped. The other seat owned a defined problem inside an existing surface and nothing beyond it.

This is not specific to one company. Userpilot’s 2026 trends analysis named go-to-market as the part of the job that compresses least under AI, because it requires reading a room, translating between customer language and engineering constraints, and owning a funnel end to end. Someone has to own that, and it is landing on product.

If your last three years were writing requirements and running ceremonies, this is the gap that ends your candidacy in a screen without anyone telling you why.

How To Approach Interviewing For A PM Role

1. Lead with an ambiguous problem you solved end-to-end at an early-stage or growth startup. Startup founders want to see startup experience. Walk through a product from the ambiguous problem definition to the metric it moved, and include the tradeoff you made and the thing you got wrong. Founders are listening for the closed loop. A story with no mistake in it sounds rehearsed, and a story where you were given the guardrails is too structured for a startup.

2. Describe your work in revenue, retention, and win rates rather than features shipped. Practice explaining your product areas and experience the way you would explain it to your own CEO. If you cannot connect your surface to the business in two sentences, that gap shows up fast, and founders will notice.

3. Prepare one AI answer that includes a human boundary. What you shipped, how you evaluated quality, what failure mode you designed for, and the piece you deliberately left to a human. The boundary is the part that separates you, so be clear and opinionated about where human judgement is needed.

4. Know what actually drove the roadmap where you worked. Founders are looking for PMs who figured out what to do without being told. That said, not everyone has had that opportunity, so if you’ve had pressure from the sales team or an executive, say so and explain what you did to pressure-test it and drive it forward. Honesty beats polish at startups.

5. Bring three real questions about the business. Ask about the moat, ICP, where the pain sits, how they think about defensibility. Every founder treats the quality of your questions as a proxy for how seriously you are engaging. Most candidates use that slot to just ask generic questions about the culture or team, so don’t be that candidate.

The Bottom Line

The role did not get harder, but the proof required to clear the bar did.

For a decade, a strong PM interview was a demonstration of process. Frameworks, structured thinking, a clean roadmap. AI now produces a competent version of all three in seconds, so none of them separate you from anyone else in the pipeline anymore.

What separates you now is specificity. Whether you have actually operated under real growth pressure instead of just wanting to. Whether you can name the exact place you chose not to let a model make the call. Whether you have owned a number beyond your own roadmap. Every founder conversation we sit in is testing for some combination of the three.

None of this is available on your resume. It only shows up when you tell the story of a real decision, with the tradeoff and the miss embedded in it. That is the entire shift and the bar is now higher.

Good luck out there. And always remember — keep grinding, but make it count.

If that is you, you are not behind and you are not missing something obvious. GTM used to describe a strategy, not a person. Somewhere in the last few years it became a job title, and it became one quickly, without anyone agreeing on what it should actually mean.

This article closes the gap in the confusion we’re hearing on the ground: where the term came from, why it splintered into multiple jobs wearing one label, what each of those jobs requires, and how to position yourself for the right one, whether you have spent years in tech or you are finding your way in from somewhere else entirely. Let’s dive in.

How GTM Became A Job Title

GTM has meant three different things across the last 15 years, and each shift explains a piece of the confusion you are feeling today.

2010 to 2020: The Decade That Built The Ladder

For most of the last tech cycle, GTM described a strategy rather than a person. Founders and investors used it to describe motion: sales-led or product-led, bottoms-up or top-down, and the term typically lived in board decks.

What actually got built during those years was specialization. In 2011, Aaron Ross published a book that earned its title as “The Sales Bible of Silicon Valley,” replacing chaotic founder-led selling with systematic processes that made revenue repeatable. GTM stopped asking one person to do everything and split the work across roles for prospecting, closing, and retention, each with its own metric and comp plan.

That created the ladder most of you know. An SDR or BDR generates pipeline, an AE runs the cycle and closes, and a CSM keeps the customer and grows the account. Marketing feeds the top while Ops keeps the machine honest underneath. It worked because it was measurable, teachable, and easy to scale by adding bodies.

2020 to 2022: Hypergrowth Made GTM A Noun

Cheap capital changed the incentive. Companies hired ahead of demand because growth was the only number anyone graded. SDR teams ballooned, marketing and customer success expanded alongside them, and companies needed a single word for the sprawl.

GTM became that word. It stopped meaning a plan and started meaning an org, and you began seeing “the GTM org” on charts that had held multiple separate functions a year earlier. Then 2022 arrived, capital tightened, and every company that had scaled by adding bodies discovered a cost structure it could no longer justify.

2023 to Now: AI Compressed It Back Down

Software replaced many of those bodies, and the efficiency gap opened. ICONIQ surveyed more than 150 B2B and AI GTM executives for its January 2026 State of GTM report and found that companies adopting AI aggressively generate roughly twice the net-new ARR per GTM employee.

They also run far leaner. At $10M to $25M in ARR, AI-forward companies field around 20 GTM employees against 35 for low adopters. Leaner has not meant weaker: quota attainment among ramped AEs sits at 67% in that group and 59% everywhere else.

So the ladder built in 2011 and overstaffed in 2021 is compressing. The work did not vanish. The number of seats holding it did, and the seats that remain are broader. That is the entire reason the title feels vague to you.

GTM is now a container for jobs that used to be separated.

What Actually Lives Under The GTM Label

Once you know it is a container, the useful question stops being “what is a GTM role” and becomes “which one is this.”

SDR and BDR

You generate pipeline through outbound prospecting and inbound qualification, which makes this the traditional entry point into GTM. It rewards people who treat rejection as information rather than judgment and who run high volume without losing care on the hundredth touch. It also sits under more pressure than any other seat, and Emergence Capital found 36% of companies cut SDR headcount in a single year, the highest of any function. But autonomous AI SDRs have not replaced human teams at scale, and roughly 125,000 people still work the role. It is splitting rather than dying.

Account Executive

You own the cycle from qualified opportunity to signature: discovery, demos, multi-threading through a buying committee, and negotiating when a deal goes sideways in week six. The people who do well here stay curious about how a buyer’s business makes money, tolerate long timelines, and build their own pipeline when marketing comes up short. This role holds up better than the roles beneath it, partly because humans still buy from humans, and partly because AI has made good sellers faster rather than replaceable. Founding AE roles keep trending, since startups increasingly want closers rather than junior prospectors.

Customer Success Manager

You retain and expand existing accounts, which is less about selling and more about noticing dissatisfaction before the customer names it. It suits relationship-driven people with the instinct to raise a problem early, which is why service and hospitality backgrounds translate cleanly here. AI pressure hits hardest at the low-complexity end, and AI-native companies can run a single AI CSM covering roughly the workload of a dozen human ones. At the strategic end, the opposite happens, and companies increasingly tie compensation to net revenue retention.

Product Marketing

You own positioning, pricing narrative, launches, and the enablement material sales actually uses. It fits writers and synthesizers who hold opinions about language and sit between product and sales without fully belonging to either. This was the original home of GTM inside most companies, which is why PMMs sometimes bristle at watching a term they defined get applied to everyone else. At early stage, the role absorbs competitive intel and content too, so expect breadth over depth.

Demand Generation and Growth Marketing

You build the top of the funnel through paid, content, lifecycle, and events. The role rewards people who think analytically and creatively in equal measure, and who can be publicly wrong about an experiment without flinching. Marketing shows the highest AI adoption of any GTM function, and there tends to be a higher output per person, given there are fewer and more senior seats.

RevOps and GTM Ops

You own the systems, data, and forecasting underneath everything above. It fits systems thinkers who like clean data and accept work that only becomes visible when it breaks. The most common GTM engineer responsibilities (see below) also show up in RevOps postings, which is why this function quietly became the place where technical GTM careers begin, ultimately leading to the growth of the GTM engineer.

GTM Engineer

You build the pipeline machine rather than working it, designing automated outbound systems, routing enriched data, and managing AI agents that do what a team of SDRs once did by hand. It attracts builders and tinkerers with commercial instincts, a different profile from either a pure engineer or a pure seller. Clay coined the term in 2023, and fewer than 100 people globally listed it as their title in July 2025. By January 2026 more than 3,000 postings were open, up 205% year over year. The only caveat is that the role skews more senior, with postings asking for 4+ years of experience on average.

How To Actually Break In

People who thrive in GTM handle rejection without absorbing it, stay organized without being told, and get genuinely curious about how a business makes money. They tolerate ambiguity, which matters enormously at early stage where the playbook does not exist yet and you write it yourself. At these companies, founders hiring their first commercial person weigh hunger, coachability, and whether someone can hold a credible conversation with a technical buyer.

If you’re looking to break in, here are some tips for how to stand out:

1. Pick your seat first. Applying to GTM broadly signals you have not thought about it, and founders read that instantly. Choose your lane before you write a single application, and understand where you can leverage your strengths best.

2. If you are targeting sales, prospect your way in rather than applying your way in.

   Build a 48-hour prospecting portfolio first: a target account list, a written outreach sequence, or a mock cold call. Bring it to the interview unprompted, because that artifact beats any certificate. It is the actual job rather than proof you studied it.

3. If you are targeting GTM engineering, build one working system and document it. 53% of people in the role today taught themselves, and it rewards demonstrable output over credentials. Pick a real problem, even something as simple as automating your own job search outreach, and build the full loop: enrichment, scoring logic, a CRM sync, an automated sequence. Write down what it does and what it produced, then add SQL and basic Python once it runs.

4. Treat the search itself as the work sample. Find the actual hiring manager and send something specific. If you cannot build a target list and earn a reply on your own behalf, you are demonstrating the exact deficiency the job is about.

5. Ask what you will be measured on before you accept. A vague answer means the company has not scoped the role, and you will end up holding four jobs while getting reviewed on none of them.

The Bottom Line

GTM is a container, and the container got smaller. The industry spent a decade splitting commercial work into specialized seats, spent two years overstaffing all of them, and now compressed those roles back down with AI handling the repetitive middle.

For candidates, that cuts both ways. The entry role shrank, but the people who build the system and sell the outcome earn more than they ever have, and the skills that get you there still transfer in from outside tech better than almost anywhere else.

So ask which seat you are actually interviewing for. If the person hiring cannot answer, you have learned something more useful than the answer itself.

Good luck out there — and always remember, keep grinding, but make it count.

Someone with 4-8 years of experience sitting between strategy and operations, sharp and specific about what they are good at, and likely graduated from a top business school, tells me they think product is where they should land next. They get there because it is the most popular title they can name, not necessarily because it is the best fit for what they have actually done.

The logic makes sense. PM is legible, the ladder is clear, and it looks like the natural home for a business-minded generalist. It is also one of the most competitive titles in tech, and the shape of the role is changing a lot. It is exceptionally hard to break into product right now, so I wanted to explore a few other paths for the traditional strategy and ops role. Let’s dive in.

Where The Role Came From And What AI Changed

Strategy and ops has been around longer than most people assume, and it started with one executive who needed leverage.

In the early 2000s at Yahoo, Jeff Weiner moved from corporate development into an operating role and built a team to give him access to the levers he needed to move the company. When Weiner became CEO of LinkedIn in 2009, he brought the concept with him and hired Dan Yoo to run it. Yoo took LinkedIn’s business operations team from 0 to more than 120 people in about 4 years, and framed the function as a decision-support mechanism that connected departments and absorbed the problems nobody owned.

From there it spread fast. Emilie Choi carried the model to Coinbase. Google built an internal group that operates like a consulting firm embedded inside the company. Stripe, Uber, Slack, and Dropbox all built versions of it. By 2015, investors were publishing posts telling founders that growth-stage startups needed one, with many describing BizOps as product management for the business model.

Between 2020 and 2022 it became the cleanest path from consulting or banking into tech. Nearly every posting listed a consulting background as the preferred profile, and business schools built recruiting motions around it.

Over time, however, that window eventually closed. In 2025, technology accounted for 1,968 MBA hires across the 95 business schools tracked by Bloomberg Businessweek, down from a peak of 2,929 in 2022.

What closed it was the collapse of the core for what the function was originally built to do. A company needed this team in 2010 because information was expensive to assemble. Pulling numbers across silos and turning them into a defensible answer took weeks, and that was slow enough to justify a headcount. Now a competent operator with a good model produces the market sizing, the teardown, and the first version of the financial model in an afternoon.

The demand did not disappear, but rather relocated into 4 other titles that all ask for different versions of the original strategy and ops title.

The New Paths That Opened

Chief of Staff

This role is the closest living relative of the original function. Weiner’s Yahoo team existed to give one operating executive leverage, and chief of staff is that same mandate with the team stripped out. Where traditional strategy and ops served many leaders through reporting and cadence, this serves one leader (usually the CEO) with the standing to act on their behalf.

The practical difference is where the work ends. In a biz ops seat, you assemble the analysis and hand the decision up. As chief of staff, you are handed the decision and expected to carry it through the organization, which includes the operating cadence, the driving of initiatives, and the sharing of context across functions. Similar work, but different directions in the org.

The AI Operators newsletter has been publishing open business operations and chief of staff roles every two weeks across 2026 at companies like OpenAI, Anthropic, Perplexity, Harvey, Decagon, and EliseAI. A large share sit at seed and Series A, which is earlier than this role historically appeared, and this has happened because AI companies are scaling revenue faster than headcount.

Founder’s Associate And Founding Operations Lead

This role is strategy and ops before there is anything to operate. The traditional version assumed a machine already existed that needed measuring and tuning, while this version builds the first one.

You are frequently the first non-technical hire, which means you are essentially creating the forecast, creating the hiring process, or managing key processes across the company. The work rotates weekly across pipeline, recruiting, vendors, onboarding, and whatever partnership conversation the founder cannot get to. Postings are vague because nobody knows yet what the company needs, and that ambiguity is the job itself.

This is the highest-variance door on the list. Founding operations people often end up running a function two years later, because they were the only one who understood how it worked.

Deployment Strategist

Take everything traditional strategy and ops does inside your own company and point it at somebody else’s.

The core skills transfer almost completely. Mapping a messy organization, finding where a process actually breaks, and getting people to adopt something they did not ask for. The difference is that you are doing it inside a customer’s environment, learning their data and approval chains and compliance constraints well enough to encode them, and driving the implementation until it produces a result they can point to. An internal recommendation can quietly die in a quarter, while ones in this role have a contract attached to it.

Palantir has run this as a distinct track for over a decade, as the business-leaning sibling of the forward deployed engineer in the same customer-embedded model. Demand has gone crazy. Indeed data showed forward deployed postings up roughly 729% year over year by April 2026, and a study covered by TechCrunch found the share of companies planning to hire for these roles jumped from under 10% at the start of 2026 to 70% by the end of Q2, against an estimated US pool of only 17,000 people.

For those in New York, these postings account for roughly 35% of all postings against San Francisco’s 11%, mainly because demand concentrates in regulated industries.

AI Operations Lead

This is perhaps an internal cousin of the deployment strategist, and the most direct evolution of the old job.

Traditional biz ops found the bottleneck, quantified the cost of it, and handed the fix to engineering or a functional team. This role, on the other hand, closes it. The process mapping across sales, support, and marketing looks identical to what a business operations analyst has always done, but the deliverable changed. Instead of a recommendation deck, you build the workflow in tools like Claude, wire it into the CRM and reporting stack, and then own the adoption and accuracy numbers afterward.

This is the most accessible door for anyone currently sitting in a strategy or ops seat because you can start doing the work at your existing company without an official title change.

How To Position Yourself

While the traditional GTM strategy and operations role lives on in smaller capacity at Series B and beyond, the role’s popularity makes it also one of the most crowded ones.

Here are some ways to stand out for these newer paths:

1. Rewrite every experience line to highlight ownership. This matters more than ever to make the transition. Highlight every bullet describing influence, partnership, or support. “Partnered with leadership on the international expansion strategy” tells a hiring manager you were in the room. The version that works names the market you picked, the number you carried, and what happened. If a bullet cannot end in an outcome, rewrite it or cut it.

2. Build one thing and be able to walk through it. Technical fluency is now a screening criterion in many of these paths, and a certificate proves nothing. Pick a process at your current job that annoys everyone, automate it end to end, put it in front of real users, and track what it saved. That artifact demonstrates the exact sequence these roles hire for, so it becomes a great talking point in your interviews.

3. Pick a vertical and get specific. These companies sell into healthcare, legal, insurance, logistics, and defense. Someone who understands how a claims workflow actually functions beats someone who understands strategy in general. If industry exposure is buried in your background, pull it forward.

4. Stop searching by title. The same job posts as Chief of Staff at one company, Founding Ops at another, and Deployment Strategist at a third. Keyword search misses most of the market. Build your list by stage and by problem instead, finding companies growing revenue faster than headcount, then identifying which function is breaking. Pick a few of these doors and go deep rather than running a thin search across all options.

5. Go where these roles circulate before they get posted. Operator newsletters, investor talent teams, and founder networks surface these openings ahead of job boards, and a meaningful share never reach a board at all. Build real relationships with people who see this deal flow and will have insight into which of the hottest startups are hiring.

The Bottom Line

This function has been reinventing itself since Weiner needed operating leverage at Yahoo 20 years ago, and it is doing it again. The people who win the next few years are the ones who stop describing what should happen and start owning whether it does.

If you are sitting between strategy and operations and feeling like the market has no room for you, look again. The market moved, titles changed, and companies are asking for something different than they asked for in 2021. Perhaps a harder bar, but hopefully a better job on the other side of it.

You have more of the raw material than you think. Go build the thing, tell the story straight, and take the shot.

Good luck out there. And always remember — keep grinding, but make it count.

Companies genuinely do buy senior fractional expertise, but the model only works when the conditions are right. The work has also drifted a long way from what it originally was meant to be, and a lot of talented people are making career decisions based on the drifted version. Let’s explore the history and how it’s viewed today.

Where Fractional Work Started

The model is much older than the trend. Interim management started in the Netherlands in the mid to late 1970s for an unromantic reason. Dutch labor law made permanent managers expensive to dismiss, so companies began renting senior leadership on defined terms instead of hiring it outright. A company with a specific problem bought leadership in a smaller unit than a full-time hire, and every version since has inherited that logic.

The American version arrived through finance. Across the 2010s, companies under roughly $10 million in revenue needed a CFO’s judgment and could not justify a CFO’s salary, so a market formed around part-time finance leadership. Marketing followed shortly after, and the definition stayed tight the whole way. A fractional executive held real decision authority, worked 10-30 hours a week on retainer, and owned outcomes the way a permanent hire would. Consultants advised from outside the org chart, and interim executives filled an empty seat full-time during a crisis. Fractional meant an ongoing part-time seat that a company had deliberately created.

Then 2021 arrived. Cheap capital, remote teams, and the Great Resignation turned the model into a category with marketplaces and communities built around it. The supply shock came right behind. Tech layoffs pushed an enormous number of experienced operators into the market across 2023 and 2024, and the word quietly changed jobs. It had always described something a company bought, but it started describing something a person is. In 2022, roughly 2,000 people on LinkedIn used fractional in their title. By early 2024, according to Harvard Business Review, that number had passed 110,000. Two years, 55 times the supply. And in 2026, that trend has continued.

What It Looks Like Today

Go Fractional, one of the larger marketplaces for this work, publishes live posting volume by role. Over the most recent 90 days, it reported 59 fractional CFO postings, 48 CMO, 19 CTO, and less than 10 each for COO and CPO. That is a couple hundred C-Suite fractional openings across an entire marketplace in a quarter, set against 110,000 people carrying the title.

The practitioner data agrees. The FRAK survey of more than 500 fractional executives found 30% earning under $50,000 a year, with 89% supplementing through consulting or advisory work to keep income stable. Go Fractional’s 2026 survey found 90% naming client acquisition as their single biggest challenge, and that figure barely moves regardless of how long someone has been at it.

The time math surprises people too. Half of fractional operators run 2-3 clients at once, and nearly 1 in 5 spends more than 20 hours a month purely on finding the next engagement. Two clients at 15 hours each, plus the business development required to replace them when they wrap, is not a part-time commitment. A real practice is a full-time job in which a serious portion of the week goes to selling rather than doing.

None of this makes the label dishonest. The trouble starts when the word gets treated as a plan, because on its own it has never been one.

How Startup Founders View The Need

We sit in intake conversations with founders every week, and fractional comes up in a narrow set of situations. Usually the company has a bounded problem with an external standard attached, like closing the books or clearing a security review. Sometimes it wants a competent adult holding a function until the next raise.

What we almost never hear is a founder with real momentum asking for a fraction of a person. The reason is context. At the early stage, the value of a senior hire comes from being present for the 20 small decisions a week that never make it onto an agenda. A fractional operator gets the 4 that did. That trade works fine for finance, where the questions arrive on a calendar. It works badly for product, sales leadership, or engineering leadership during a build, where the answers depend on things you only learn by being in the room every day.

The pattern is consistent. Companies with money and momentum hire. Companies short on one or both go fractional. Just be clear-eyed about who your buyer usually is.

How To Pick The Right Fractional Work

Fractional work is genuinely good input. Founders treat it as a way to buy proximity to how modern companies actually operate. The teams doing interesting work right now are small and leaning hard on AI tooling, which means they run loops faster than anything inside a larger organization. Three months next to that keeps your judgment current in a market where currency is exactly what’s being screened for.

That said, the fractional payoff only shows up if you’re deliberate:

1. Pick clients on domain strength. Take engagements where you already have depth and the company gets your best work. Ranging in the wrong direction produces the scattered profile that gets passed over later. Lean into your strengths from the full-time experience you’ve worked so hard to build over time.

2. Optimize for the experience over the rate. The puck is obviously moving towards AI so find those engagement that teaches you how an AI-native team ships, how GTM strategy is changing with AI, how engineering teams are using agents, or how a customer success team is using better AI tools. Experience beats making slightly more per hour in your rate.

3. Cap your clients. Two serious clients will teach you more than five shallow ones. Go deep where you can and build real expertise in a space. Imagine what accomplishments you would want to put on your resume, not just the brand names or scope size.

4. Keep a public record where you can. Write about the patterns you’re seeing across engagements. It’s the cheapest evidence of judgment available to you, and a resume structurally cannot hold it. The more context you can put out in the wild, the better you can back up your accomplishments.

5. Know which game you’re playing. Decide whether you are going full-time on fractional work or whether it’s a stepping stone towards your next full-time role. The nuance matters and hiring managers will notice.

Side note on positioning: If you’re doing fractional work as a side gig or part-time until your next full-time role, the biggest question you will get in full-time interviews is about commitment. Founders and hiring managers will wonder whether you want a job or a client. They will almost never ask you directly, so it’s better to address it proactively. Say plainly why you went independent, what you learned from it, and what you’re after now. Ambiguity on this single point costs strong people real offers, and most of them never find out that’s what happened.

The Bottom Line

Fractional went from a purchase decision to an identity in about two years, and the supply of people claiming it has badly outrun the demand. The work still has real value, and that value is in what it teaches you and who it puts you next to. You collect it by treating the period as a phase with a clear purpose behind it.

Choose your engagements the way you’d choose a job. Then be direct with everyone, including yourself, about what you’re actually after.

Good luck out there. And always remember — keep grinding, but make it count.

This example is the type of advice that founders are actively being given. Sierra Ventures published an interview recently with Adam Ward, who ran recruiting at Meta and Pinterest before Cursor acquired his boutique firm. Ward’s argument is that great teams get built by founders who treat recruiting as a primary job rather than a moment in time, which means more upfront work scoping roles, holding the bar high, and building a warm bench months before there is an urgent need.

So by the time you see a job posting, the search has quietly been running for months and a few names are already sitting in the founder’s head. If you have spent the last several months applying and hearing nothing back, that probably lands somewhere between validating and infuriating.

The data underneath it points to a problem and an opportunity. Let’s dive in.

The Math Behind the Job Applications

CareerPlug studied more than 10M applications and found that roughly 3% of applicants reach an interview. In tech, the ratio runs even worse. So when you fire off 50 applications and hear back from 2, you are performing to the market average.

The instinct is to read that as a quality filter, as though 97% of people were weighed and left in the dust. That is not what is happening. Recruiting teams got smaller while application volume exploded, and no human can read 300 applications with care. What that 3% measures is capacity. The queue rations attention long before anyone evaluates you, and a rationing system will always favor whatever sorts fastest, whether that is keyword matches, recognizable logos, or school names. Your resume is competing against time and headcount, not against the other candidates.

Before you write off the whole channel, hold that next to Ashby's data on tens of millions of applications. Inbound applicants are still the single largest source of hires, and their share has grown over the past 5 years. People do get jobs by applying, every week, and that door is still open to everyone reading this.

The tension actually resolves once you separate volume from odds. Applications produce the most hires because applications are where nearly all the volume sits. Gem’s 2026 Recruiting Benchmarks Report, built on 165 million applications and 1.2 million hires, found that a sourced candidate is close to 8 times more likely to get hired than someone who applied. That gap has nothing to do with talent. Somebody already decided they were worth pursuing, so they walk in with an internal advocate, a reason for existing in the pipeline, and a hiring manager already looking for reasons to say yes. The applicant has to manufacture all of that inside a 30-minute screen.

Then there is the finding that should change your perspective. Of every hire made through sourcing, 46% came from candidates already sitting in that company’s own database, up from 26% in 2021. That figure nearly doubled in 5 years, and it is the fastest-moving line in the report.

Read it as a signal about where the industry is heading. Companies drowning in applications stopped trusting the pile and started trusting their own history. The most reliable place to find a good hire turned out to be the record of everyone they had already met. Half the time a recruiter goes searching now, the person they surface is someone the company already knows.

What Candidates Get Wrong About Rejection

At Stride we run embedded searches for early-stage startups, which puts us on both sides of this problem. We sit in a room with a founder working out what the role actually is, and we are on the phone afterward when they explain why a candidate did not make it through. That vantage makes a few things obvious that are close to invisible from the candidate seat.

• Myth: A recruiter read my application and said no.

  Most of the time nobody read it. Your application was sorted by a filter or skimmed in 10 seconds by someone carrying more open roles than any person should hold. There was no considered assessment of whether you could do the work, and no mechanism anywhere in the process designed to tell you so. Read the silence as information about the channel rather than information about you. Cold applications are the least effective route into a company, and they behave that way no matter how strong you are.

• Myth: A rejection after an interview closes the door.
  Instead, it creates a future opportunity. The company now holds a scored, tagged, timestamped record of someone who cleared a screen, impressed at least one interviewer, and lost for reasons that often had nothing to do with your ability. Maybe the other finalist had done the exact thing before. Maybe the role changed shape mid-search. That record costs them nothing to keep and outranks many cold resumes arriving down the line because somebody already did the expensive work of vetting you. The follow-up you send 6 months from now has history.

• Myth: The way to beat bad odds is more volume.
  This is the trap, and it is the most expensive mistake we see. Every cold application you send reproduces the same 3%, so doubling your output doubles your rejections and changes nothing structural. It has never been easier to apply, which is exactly why applying has never been worth less. Thirty minutes spent on one real conversation moves you into a different pile. Thirty more applications keep you in the same one. That trade pays off many months from now rather than this week, which is why almost nobody makes it.

• Myth: My record speaks for itself.
  Your record is a snapshot of whoever you were the week you applied. If you have since changed jobs, shipped something significant, or moved into a new function, none of it lives in that application. Take an active role to take charge of your own narrative. Go to networking events even when you’re happy in your job, talk about your learnings publicly, and keep your network warm as much as you can. The upfront work you do now will pay off in the long-run, many times over.

How To Get On The Bench For Your Next Role

Both job seeking and recruiting are a long game, and there’s a lot you can do upfront to set you up for success when your time comes:

1. Build your warm list before you build your target list. Find every company where you got past the first screen in the last two years. That list is short and specific, and it is the highest-yield asset you own right now. Everybody keeps a list of dream companies, and almost nobody keeps a list of companies that already came close to yes. Go back to the recruiters, hiring managers, and interviewers on that list and give them something to remember you by. You will be surprised what comes back.

2. Reconnect on a trigger instead of a need. A funding round, a new executive you respect, a competitor's launch, or a real piece of work you shipped all give you a reason to write that has nothing to do with wanting something. Two or three sentences will do it. Name the specific thing, say what it made you think, and stop. "Just checking in" gives a recruiter nothing to react to, and they can spot it from the subject line.

3. Answer recruiter emails even when you’re happy where you are. This is the controversial one, and it’s still right. A short honest reply saying you are not looking, here is what would make you look, and here is what you have been building costs you a few minutes and puts you on exactly the bench that Adam Ward is telling founders to build. Six months later, when that role gets scoped or your own situation changes, you are already a warm name in the room.

4. Refresh the record on purpose. When something meaningful changes, tell the people who already hold a file on you. A one-line note to a recruiter from last year saying you moved into a bigger scope updates their picture of you at almost no cost. Update your public profile the week it happens rather than the quarter, because that is the index most rediscovery searches actually run against.

5. Write for the role you want next. Rediscovery is a keyword query before it is ever a conversation. If your title describes what you do now and your ambition describes something adjacent, the query will pass right over you. Make sure the language of the job you want appears somewhere in your public record, in your own words, attached to real work you did.

The Bottom Line

Founders are being coached to build a warm bench long before the need turns urgent because the alternative is starting from zero under pressure with a burning req and a board asking questions. That advice is correct and the mirror image is equally correct. The candidates who land the best roles are already on somebody’s bench when the posting goes live.

The posting sits closer to the middle of the process than the beginning. By the time it reaches you, a few seats have quietly been claimed. Grinding harder inside the application queue will not change that.

What you can change now is how many open files you have out there, and whether the version of you inside them still resembles who you are today. That work is unglamorous, it compounds on a timeline that feels useless when you need a job this month, but it is all the closest things to a real edge available to you.

Good luck out there. And always remember — keep grinding, but make it count.

The founder hadn’t done that carelessly. He genuinely wasn’t sure yet which of the two problems mattered more. Over time, his job posting hedged in one direction and every week he had cycled back and forth on which of the two problems to evaluate candidates against, leading to the belief that the “right” candidate wasn’t out there.

This isn’t uncommon, but rather the default. Uncertainty gets published as precision, and then it hardens. Recruiters screen against it, filters parse it, and candidates read it as a verdict on whether they belong in the room. And when a process gives candidates nothing real to aim at, they do the rational thing and apply to everything. Multiply that in both directions across every open role, and you get where we are now: a market drowning in volume, where hiring managers can’t find their people and strong candidates can’t get seen.

The JD Is Usually Unfinished Thinking

The truth behind the scenes is that most job descriptions are written before the thinking is done.

At an early-stage company, the JD is often drafted by a founder who has likely never hired for that function. They know something is broken. They have a rough sense of who might fix it. They write that down, borrow structure from 3 postings they found online (or Claude), and add a qualifications list describing a profile that doesn’t exist.

That document then hardens into a spec. Recruiters screen against it. Filters parse it. Candidates read it as a verdict on whether they’re allowed in the room. Meanwhile the thinking behind it keeps moving, and nobody goes back to update the posting.

While some data does show that senior searches now run 2-4 weeks longer than they did in the past, the diagnosis matters more than the duration. The biggest driver of a slow senior search is organizational readiness, not the talent pool. That means that most delays come from the process, not from an absence of qualified people.

So the document you’re treating as ground truth is often written by a non-expert, describing an unresolved problem, frozen at the moment of maximum uncertainty, and perhaps even sometimes not real.

Volume Feeds The Doom Loop

Given this opaque, low-information process, candidates do the rational thing: volume.

The average job opening now receives somewhere around 250+ applications. Five years ago it was closer to ~100. Greenhouse, with roughly 175,000 live jobs on its platform, reports applications per recruiter up 412%, driven by easier access to mass application tools, AI making it faster to hyper-tailor a resume, and a tech market that has a lot of candidates looking for their next role.

Greenhouse CEO Daniel Chait recently called this a “doom loop” and that’s exactly right. Candidates use AI to apply at scale. Recruiters are buried and use AI to filter harder. Rejected candidates automate more. Around 90% of HR managers say their workload has increased because of AI-generated applications. This is the first time both sides have been unhappy at once.

If you’re running a volume strategy, know that a candidate is roughly 3 times less likely to get hired for a given role than 3 years ago, with passthrough rates down at every single stage of the funnel, one that is now optimized to reject, not to discover.

As a recruiter processing 250 applications for one role with no extra headcount, your job stops being “find the best person” and becomes “get this pile down to single digits.” That rewards completely different things. Anything reading as median gets treated as median, resulting in everyone more or less looking the same on paper.

Understand The Evidence In The JD

Stop reading job descriptions as instructions and start reading them as evidence. These postings tend to leak enormous amounts of information about a company’s clarity, urgency, and flexibility, but almost nobody reads it that way.

Here’s how we’d recommend actually interpreting one:

• Prioritize the first few bullets, and discount the rest. Responsibilities get written in the order they occur to the drafter. The top is the real job while the bottom is padding. If what excites you is bullet nine, you’re applying to a different role than the one being filled.

• Count the number of jobs in a JD. Two or three genuinely distinct skill sets in one posting means the company hasn’t decided. That’s not a higher bar, but rather an unresolved internal debate, and it means the role is more malleable than it looks on the surface.

• Find what repeats. Whatever appears in the summary, again in responsibilities, and again in qualifications is the actual obsession. Things that are mentioned once tend to be noise. Build your entire pitch around the repeated things.

• Read the comp band range. A tight band means the level is settled. A wide spread means they haven’t decided what seniority they’re buying and will flex for the right person.

• Check how long it’s been posted. A role live for 4 months is one where the original hypothesis has probably already cracked internally. Watch out for that ambiguity.

• Notice what’s absent. No named manager, no team size, or no success metric means the role isn’t scoped. That’s real risk on the inside but also real opening for someone who shows up with a plan.

• Translate the euphemisms. “Wear many hats” means no process exists. “Comfortable with ambiguity” means leadership hasn’t aligned. Neither is disqualifying but both are load-bearing information about what you’d walk into.

Adjust Your Approach

In a channel flooded with polished, generic, high-volume applications, the only thing carrying signal is specificity. Here’s what you can do to optimize your time:

1. Cut volume, raise depth. Job seekers using tailored resumes hit roughly a double application-to-interview rate than those who use generic resumes. 20 deeply researched applications beat 200 sprayed ones and take less total time. Focus your energy and go deep rather than broad.

2. Target roles where your strength is the hardest thing on the list. This is the highest-leverage change most people can make. Don’t apply where you barely clear the bar and blend into the pile. Apply where the thing the company is most worried about is the thing you’re best at. Your differentiator should be their hard problem, not a bullet you happen to satisfy. That’s the difference between “qualified” and “obviously the answer,” especially in a 250-applicant pool.

3. Lead with their problem, in their language. Most outreach opens with interest: “I’m excited about this role and think I’d be a great fit.” That sentence is indistinguishable from everyone else. Open instead with the repeated theme you found in the JD, what you’d do about it in 90 days, and one piece of evidence showing you’ve done it before. Interest isn’t information but a plan is.

4. Stop using the front door. Every path where a human knows your name outperforms the cold application form by an order of magnitude. Message the hiring manager on LinkedIn. Message the founder. Message the recruiter who posted it. Find someone one level up from the role and ask what the team is actually struggling with. Most won’t respond, but the ones who do are worth more than a hundred submissions.

5. Build something. This applies to every function, not just engineering.

   You have the same tools flooding the funnel. Most people use them to send more applications. Use them to make artifacts instead. Vibe-code a working prototype of a feature they’ve publicly said they’re building. Write a two-page teardown of their onboarding with three specific fixes. Build the territory plan, the comp model, the competitive analysis. Record a five-minute Loom on what you’d do in month one. These signals mainly work because they can’t be faked at scale. An artifact is proof of judgment, not just proof of interest.

The Bottom Line

The dysfunction isn’t that companies are cruel or candidates are lazy. It’s that both sides are making decisions under uncertainty and hiding it from each other. Companies publish false precision about roles they haven’t scoped. Candidates publish false enthusiasm about companies they haven’t researched.

If you’re hiring: write the problem, not the profile. Name the 90-day outcome. List only what would actually rule someone out. If you don’t know what level you need, say so or take more time to define it - you’ll get better candidates as a result.

If you’re searching: read the JD as evidence, not a verdict. Find the repeated theme, count the jobs hiding inside it, notice what’s missing, check how long it’s been open. Then pick fewer targets, go around the form, aim where your strength is their hardest problem, and show up with something you made.

Everyone is drowning in volume from both directions, and the heroes in that environment are those who clearly do the work to understand the other side.

Keep grinding out there, but make it count.

No skills gap. No missing credential. Just a feeling, formed somewhere inside a thirty-minute intro meeting, that this person wouldn’t run through the wall on the day the wall showed up.

We see this rejection more than almost any other, and it’s the hardest one to do anything about. There’s no fact to correct and no resume line to rewrite. Someone looked at a strong candidate, decided the intangible wasn’t there, and couldn’t quite tell you what the intangible was.

The Word Founders Can’t Quite Say

When a founder says they want “hungry”, “driven”, or someone with “fire”, they are almost always reaching for one word they can’t quite land on: Ownership.

An owner spots a problem and moves before anyone assigns it. They treat the company’s goal like their own money is riding on it. They start building the plan in the exact moment most people sit and wait for one to arrive. Every serious study of early-stage hiring circles the same short list of agency, adaptability, and ownership, over and over. One venture firm put it this way: You can teach almost anyone a new skill, but you can’t teach someone to care.

That is what sits under the fuzzy word. And the trouble is that founders almost never say it that cleanly. The whole judgment then stays a vibe, and a vibe is a terrible thing to have your career decided by.

Why This Matters More Than It Used To

AI has flattened nearly everything a resume was ever good at measuring. Every application now arrives polished, every skill gets claimed, and competence reads as the baseline across the entire pile. When the measurable signal flattens like that, the decision leans harder on the things you can’t fake, and ownership sits right at the top of that list. The intangible became the whole game the moment the tangible stopped saying anything.

This is not some scrappy-startup quirk, either. Netflix’s product and technology chief, Elizabeth Stone, recently told that the most important skill she now hires for is systems thinking - the ability to see across a whole business and step back from your immediate task toward the larger problem it serves. She is describing the same instinct a seed founder is fumbling toward in a half-hour call. Top to bottom, the market is reorganizing around people who own the entire problem, the parts nobody handed them included.

The Interview Is A Constant Hunt

Because founders can’t define ownership, the interview quietly turns into a hunt for it in disguise, and most candidates never realize that’s the game being played. A good interviewer asks you to walk through one thing you owned end to end, and they’re listening for whether you scoped it yourself or got handed a spec, whether you decided what mattered or waited to be told, what you shipped, and what genuinely changed after you did. Then they throw something unstructured at you on purpose, some version of “you show up Monday to 10 problems and 3 loud people are all swearing their problem is the real fire: so what do you do first?”

There is no right answer. They only want to watch you think like the problem is already yours. And the entire time, they’re running a quiet checklist against you that cross-checks against certain yellow flags:

• Internal demos that never reached real users or shipped

• Impact described as “improved efficiency,” with no number behind it

• Over-indexing on internal stakeholder opinions versus customer feedback

• Not one real tradeoff, not one thing you consciously chose to kill

• Any hint that you need a playbook before you can move

Every one of those lands as the same silent verdict: Capable but still not someone who will own the work when it arrives undefined and nobody is watching. Of course this is inherently a “vibe check” and can be quite subjective. Humans are genuinely awful at separating someone who shares our drive from someone who simply feels familiar, because from the inside, those two sensations are identical. That is the real pain of this market. You can do everything right and still lose to a feeling that was never about you.

How You Can Actually Stand Out

The most important thing you can do is take the founder’s gut dependency completely out of the equation. That is your opportunity. You can’t win a vibe check, but you can make one unnecessary, by stacking so much hard evidence of ownership in front of them that nobody in the room ever has to guess.

1. Bring one story you owned start to finish. Tell a single story along its full arc, where it began, what was broken or undefined, what you decided, what you shipped, and the specific before and after. An engineer names the system they built and the hours it erased, a salesperson names the pipeline they built from nothing and the number it closed, a product hire names the feature they shipped from customer feedback to PRD to launch, all with a high degree of ownership.

2. Kill every vague number. “Improved efficiency” is the most forgettable phrase in interviewing, and it quietly signals you stood too far from the work to know the real figure. Move away from adjectives and focus on the hard numbers. Only the person who actually did the thing carries its numbers, so put a figure on everything that can hold one.

3. Say what you chose not to do. Owners live inside tradeoffs, so name one explicitly, whether it’s what you deprioritized, what you decided against building, or the good idea you killed because the leverage clearly sat elsewhere. Only the person holding the wheel ever has to decide what gets left behind.

4. Walk in already working on their problem. Arrive with a genuine point of view on their business, where you’d guess their biggest bottleneck sits, and the risk you’d watch most closely. You don’t have to be right. You have to show you already treat their problem as worth a real thought before anyone has paid you a dollar for it.

5. Be all in on the company, out loud. When they ask why them and why now, skip the warm enthusiasm everyone else leads with and give them a clear-eyed answer, then ask the pointed questions about runway, churn, and the thing that keeps the founder up at night. See the risk clearly, and then tell them plainly why you want in anyway. A candidate who understands and chooses the danger is likely far more serious than one who seems grateful for any job that will have them - this conviction is ultimately a signal you can control completely.

None of these actions ask you to perform intensity theater, borrow a personality, or hand over your weekends to prove a point. You are simply making the ownership visible in specifics, so nobody has to squint and guess. And if you feel like you’re still building the muscle rather than showing it off, run the daily version, stepping back one click on your current work and doing your own job in the way that most helps your manager do theirs.

The Takeaway

Go back to the candidate from the top, the one who did everything right and still heard they weren’t hungry enough. What separated them from the person who walked out with the offer almost never came down to drive. It came down to evidence. One of them left the founder guessing, and the other made guessing impossible, by proving ownership in specifics long before anyone had to reach for a feeling. That is the whole game this early. Act like the company is already yours, show the receipts, and the fuzzy word falls away on its own.

Good luck out there 🙏

P.S. If this was useful, forward it to someone who’s interviewing at early-stage startups and could use an insider’s perspective. Every week, we turn our real stories from our recruiting firm Stride into tangible insights and actions for candidates to navigate this crazy market.

If you've looked for a job in tech over the last year, you already know something is off. You tailor the resume, you write the note, you hit apply, and it vanishes into a void that never writes back. You're more qualified than you've ever been, and somehow it's never been harder to get a single human to notice.

The worst part is that on the other side of that void, the founders doing the hiring feel exactly the same way. They're posting roles and getting buried with hundreds, sometimes thousands of applications per opening. Yet they’re still convinced the person they actually need is out there somewhere else, unreachable.

Two groups, staring at the same broken market from opposite sides, both drowning, both certain the problem is everyone else. The market didn't get harder in the way everyone thinks it did. It got broken in a specific, fixable way, and once you see it, you can't unsee it. Let’s break it down.

The Market Is Not What The Headlines Say

The narrative you’ve absorbed is “layoffs everywhere, AI taking jobs, brutal market.” Some of that is real. Tech employers announced roughly 52,000 job cuts in the first quarter of 2026 alone (the highest first quarter since 2023). A lot of very good, very senior people are looking right now.

But at the same time, what isn’t broadly being talked about is that there are is also lots of hiring happening. Lenny Rachitsky’s most recent read on the product job market found PM openings at their highest level in over three years, software-engineering demand holding steady, AI roles exploding, and the total number of tech jobs still growing. His word for the situation was “optimistic.”

So which is it - brutal or booming?

It’s both. And the fact that it’s both is the entire point. There is more talent in the market and more open roles and it somehow feels impossible on both sides of the table. Founders can’t find people. People can’t get found. When supply and demand are both high and everyone’s still miserable, you’re not looking at a shortage. You’re looking at a matching failure.

AI Broke The One Signal We All Relied On

The resume used to carry signal, not because it listed your jobs, but because a tailored resume meant something. If a candidate had clearly read the job description, mirrored its language, reworked their bullets for that specific role, the effort itself was evidence. It told a hiring manager that this person is serious, this person cares, and this person did the work.

AI vaporized that overnight. Now every resume is hyper-tailored to a job description. Every cover letter is crisply written. Every application is optimized perfectly. The polish that used to separate the serious few from the spray-and-pray many is gone because the spray-and-pray many now have the same polish. A founder opening 1,700 applications isn’t looking at 1,700 signals, but rather 1,700 near-identical, competently written, impossible-to-differentiate documents.

This is the idea we built Stride around, and it’s the most important through line:

Hiring was never a sourcing problem. It’s a signal problem.

Finding people has never been easier - post a role and get hundreds of resumes in the first few days. But, understanding which of them can actually do the job has never been harder. The information that predicts success like how someone thinks, how they operate under ambiguity, or whether their experience holds up to the real experience of the job was never on the resume in the first place. And now the resume is a layer of pure noise sitting on top of it.

The tools don’t fix this. Applicant tracking systems track candidates. Sourcing platforms find them. None of them tell you who’s actually good. The only reliable signal left lives in a real conversation, and real conversations don’t scale to 1,700 applications.

What This Means For Candidates

If the resume is dead as a differentiator, what do you do? Here are some ways to differentiate yourself in this crazy market:

• Show how you think, before round one. The highest-leverage thing you can do in this market is hand a hiring manager something to react to before they ever screen you. This could be a short public teardown of a product you admire, a written breakdown of a hard problem you solved and how, or a post about something you learned the painful way. You’re not building an audience, but rather handing someone evidence of your judgment that a resume structurally cannot hold. In a world where every document looks the same, being the candidate with a visible mind is a cheat code to your foot in the door.

• Lead with outcomes, not responsibilities. The most common reason a strong-looking candidate gets passed over is that they describe what they were responsible for instead of what changed because of them. Founders don’t care about your scope or title. They care about the delta - what was true before you, what was true after, and the specific thing you did in between. “Owned onboarding” is noise. “Cut activation time 40% by killing three steps” is signal. Say the second thing, in numbers, up front.

• Make your experience survive a real question. AI can polish how you describe your experience. It cannot manufacture the experience itself. When someone who has actually done the job asks the second and third follow-up (i.e. why did you do it that way, and what broke when you did), polish falls apart and substance holds. Be ready to go three layers deep on anything you claim. Depth is the one thing that can’t be faked, which is exactly what makes it the most valuable thing you own right now.

• Get into context-rich channels. Being one of hundreds is the failure state. The way out is any path where you arrive with context already attached like a warm introduction, a referral, or a recruiter who actually knows your story and can vouch for how you operate. This isn’t about who you know. It’s about refusing to enter as an anonymous resume when you could enter as a known quantity. Context-rich channels are placing senior people in a couple of weeks while the application pile runs 45 to 90 days.

Notice the thread running through all four: you win now by carrying your own signal, not by having a cleaner resume. The people getting pulled out of the pile are the ones who understand the resume is now just table stakes and it’s important to make their thinking, their outcomes, and their depth impossible to miss.

The Takeaway

The market isn’t brutal or booming. It’s flooded with talent, with openings, and with AI-generated sameness that has buried the signal both sides are desperate for. Founders are drowning in applications and still can’t find people. Candidates are more qualified than ever and still can’t get seen. These are two sides of the same problem.

If you take one thing from this article, it’s that the resume is no longer how you stand out because it’s no longer how anyone stands out. The winners in this market supply what the resume never could: visible judgment, concrete outcomes, real depth, and a way in that carries context. Get out there and conquer 💪

A note on the new name and direction, for those of you who’ve been here a while:

The thesis of our recruiting business revolves around spending every single day inside the exact question this newsletter has always circled: how hiring really works, and who actually gets picked. So I’m bringing it all under one roof. Same voice you subscribed for, same candidate-first perspective, just now written from inside the market instead of alongside it.

If this new direction isn’t what you signed up for, feel free to unsubscribe and I won’t take it personally. But if you know someone getting buried in the application pile or starting to poke their head out in the market, forward this to them.

P.S. If you’re in the market yourself, you can join the Stride talent network on our website. We’ll reach out if there’s a fit for our open roles, and we’ll learn about you beyond your resume.

“Thank you for your interest. After careful consideration, we’ve decided to move forward with other candidates…”

You stop reading, put your phone away, and don’t say much about it. When someone asks how the search is going, you say “fine.” It isn’t, really. You just went through hours of interviews and preparation, only to receive a generic rejection email with no explanation whatsoever.

If you’re navigating this job market, you’ve probably now stopped counting the rejections. Whether that’s the automated one that arrives the same day you submit an application, the recruiter who was warm on the call and then went quiet afterwards, or the classic “you were great, but we went with someone else” feedback after spending hours in final round interviews.

Underneath all of these rejections sits the same quiet thought: maybe the problem is me.

I want to take that thought seriously, because it’s costing you more than you realize, and then I want to show you why it’s mostly wrong. Most of those no’s say very little about your worth. They’re math, policy, and timing that look like a personal verdict, but the market has handed companies most of the leverage - the system is built to reject by default and explain almost nothing.

Let me break down what these rejections actually mean, and then explain where your leverage actually lives.

The Common Types of Rejection

Not all no’s are the same. The mistake candidates make is treating every rejection as one undifferentiated verdict on their worth. They’re not. They come from different places in the system, and each one means something different.

• The instant auto-reject. You applied, and the rejection came before any human could have possibly read your resume. This one is pure math, and the math is brutal. The average corporate posting in 2026 pulls around 250 applications, with entry-level roles often seeing 400 or more. Only 2 to 3 percent of applicants get an interview, and a large share of resumes are filtered by automated screening before a person ever looks. This rejection is not a judgment of your experience. It’s a filter that never read it. Treating it as personal feedback is like reading tea leaves in a coin flip.

• The post-screen ghost. You had the recruiter call. It felt fine. Then silence, or a generic rejection email days later. Remember what that recruiter was actually doing: they had a stack of other candidates that week and a thirty-minute brief on the role. You weren’t evaluated against your potential., but rather against a checklist and a pile. Roughly 70 percent of candidates get no feedback at all after a phone screen. The absence of feedback is unfortunately the default setting.

• The final-round “it was close.” This is the one that hurts most, because you invested the most and the rejection sounds the most personal. It usually isn’t. “We found someone who fit exactly what we were looking for” is, more often than not, literally true and has nothing to do with your quality. The req shifted, the budget moved, an internal referral surfaced late, or they wanted someone 10 percent more senior or who’d done this exact thing at this exact stage before. The selected candidate is a subjective call based on what the employer needs at that moment and how someone happens to mesh with the team. You can be excellent and still not be the specific shape they were measuring against.

The throughline through all of this is that most rejections are about fit against a narrow, often arbitrary set of criteria, decided by people with partial information under time pressure. That’s not a verdict on you.

Why You’re Not Getting Feedback

Candidates torture themselves trying to extract a lesson from rejections that contain none. However, the lack of feedback is mostly legal and structural, not personal.

Employers are routinely advised by lawyers and HR not to share the real reason, out of fear it could create legal exposure. If a rejected candidate believes they were passed over for their gender, race, age, or disability, that feedback becomes evidence, so companies issue blanket “give no feedback” guidance to be safe. Add to that the simple fact that by the time you’re rejected, the hiring team has already moved on, and spending more time on you is not a priority.

So the silence you’re agonizing over is usually a policy, not a personal rejection of you. There is frequently no hidden sentence you failed to read. There is just a legal department, a busy calendar, and perhaps even a company that doesn’t want to invest in building longer term relationships.

That should be freeing. You are not failing to decode a message because there is no message to decode.

Where To Actually Use Your Leverage

The unfortunate reality in the job market is that companies have all of the leverage right now. The imbalance between application volume and open roles gives employers the leverage to be slow, vague, and non-committal because they can afford to wait until they find the “perfect” candidate by their criteria.

You don’t fix that by getting angry at the system, and you don’t fix it by sending application number 201. You fix it by playing a different game than the one that’s rigged against you:

1. Stop feeding the funnel that’s designed to reject you. The cold application is the lowest-signal, highest-competition path in the entire system, and it’s the one most candidates pour all their energy into. Applying through a referral or a warm connection increases your interview rate by several times over a cold application. The leverage isn’t in volume. It’s in being a known quantity before the pile even forms. Every hour you spend on your 50th cold app is an hour not spent becoming someone a hiring manager already wants to talk to.

2. Make the no’s give you information, even when they won’t. You usually won’t get feedback, but the way you ask changes your odds. Don’t ask “why didn’t I get it?” That triggers every legal reflex they have. Ask for advice instead: “I really valued this process. If you were in my seat targeting roles like this one, what’s the one thing you’d sharpen?” Framing it as a request for advice rather than a demand for a reason is far more likely to get a real answer. One honest sentence after a loss is worth more than ten of your own assumptions.

3. Build leverage where companies can’t take it from you. Your reputation, your network, and your visible work are the only assets in this process that a hiring committee doesn’t control. Consider a post about a problem you solved or a teardown of a product you admire. Build real relationships with people at the companies you’d actually want to join. That’s the surface area that gets you pulled in through the side door, where you’re being evaluated as a person, not sorted as a row in an ATS.

4. Pick your targets carefully. The candidates winning this market stop applying to 200 big-name roles and start building real relationships at 20 carefully chosen companies. Build a target list, know what company size you want, and leverage your strengths when targeting a domain or industry. Go where the pile is smaller, your reputational leverage is greater, and the right people are more reachable.

The Bottom Line

The rejections are real, there are a lot of them, and they hurt. But the stack of no’s in your inbox is not the verdict you think it is. Most of it is math, policy, and timing wearing the costume of a personal judgment.

The market is giving companies the leverage. But the response to a system that holds all the cards at the front door is to stop playing at the front door. Your leverage is in relationships, reputation, and targeting, and none of that shows up in the 2 percent that the funnel rejects on application submission.

You will get more of these emails. Read them for what they are, take the rare piece of real signal, and put your energy where you actually have a say. The candidates who get through this market aren’t the ones who never get rejected, but rather the ones who stop letting rejections define their search.

Good luck out there — and always remember, keep grinding, but make it count.

A growing share of any product org’s actual output is now being produced by agents: narrow, scoped, semi-autonomous systems that take a task, do a thing, and report back. As that share grows, the PM’s job is turning into something different than it was: less product manager, more agent manager.

This is the most consequential shift to the PM role since the move from outputs to outcomes. Let’s break this down.

What’s Actually Changing

For years, PMs have flirted with AI features: recommendation engines, smart defaults, the occasional ML-powered ranking model. That work was real, but it lived inside the existing PM motion. You scoped it, you spec’d it, you shipped it, and it became a feature in your product like any other.

What’s happening now is structurally different. The model is no longer a feature inside the product, but rather a worker inside the org.

Anthropic’s framing in their “Building Effective Agents” essay is a useful starting point: an agent is a system that uses tools to take multi-step actions toward a goal, with some degree of autonomy. Read that definition twice and it stops looking like a feature and more like a job description.

These “jobs” that agents are taking are in the form of workflow agents that route customer tickets, research agents that produce competitive teardowns, coding agents that close low-risk bug tickets overnight, summarization agents that turn meeting transcripts into status updates, and internal ops agents that reconcile data across tools. These are now features inside your product and your org, doing work that used to belong to a person.

Someone has to scope them, onboard them, evaluate them, expand them, and retire them. In most of the companies I’ve talked to over the last six months, that someone is becoming the PM, sometimes by design, but more often by default.

What “Agent Manager” Actually Means

An agent manager is a PM whose job has expanded to include the operating responsibility for a portfolio of agents that contribute to their product’s outcomes. They don’t replace engineering, design, or research. They don’t write production model code. But they own the lifecycle, including deciding which agents exist, what each one is responsible for, how each one is measured, and when each one gets promoted, scoped down, or shut off.

In practice, this looks like a PM who:

• Holds a written charter for every agent in their product, the same way they’d hold a PRD for every feature.

• Maintains a regression set of evaluation cases for each agent and reviews the results on a regular cadence.

• Decides when a human stays in the loop on a class of decisions and when the agent is trusted to ship without one.

• Coordinates with engineers on what tools and context the agent has access to, the same way they coordinate with designers on what surfaces the user sees.

• Knows the unit economics of each agent: what it costs to run, what work it offloads, and whether the math still works.

The Management Stack, Reimagined

Every part of the traditional management stack has an analog when the direct report is an agent.

• Hiring → Spec’ing. Instead of recruiting an agent, you scope one. The bar is the same as a great hire though: a clear charter, a clear success metric, and a clear set of things it is not allowed to touch. PMs who write fuzzy specs get fuzzy agents. PMs who can write a tight scope ship agents that hold up and compound over time. If you’ve ever struggled to write a sharp PRD, this part of the job will expose it fast.

• Onboarding → Context engineering. The system prompt is the new PRD. Half of an agent’s performance is determined before it ever runs, by the context you load it with: the company voice, the product constraints, the decision rules, the examples of “good,” and the edge cases that have burned the team before. This is the part of the job most PMs are sleeping on, and it’s where the biggest performance delta lives between an agent that feels magical and one that feels embarrassing.

• 1:1s → Eval loops. Humans drift in visible ways, while agents drift in silent ones. A teammate slipping on their work will eventually show up in a sprint retro, a missed deadline, or a quiet conversation. An agent slipping will show up nowhere unless you’ve built the scaffolding to catch it. The only reliable way is a saved regression set: a set of use cases that represent the work you actually care about, re-run on a cadence, with results reviewed by a human. If you don’t have these, your agent won’t know the ground truth.

• Performance reviews → Capability expansion. You “promote” an agent by widening its scope and watching the failure rate. The rubric you’d use to decide if a human is ready for the next level is structurally the same as the one you’d use to decide if your triage agent is ready to also handle routing, or your research agent is ready to start drafting recommendations. Most PMs already know how to do this work for humans, and the skill transfers cleanly to agents.

• Coaching → Feedback design. Some agents learn from feedback loops you build into the product itself, whether thumbs up/down, accept/reject, or edit/keep. Others learn from how you adjust their context and rules over time. Either way, coaching the agent is a deliberate act of design rather than an off-the-cuff conversation. PMs who can engineer those loops end up with agents that improve in production.

• Firing → Decommissioning. Agents accrue over time. They sit in the stack long after they’ve stopped earning their value, because nobody owns turning them off and because nobody wants to be the one to admit a previous bet didn’t pan out. The PM who kills an underperforming agent earns the same kind of credibility lift as the manager who finally has a hard conversation with a struggling teammate.

The New PM Skill Stack

Zooming out, this new way of working concentrates around four skills, most of which are not necessarily going to be “taught” by your company:

1. Context engineering. Writing the brief that determines 80% of the output before a single token runs. This is the closest thing to a genuinely new PM skill, and it rewards exactly the people who have always written sharp PRDs and clear rubrics.

2. Eval design. Turning “good” into a rubric and a regression set, so quality isn’t a vibe. Borrow from how senior engineers think about evals, and then translate it into the PM frame: what does this agent need to do well, and how would I prove it’s doing so next week and three months from now?

3. Trust calibration. Knowing where to keep a human in the loop, where to let the agent ship, and when to move that line. Too much human-in-the-loop and you’ve built an expensive autocomplete. Too little, and one bad agent run hits the customer before anyone notices.

4. Hybrid org design. Deciding which work routes to humans, which routes to agents, and which lives in a deliberate handoff between the two. Route too much to humans and you’ve given up the leverage AI is supposed to provide. Route too much to agents and you’ve given up the taste and judgment that made the product worth using in the first place.

What This Means for Your Career

The unit of leverage in product is moving from “what did I ship” to “what did my fleet ship.” That’s a management job. It looks a lot like engineering management for non-human reports (scoping, evaluating, promoting, retiring) except the cycle time is in hours instead of quarters and the direct report doesn’t need a 1:1.

PMs are unusually well-positioned for this transition. We have always managed without authority. We have always written the brief that drives the output for others. We have always been graded on outcomes we couldn’t fully control. Switch from humans to agents and the underlying muscle is mostly the same.

What changes is the leverage. A great PM with a strong fleet of agents can produce the throughput of a team that is two or three times their size, but only if they’re willing to do the actual management work behind the scenes. The PMs who treat agents as a side project, or as a vague “AI initiative” they’ll get to next quarter, will spend a year producing more or less the same output they did the year before.

Your organization, and ultimately the job market, is going to notice the difference.

The Bottom Line

The title doesn’t have to change yet, but the job already has.

The PMs who thrive in 2026 and beyond are the ones who can run a fleet of agents like a small team, with a charter for each, a regression set behind each, and the judgment to know when to widen scope, when to keep a human in the loop, and when to shut something off.

The product role isn’t going away. It’s expanding. The PMs who expand with it will have the same edge they’ve always had: sharper judgment, faster execution, and better outcomes.

If your week now includes more time spent shaping what agents do than shaping what humans do, that’s a good sign. Keep it going, and encourage others around you to do the same.

Good luck out there — and always remember, keep grinding, but make it count.

P.S. If you’re in the job market looking for a new role, join our talent network, and we’ll be in touch! We partner with NYC startups to help them hire top tech talent: product, engineering, sales, and more. We’d love to get to know you!

And every time, the email lands: “We’ve decided to move forward with other candidates.”

You ask for feedback, but you get nothing back. You replay every round looking for the moment it broke, but you can’t find it. You’re looking for where your story was supposed to be told, but nobody told it for you.

If you’re navigating this crazy job market, you already know this feeling. The job search isn’t broken because there aren’t enough roles or because the interviews are too hard. It’s broken because nobody is going to advocate for you in this process unless you do.

Most candidates are running their search as if the process is supposed to surface them - as if a clean resume, a polite recruiter screen, and a few strong rounds will add up to an offer. They won’t. The candidates who actually win this market are becoming their own advocate from the first conversation forward.

Let’s break this down.

Nobody Else Will Tell Your Story For You

The uncomfortable truth most candidates don’t want to sit with is that every other person in the process has a fragmented, partial picture of you.

The recruiter has 20 other candidates this week and a 30-minute job brief from the hiring manager. The first-round interviewer is going to scan your resume for 5 minutes before the call. The panel debating you after onsite is going to argue from three different impressions, none of which include the parts of your story that matter most. The hiring manager is going to fill in the gaps with assumptions, and those assumptions can go in any direction.

You can be frustrated about this, or you can do something about it.

That something is advocacy, but not from a recruiter, a friend, or a coach. From you. Self-advocacy is the work of making sure that by the time anyone in the process is making a decision about you, they have a clear, accurate, compelling picture of who you are and what you’d do in the seat. And it is almost entirely on you to produce.

What Self-Advocacy Actually Means

Self-advocacy is not bragging, and it’s not performance. It’s three specific responsibilities that most candidates either skip or do badly:

1. Own your narrative. Your career has an arc. You probably can’t articulate it in 60 seconds or in a way a stranger could repeat back to someone else. That’s a problem, because that 60 seconds is the artifact every person in the loop is going to use to summarize you when you’re not in the room. If you don’t write it, they’ll write it for you, and you won’t like what they write.

2. Pitch yourself, directly and often. The strongest candidates don’t wait for the process to deliver them to the hiring manager. They make their case directly through warm intros they engineer themselves, through a LinkedIn DM that lands with specificity, or through a piece of writing or a side project that reaches the right founder. The “front door” is the lowest-signal path in the entire system, and most candidates only use the front door.

3. Set expectations on your terms. This is the one I see candidates miss most. They walk into every conversation letting the other side define the frame: what level, comp, timeline, and fit looks like. The strongest candidates do the opposite. They show up with an internally-grounded sense of what they want and what “great” looks like for them, and they communicate it early. That changes how the entire conversation gets evaluated.

Most candidates are running a search without doing any of these three jobs. They have a resume but no narrative. They have applications out but no direct pitches. They have answers but no frame. And then they’re surprised when they lose to candidates who have all three.

Why Self-Advocacy Feels Uncomfortable

Most candidates are bad at self-advocacy for a structural reason: the job trained you to be the opposite.

For example, a good PM gives credit, a good PM points to the team, and a good PM frames wins as collective and losses as personal. That instinct serves you well inside a company, but it actively hurts you in a search, where the only person who can articulate exactly what you did and why it mattered is you.

The candidates who break through hold both stances. They are still collaborative and team-first inside the company they end up joining. But during the search, they are willing to be specific, even uncomfortable, about what they actually owned. “I drove this from zero to one.” “I was the one who made the call to kill that project.” “I rebuilt the team after the last lead left.” None of that reads as bragging when it’s specific, accurate, and offered in service of a clear decision the other side has to make.

If you can’t say those things out loud about your own career, the hiring manager has no other source for that signal. They are not always going to dig it out of you.

The Self-Advocacy Playbook

If you’re searching right now, here’s what to do this week:

• Write your one-paragraph pitch and stress-test it. Not your resume. A paragraph a hiring manager could read in 30 seconds and immediately know what you’d own and why you’d be right for a specific kind of seat. If a smart friend who doesn’t work in tech can’t repeat it back after one read, it isn’t done. This is your single most important artifact, and many candidates miss this.

• Audit your story for drift. Look at your last three roles and ask whether they tell a coherent arc or a string of unrelated chapters. If the arc isn’t obvious, write the connective tissue yourself. Don’t leave it to the HM to fill in.

• Engineer your own warm intros. Make a list of the 10-20 companies you’d actually want to work at. For each, identify two or three people in your extended network who could make a real intro. Then go ask them, one at a time, with the pitch ready. The candidates that win take a proactive seat in getting intros.

• Pitch yourself in writing, in public. A post about a problem you’ve solved, a teardown of a product you admire, a thread about something you learned the hard way. You are not building an audience. You are giving a hiring manager something concrete to react to before round one. That signal can sometimes be evidence of how you think, and evidence does not always live on a resume.

• Set your comp range before someone else does. Have a researched range, give it confidently, and tie it to the level and scope you’re targeting. The number you give first is the floor of every subsequent conversation. Don’t anchor blind, and don’t outsource the anchor to AI to decide for you.

• Ask for honest feedback after every loop, win or lose. Most candidates don’t ask. The ones who do learn faster than everyone else in the market. Even one sentence of real feedback after a rejection is worth more than ten assumptions.

The Bottom Line

The candidates who win in this market are the ones who advocate for themselves at every step - owning the narrative, pitching direct, and selling their story.

No one else in the process is going to do this for you. The system is not designed to surface you on its own. The job search rewards agency. It always has, and in a market this tight, the gap between the candidates who exercise it and the ones who wait has never been wider.

If you’re searching right now and the rounds keep ending in form rejections, the answer is almost never to simply “interview more.” It’s advocate harder for yourself. Write the pitch. Engineer the intros. Ask the questions. Tell your real story.

DM me on LinkedIn if you want help with your positioning - I’d be happy to help!

Good luck out there — and always remember, keep grinding, but make it count.

The numbers back up the pit in your stomach. Roughly half of new hires don’t make it past 18 months, and at early-stage startups the failure cycle is often much shorter — weeks and months, not years. The cost of a single bad hire lands between half and two times that person’s annual salary, before you count the runway and momentum you can’t get back. Offer acceptance for senior roles has dropped from 74% to 51% in two years. Every one of those numbers is somebody’s small grief: a founder who picked wrong, a candidate who uprooted their life, a team that absorbed the chaos.

What breaks, in nearly every case, is that neither side actually knows the other until it’s too late.

The hiring conversation in 2026 is obsessed with process. Better ATS, tighter rubrics, AI-augmented screens, leaner loops. All of it matters. But the most expensive failure mode at the early stage isn’t a process gap. It’s that hiring has quietly become transactional in a domain where it absolutely cannot be.

The Process Obsession Is a Cope

Spend ten minutes on Founder Twitter and you’ll see the same thread shape on repeat. The JD is too generic. The ATS is filtering out the wrong people. The take-home is too long, too short, too irrelevant. The recruiter is moving paper instead of building signal. The candidates are AI-spamming applications. The funnel is broken.

All of that is true. I’ve written about a lot of it. But beneath all of these complaints is a deeper move: founders are trying to fix relationship problems with workflow tools.

You can’t ATS your way to trust. You can’t rubric your way to “this person has my back when it gets hard.” You can’t take-home your way to “this is someone I want in the room at 11pm on a Thursday before a launch.”

The process discourse is so loud because the relational layer underneath it has eroded, and nobody quite wants to name that. Process is something we can change. Relationships feel like something we’re supposed to already have.

Hiring Is a Trust Transfer, Not a Filter

When hiring works, it doesn’t actually look like filtering. It looks like trust moving through a network.

A founder I trust vouches for a PM I’ve never met. I take the intro at high signal because the founder has skin in the game with me. Their reputation rides on the intro, not just on the candidate. The PM shows up to the first conversation already understanding what I’m trying to build, because the founder spent 20 minutes briefing them, not 20 seconds forwarding a JD. By the end of round one, we’re calibrating a hypothesis that already has weight on both sides.

Compare that to the default flow. A stranger applies through a job board, gets pattern-matched against keywords, lands in front of a recruiter who has 20 of these calls this week, and is asked to differentiate themselves in 30 minutes against a target they cannot see.

The first version is a trust transfer while the second is a transaction. Both produce a “hire” at the end, but only one produces a relationship that survives the first hard quarter.

Spray-and-Pray Is the Unfortunate Default

Ultimately, many founders default to spray-and-pray sourcing. Why? Because relationships don’t scale on demand, and hiring almost always feels urgent.

Founders have runway pressure, board meetings coming up, and features that need to ship in a matter of weeks. They claim they need engineers and PMs yesterday. So they post the JD, blast LinkedIn, and hope the funnel does the work their network was supposed to.

The tradeoff founders are implicitly making is “I’d rather see 200 strangers fast than eight vouched-for candidates when the time is right.” It feels rational under pressure. But the math on early-stage hires doesn’t agree. A mis-hire on a founding team can cost half to two times the person’s annual salary, plus three to six months of momentum you cannot get back. Eight vouched-for candidates produced over four weeks beats 200 strangers produced over the weekend on almost every metric that actually matters.

The reason founders don’t do it more is that they don’t have a system to make the relational route as fast as the transactional one. That’s a fixable problem.

Why NYC Is a Uniquely Dense Trust Graph

If you’re building in New York right now, you are sitting on top of one of the densest trust graphs in tech, and most founders are dramatically underusing it.

Consider what’s actually here:

• Repeat founders across fintech, media, healthcare, consumer, and now an enormous wave of applied AI.

• Operators who’ve cycled through Stripe, Ramp, Datadog, Squarespace, Peloton, Plaid, Vimeo, Notion, and a long tail of growth-stage companies that have produced hundreds of senior PMs, engineers, and designers.

• Early-stage investors who actually know their portfolios at the individual level, not just the deck level.

• Communities like On Deck NYC, South Park Commons, NY Tech Week, and founder dinners that happen every week of the year.

Crucially, NYC is still an in-person culture. People physically run into each other. Coffees happen on short notice. A founder dinner on Tuesday produces intros by Thursday because the people in the room saw each other’s body language when the name came up, not just a Slack DM.

This matters because trust depreciates faster over digital surfaces than it does over physical ones. NYC’s advantage is relational compression - fewer degrees of separation between any two operators who are serious about building, and a culture that still treats showing up in person as table stakes.

For early-stage hiring, that compression is the whole game. Your founding PM is almost certainly two warm intros away from you, in this city, right now. The question is whether you have a system to find them before you give up and post the JD.

What Relationship-First Hiring Looks Like

When relationship-first hiring works, it doesn’t feel like a heavier process. It feels like the loop got shorter on its own.

The candidate shows up to the first call already understanding the product, the stage, and the founder’s actual concerns because the person who made the intro briefed them like it was their own hire. The founder isn’t trying to “evaluate” in the first conversation. They’re calibrating a hypothesis that already has a baseline of trust on both sides. The references are not three people the candidate hand-picked from their last job. They’re operators the founder already knows, who can tell you what this person is like at 11pm on a hard Thursday.

The downstream effects are real. Offer acceptance goes up, because the candidate has been pre-sold on the founder by someone they trust. First-year retention goes up, because both sides walked in with calibrated expectations. Time-to-productivity drops, because the context handoff started before day one. And the next hire is easier, because the person you just hired now becomes a node in your trust graph, with their own warm intros for the next role you open.

This is the compounding part that the funnel never gives you. Each relational hire makes the next one cheaper. Each transactional hire makes the next one harder, because you’ve spent network capital and gotten a stranger in return.

Building the Right Hiring Engine

If you’re a founder hiring now or about to hire:

1. Engage your network, but do it often and not only when you need favors. Most founders only ping their network when they’re desperate. The ones who hire well are in constant low-grade circulation - coffees, dinners, and intros they didn’t strictly need. So when a role opens, the network is already warm.

2. Define the bar with operators, not just with yourself. Before you open the role, have three or four conversations with operators you trust about what “great” looks like for this specific seat at this specific stage. You’ll write a sharper internal brief, and you’ll seed the search through people who can now actually make a meaningful intro.

3. Make your intros expensive. When someone vouches for a candidate, treat the vouch as part of the signal. Ask the introducer what they specifically saw that made them send this person. The quality of the vouch is often more predictive than the candidate’s first round.

4. Do real reference work early, not late. References at the end of a loop are theater. References early in the loop reshape the loop. If three operators you trust have specific, unprompted stories about this person, you’ve already learned more than a take-home will tell you.

Don’t outsource the relational layer; augment it. This is where outside help can actually compound your network instead of replacing it, if you pick the right partner. A good hiring partner brings their trust graph into your search and operates on the same relational layer you would, just at higher leverage. A bad one runs a faster funnel on the same broken artifacts and hands you back a shortlist of strangers.

The Bottom Line

The reason early-stage hiring feels broken isn’t that the process has too few rounds or too many. It’s that the process has been carrying weight only relationships can actually hold.

Process is necessary, and getting it right matters. But process is the scaffolding. The structural load is relational. And in a market where every founder is running roughly the same playbook, the ones who win the early hires are the ones who hire from a trust graph instead of a job board.

If you’re building in NYC, you have an unfair advantage on this dimension, and most founders are leaving it on the table. The density, the repeat operators, and the communities are all here. The in-person culture is also here. The only thing missing is a deliberate system for routing your hiring through it.

If you’re actively hiring in NYC or planning to soon, let’s talk. Reply to this post or DM me on LinkedIn. I’d rather help you turn one warm intro into your founding engineer than watch you post another JD into the void.

And if you’re a candidate navigating the crazy NYC market, I’d love to get to know you and help you find the right next role. Submit your info on my website and we’ll reach out if there’s a fit: https://hirewithstride.co/

Good luck out there — and always remember, keep grinding, but make it count.

You take the call, it feels fine, and you answer the questions. You leave thinking that went well, now I just have to wait for the real interviews.

A week later, you get an automated email: “We’ve decided to move forward with other candidates.”

Confusion hits: you replay the call and you feel that nothing went wrong, exactly. You just don’t know what went right. And you never will, because nobody’s going to write you a postmortem on a 30-minute screening call.

If this sounds familiar, you’re not alone. The recruiter screen is the most underestimated round in the entire PM interview loop, and it’s the one I see candidates lose more often than any other.

The reason is simple. Every other round has a clear bar. Product sense, behavioral, case, take-home. You can study for them, debrief them, and improve. The recruiter screen has no such bar. It feels casual, sounds conversational, and gets dismissed as logistics. So candidates phone it in, and then wonder why the “real” loop never started.

Why the Screen is Brutal on Both Sides

The recruiter screen is the first filter, and it’s the last safety net before your profile hits the hiring manager. If you don’t win it, nobody tells you the real reason. You just get the form rejection, or worse, you get nothing at all.

Behind the scenes, the dynamic most candidates miss is that the recruiter usually doesn’t deeply understand the role they’re hiring for. They typically get a 30-minute briefing from the hiring manager when the role is first opened, get a JD that’s probably been pasted from the last open req, and have a fuzzy mental model of “good.” Then they’re expected to evaluate dozens of candidates against it.

That’s not a knock on recruiters. It’s the structural reality of the job, and oftentimes they don’t get an opportunity to go deeper than that. They’re typically pattern-matching against a target they only half-saw. The good ones know this and ask sharp questions to compensate. The rest are running off the JD and vibes.

And on the candidate side? You have even less. You don’t know what the recruiter actually understands about the role. You don’t know what signals they’re listening for. You don’t know whether the brief they got from the HM said “we need a marketplace person” or “we need someone who’s shipped from zero to one.” You don’t know if the role got reshaped last week, if the level is flexible, or if the HM is actually involved in the search at all. You’re answering questions blind, hoping the answers map to a target you can’t see.

As a result, both sides are operating on incomplete context. The screen happens in that gap. And the candidates who win are the ones who close the gap, not the ones who hope the gap doesn’t matter.

What Recruiters Are Actually Listening For

Recruiters are not product experts. They’re not going to evaluate the technical depth of your last roadmap call or push back on your prioritization framework. They’re listening for signal clarity: can they understand you, position you, and pitch you to the hiring manager in a few sentences?

That’s the bar. Rather than measuring you on whether you gave great answers, recruiters are looking for signals that they can use to summarize you in their post-call notes or Slack message to the hiring manager. Something like “Strong marketplace background, shipped 0 to 1 at a Series B, looking for staff-level scope, comp aligned, can move in 4 weeks.” That’s the message they’re trying to write while you’re talking.

Your job in the screen is to write that summary for them.

That changes everything about how you should show up:

• Concision beats comprehensiveness. Most candidates talk too much. Every extra minute you spend on an answer dilutes the signal the recruiter is trying to extract. If your “tell me about yourself” runs 10 minutes, you’ve buried the headline. The recruiter is now trying to reverse-engineer your story from a pile of context, which is exactly the work you were supposed to do for them.

• Your “tell me about yourself” is a positioning statement, not a career history. One through-line, clear progression, and a clean landing. If a recruiter can’t repeat your story back in their own words after you finish, you didn’t tell a story, but rather just verbalized your resume. The test I use: can you deliver it in 90 seconds, and would a smart friend who doesn’t work in tech understand the arc?

• Energy and clarity beat thoroughness. Recruiters oftentimes remember how you made them feel more than what you said. The candidate they fight for is the candidate who made the call easy and made them feel sharp. Recruiters take many calls a day. The candidate who shows up clear, warm, and confident is genuinely a relief to talk to, and that relief turns into advocacy when your name comes up in the next pipeline review.

The Traps Hiding in Friendly Questions

Most of the screen’s damage happens in a few questions that sound like small talk and aren’t:

• “What are you looking for in your next role?” This is a positioning test. If you ramble, you signal you’re shopping. If you’re too specific, you signal rigidity. The right answer is a tight version of what you actually want, said with enough conviction that the recruiter can immediately match or unmatch you against the role. Vague answers here are how candidates get politely filed away. The structure that works is 1-2 sentences on each of the following: the type of problem, the stage or environment, and the kind of team. Concrete enough to be real, open enough to fit the role they’re hiring for.

• “What’s your comp expectation?” The comp conversation is a negotiation that most candidates lose before they realize it started. Anchor too low and you’ve capped your offer before you’ve even interviewed. Anchor too high and you get screened out for fit. Be evasive and you get flagged as a hassle. The move is to have a researched range, give it confidently, and tie it to the level you’re targeting. Levels.fyi and your network are your friends here. And remember: the number you give in the screen becomes the floor of every subsequent conversation.

• “Why are you looking?” Don’t trash your current employer. Don’t sound like you’re running from something. Frame it as motion toward something specific, like a product problem, a company stage, or team dynamic. The recruiter is listening for whether you’ll be a flight risk in their company too. The pattern I’ve seen work: acknowledge what’s been good about your current role, then articulate the specific gap you’re trying to close. That signals you’re thoughtful, not reactive.

The Screen is a Two-Way Fit Conversation

The recruiter screen is a two-way filter, and you’re under-using your half.

This is the easiest round in the entire loop to extract intel from because the recruiter’s job is to keep you engaged. They might answer questions they wouldn’t answer later, and they have visibility into the broader hiring picture that the HM might not share directly.

• Ask about the hiring timeline. Their answer tells you how serious they are. “We’re hoping to close in 6-8 weeks” is a real process. “We’re still figuring out the scope” is a process that will ghost you or drag you along. Timeline answers also let you sequence your own pipeline. If one company is moving in two weeks and another is moving in two months, you know where to push and where to pace.

• Ask why the role is open. New headcount? Backfill? If backfill, what happened to the last person? You’ll learn more about the team’s actual dynamics in 90 seconds than you will in three rounds of behavioral interviews. “The last PM left after eight months” tells a different story than “we just got Series B funding and are doubling the team.”

• Ask what the rest of the loop looks like and who’s on it. This tells you what each round will focus on, which lets you prep with precision instead of casting a wide net. If there’s a panel with the head of design and the head of engineering, you know cross-functional dynamics will get tested. If there’s a take-home, you know to clear your weekend.

• Ask what kind of profile they’ve been seeing in the pipeline. Recruiters will usually tell you. And you can use this for future reference when you are targeting other jobs. Now you know your competitive set, and you know how to differentiate. If they’ve been seeing a lot of big-tech PMs and you’re coming from a startup, lean into the operator angle.

• Ask what the hiring manager is most worried about getting wrong on this hire. Recruiters often actually know the answer, because the HM told them when they kicked off the search. And the answer will reshape how you prep for every subsequent round. If the HM is worried about hiring someone who can't operate without a playbook, you now know to lead with stories about ambiguity. If they're worried about someone too senior to roll up their sleeves, you know to emphasize craft. This is the single highest-leverage question you can ask in a recruiter screen.

Finally, listen for what they don’t know. If the recruiter is vague about the role, the team, or the timeline, that’s a yellow flag on the company. A disorganized screen often signals an org that hasn’t aligned internally on what they’re hiring for, which means the offer (if it comes) will arrive late, the level will get re-debated three times, and the role will probably get reshaped before (or even worse, after) you start.

The Bottom Line

The recruiter screen is where the largest gap exists between how candidates treat it and how much it actually matters. It’s the first filter, the last safety net, and your single best opportunity to turn a recruiter from a gatekeeper into an advocate.

Most candidates lose this round because they gave the recruiter nothing memorable to fight for. The ghost-after-the-screen pattern almost always traces back to that.

Don’t be too deferential. You’re evaluating them too. Make their job easy. Speak in headlines, not paragraphs. Treat the call as recon as much as performance. And remember that on the other side of the line is someone with their own incomplete picture of the role, doing their best to pattern-match you against a loose target.

The candidates who win the screen are the ones who help the recruiter see them clearly and then walk away with a sharper picture of the company.

That’s the round. Don’t literally phone it in.

Good luck out there — and always remember, keep grinding, but make it count.

I’ve been the candidate in PM interview processes across big tech, growth-stage startups, and everything in between. I’ve been the hiring manager on the other side of the table, trying to evaluate strangers in a 45-minute product sense or strategy interview. I’ve been the coach helping PMs figure out if the opportunity in front of them is real. And I’ve been the advisor sitting with founders as they make their early team hires.

The contexts were different, but the frustration was identical.

It always showed up in the same place: both sides were making a high-stakes decision with almost no real context. Resumes weren’t telling founders what they actually needed to know about a PM’s product judgment. Job descriptions weren’t telling candidates what they actually needed to know about the product, the team, or the founder. And by the time both sides had enough signal to make a good call, they’d already burned hours in a process that should have been sharper from the start.

This is the real problem with early-stage hiring in 2026, and it’s especially acute for product roles, where fit is hard to screen for and the cost of getting it wrong is high. It isn’t a sourcing problem or a volume problem, but rather a context problem.

Volume Is a Symptom, Not the Cause

Let’s start with what the PM market looks like, because it’s easy to misread.

The average corporate job posting gets 250 applications. Product roles at well-known startups routinely blow past that. Around 75% of those resumes get auto-rejected by the ATS before a human sees them. Of the ones that get through, only 2-3% make it to an interview (down from 15% a decade ago). Average time-to-hire sits at 41-44 days, and for senior product roles, it regularly exceeds 60.

For a founder, this looks like an overwhelming volume problem. The inbox is full of “PMs”, from APMs with 18 months of experience all the way up to ex-VPs of Product looking to drop a level. Signal is impossible to find, so the instinct is to filter harder, tighten the keywords, add another round. Or perhaps if all else fails, hand the stack off to a recruiter and hope they compress it.

Ultimately, the filters everyone is using are broken. They’re built on a resume and a job description, two artifacts that were never designed to carry the context you actually need. This yields the wrong representation of PMs, and the wrong representation of the role you want to hire for. It’s not just a volume game.

What Resumes Don’t Tell You About a PM

A resume tells you where a PM worked, but it doesn’t tell you what they actually owned. It tells you their title, but as I’ve written before, PM titles mean wildly different things at different companies. A “Senior PM” at one place might have 3 years shipping side features while a “Senior PM” at another might have 8 years owning a nine-figure P&L.

The traditional resume tells you what someone worked on, but doesn’t tell you whether they were the driver or the passenger on the feature they’re claiming credit for. It doesn’t tell you how they think about prioritization, how they handle a founder changing direction three days into a sprint, or whether they’d survive the specific chaos of your specific startup at your specific stage. It tells you their tech stack, but doesn’t tell you whether they can actually build a prototype, run a customer call, or operate as a 360 PM instead of a coordinator.

For a founder making a founding PM hire, the resume is the most important input they’re using. And it’s telling them almost nothing that matters, even though getting the decision wrong can cost between half and two times the person’s annual salary. The same dynamic applies to early engineering and design hires, but for PM it’s worse because product judgment is the single hardest thing to infer from a page of bullets.

What Job Descriptions Don’t Tell Candidates

The gap on the candidate side is just as bad, and almost no founder realizes it.

The PMs a founder actually wants to hire aren’t desperate. These are the ones with 5-8 years of shipping experience, who’ve operated at both scale and startups, or who can code well enough to build a prototype. They’re also likely employed, and when they evaluate a new opportunity, they have a short list of things they need to know fast:

What is this company actually building, and is the product insight real? Is this actually a product role or is it really a chief of staff role? How involved are the founders going to stay in product decisions?

None of these questions are answers in a JD. Instead, what’s in the JD is “5+ years of product management experience,” “excellent communicator,” and “data-driven mindset” — language that could describe almost any PM role at almost any company.

So what do the good candidates do? They infer and triangulate from ChatGPT, LinkedIn, and podcast clips. A lot of them decide the role isn’t worth 20 hours of their time, and the founder never knows they were in the consideration set.

For the ones who do engage, it takes three or four conversations before they have a real picture. By then, both sides have invested emotionally, regardless of whether it’s actually a fit. It’s how you end up with offers that don’t get accepted (acceptance rates dropped from 74% to 51% in two years), and hires that don’t work out.

Why the Existing Options Don’t Close the Gap

The instinct when the process is broken is to outsource it. Founders hiring their early team try a few things, and each of them fails to address the context problem:

• Job boards and inbound. The artifact a job board asks you to produce is a JD. The artifact it hands back is a resume. The entire system is built on top of the two documents that don’t carry the context either side needs. You get volume and you get noise, but you get none of the signal that actually helps you decide.

• Internal recruiting. Most early-stage companies don’t have a dedicated recruiter. When they do, that recruiter is usually wearing three other hats and sourcing across every function. They don’t have the product judgment to pull founder context out of the room, translate it into a search, or evaluate candidate context on the way back. They’re moving paper, rather than building understanding.

• Traditional recruiting firms. A good firm compresses volume and brings you a shortlist instead of 250 resumes. But look a little deeper and they’re actually filtering on a boilerplate JD, a generic screening process, and the same resume pool everyone else is looking at. The shortlist is a more curated version of the same artifact mismatch. Faster, but not necessarily closer to the right hire for a specific product and stage.

None of these options are bad at what they do; they’re just all architected to solve the volume problem. The context problem is a different problem, and it needs a different approach.

What Has to Be True

The founder’s real context (not the generic JD) has to get captured before a single candidate is looked at. What is this product actually becoming, what does the founder need this PM to own in year one, what kind of operator is going to thrive here? The search and screen have to be built around that context, not keyword-matched against it. And what gets delivered back can’t just be resumes; it has to carry enough evidence of how each PM actually thinks and operates that the founder can make a real call without running four interviews to get there.

That’s a different kind of process. It doesn’t scale the way a job board scales, and it doesn’t look like a traditional recruiting engagement. But when it works, the whole funnel changes shape: fewer candidates, dramatically higher hit rate, shorter time-to-hire, higher offer acceptance, higher first-year retention. Because you’re no longer trying to force a yes out of a mismatched pool.

The founders who figure this out for product (and eventually for their early engineering, design, and GTM hires) are going to have a compounding advantage over the ones who don’t.

Why I'm Writing This Now

I’ve been carrying this thesis for a while, but I’m writing about it now because I’ve jumped into the arena to fix this broken hiring process.

Over the last few months, Wesley Repass and I have been quietly building a company specifically around the context problem I’ve described in this post. Our company is called Stride, and it’s an AI-augmented hiring service for startup founders and early teams. We capture company and role context upfront, turn it into a tailored search and screening process, and deliver qualified candidates with the evidence founders need to decide who to interview.

We’re working with a small number of founders right now, but I’d love to hear from you if you’re currently hiring or about to hire soon. Reply to this post or DM me on LinkedIn, and I can share more about how we’re rethinking the hiring process.

Good luck out there — and always remember, keep grinding, but make it count.

Every founder and PM has heard the advice. “Focus on your customers, not your competitors.” It’s become one of those things people say in product circles that is technically correct, but universally ignored when it counts, and usually offered by someone who isn’t the one staring at a competitor’s launch announcement at 9 PM wondering if their roadmap just became irrelevant.

I’m not here to give you the sanitized version. The truth is that competitor obsession is rational. It makes sense. When you’re early-stage with limited runway, limited team, and limited time, watching someone else ship a feature that overlaps with your core value prop feels like an existential event and survival instinct tends to kick in.

But if that instinct is left unchecked, it will kill your company faster than the competitor ever could. Because reacting to competitors means you’re always building their product, not yours. And you’ll never out-execute someone on their own vision of the market.

Let’s unpack this further.

Reaction Disguised as Strategy

The PM who can tell you everything about what Competitor X shipped last quarter but can’t tell you why their last three customers churned is optimizing for the wrong signal. They’re doing competitive intelligence when they should be doing customer intelligence. And the reason they’re doing it is because watching competitors is easier than talking to customers. It feels productive. You can put it in a spreadsheet. You can build a matrix. You can present it in a slide deck. It has the shape of strategy without any of the substance.

Competitive analysis is the most socially acceptable form of procrastination in product. Building a competitor matrix is a way that PMs avoid talking to customers.

You’re Copying Assumptions, Not Strategy

Your competitor’s roadmap is just their set of assumptions about the customer. That’s it. Every feature they shipped is a bet they made (probably six months ago) about what the market needs. Some of those bets are right. Most of them are guesses. A few of them are outright wrong and they know it but can’t course-correct because they already announced it publicly.

When you copy a competitor’s feature, you’re getting their homework, instead of their insights. And you have no idea whether they got the answer right.

Think about it this way: the feature they just launched tells you what they bet on six months ago. It doesn’t tell you what the market needs today. It doesn’t tell you whether that feature actually moved their retention. It doesn’t tell you whether their customers love it or are confused by it. You’re seeing the output with none of the context.

If your roadmap has ever been directly influenced by a TechCrunch article about a competitor, your prioritization process is broken. “They just shipped X” is a news headline, not a product requirement.

The Feature Parity Trap

Let me paint the picture I’ve seen play out at multiple startups.

Competitor ships Feature A. The founder panics. The PM gets pulled into a “quick sync” that turns into a two-hour war room. The team scrambles to build their version of Feature A. They ship it in six weeks. It’s fine. Not great, but fine. It doesn’t move the needle on acquisition or retention. Meanwhile, the thing that would have moved the needle (e.g. the customer pain point they’d been hearing about for months) sits untouched on the backlog.

This is the feature parity trap, and it’s a race to the bottom, where margins go to die.

You will never out-resource a better-funded competitor by copying them. That math doesn’t work. They have more engineers, more budget, and a head start on the thing they built. What you can do (i.e. what they usually can’t do) is out-learn them by staying closer to customers. That’s the asymmetric advantage of being small, and you throw it away every time you pivot to match someone else’s feature set.

The startups that win make competitors irrelevant by making the comparison feel wrong. They redefine what the customer cares about so that the old feature checklist stops mattering. That’s how they beat their competitors.

What’s Really Underneath the Obsession

When I talk to founders who are in constant reactive mode of always tracking competitor launches or adjusting the roadmap based on what someone else just did, there’s almost always something underneath it. And that something is usually a fear that if they actually sat down with their customers and asked the hard questions, they might not like the answers.

Competitors are a safer mirror. They show you what someone else thinks the market wants, which is less threatening than finding out what your own customers think about your product. Competitor analysis lets you stay in the realm of strategy and positioning. Customer conversations force you into the realm of truth.

The PM who’s truly dangerous (in a good way) is the one who’d rather hear a painful insight from a customer than a reassuring data point from a competitor teardown. That’s the person who builds products that actually win.

When Competitor Awareness Actually Matters

There are legitimate situations where you need to pay close attention to competitors.

• When a competitor ships something that directly addresses your core retention problem, and you’re seeing it show up in churn conversations. That’s real.

• When you’re losing deals specifically because of a feature gap. Not because a prospect mentioned it once, but because it’s a consistent pattern in your loss data.

• When the market is consolidating around a capability that you don’t have, and not having it is starting to mean you don’t get invited to the evaluation at all.

These are legitimate signals, and ignoring them is just as dangerous as overreacting to everything.

The appropriate method to managing this is to monitor competitors enough to know when they’ve found something real. However, you should let your customers tell you whether it’s real for your market. Those are two different things, and conflating them is where teams go off the rails.

Watching competitors is useful for market awareness, while letting them set your priorities is surrender.

The Real Advantage is Invisible

The best response to a competitor shipping your roadmap is to already be two steps ahead in customer insight, rather than in features. Features are visible. Insight is invisible. And the invisible advantage is the one that compounds.

The companies that win don’t out-feature competitors. They out-understand customers. They know things about their users’ workflows, frustrations, and unarticulated needs that the competitor hasn’t figured out yet, mainly because the competitor is too busy watching them.

If you’re reacting to every competitor launch, you don’t have a strategy, but rather a news feed. And a news feed is not a product vision.

Most competitor “threats” are only threatening if you were already solving the same problem the same way. If you’ve done the work to understand your customers at a level your competitors haven’t reached, their launches are just noise.

The Bottom Line

Competitor obsession is one of those failure modes that feels like the opposite of failure. It feels responsible. It feels strategic. It feels like you’re doing the hard work of staying informed and staying sharp.

But what it actually does is pull you away from the only source of truth that matters: the people who pay you money to solve their problems. Every hour spent dissecting a competitor’s feature is an hour you didn’t spend understanding why your customer almost cancelled last month. Every “quick pivot” to match a competitor’s launch is a sprint you didn’t spend on the thing your users have been asking for.

The startup that’s obsessed with competitors will always be one step behind because they’re optimizing for someone else’s vision of the market. On the other hand, a startup that’s obsessed with customers will eventually make the competition irrelevant. Not by beating them at their own game, but by changing the game entirely.

Stop doing someone else’s homework. Go talk to your customers.

Good luck out there — and always remember, keep grinding, but make it count.

P.S. If you’re a founder or PM caught in the reactive cycle and want help building a customer-driven product strategy instead of a competitor-driven one, I can help. Book an intro call if you want to chat!

Then the founder walks into standup the following week with a completely new direction because they just got off a call with a customer who said something that reframed everything …

The PM’s entire system collapses, sprint scope has changed, and the team is confused. The PM is frustrated and everyone starts questioning whether this company has any idea what it’s doing.

Here’s what actually happened: the founder did their job. The PM didn’t do theirs.

The Founder Isn’t the Problem

The founder changing direction isn’t a dysfunction, but rather a feature.

At a startup, the founder is processing information faster than anyone else in the building. They’re talking to investors, customers, advisors, and competitors, sometimes all in the same day. Their job is to absorb signal and update their priors constantly. If the founder isn’t changing direction based on new information, something is wrong.

Ultimately, the problem is the dependency on stability. If an entire sprint collapses every time the founder has a new idea, the backlog is just a queue, rather than a strategy. And the moment someone disrupts the queue, there’s nothing to fall back on.

Most PMs were trained in environments where stability was the default and change was the exception. At a startup, it’s the opposite. Change is the default. Stability is something created in small, deliberate pockets so the team can execute, not something that gets handed down from above.

A Roadmap at a Startup Is a Hypothesis Document

The roadmap is less of a commitment and more of a hypothesis of strategic bets.

The moment it’s treated like a promise, whether to the team, stakeholders, or others, you’ve already lost. Because now every direction change feels like a betrayal instead of an update. Now you’re emotionally attached to a plan instead of focused on the outcome the plan was supposed to produce.

At a big company, the roadmap exists to coordinate dozens of teams across shared timelines. It’s a contract. That makes sense when you have hundreds of engineers, multiple product lines, and dependencies that span quarters.

At an early-stage startup, the roadmap exists to create just enough shared context so that everyone is running in roughly the same direction. That’s it. The moment you over-engineer it or the moment you start treating it as a source of certainty, you’ve introduced something more dangerous than chaos: false confidence. Roadmaps create false certainty. And at a startup, false certainty is more dangerous than honest chaos.

Prioritize Bets, Not Features

The shift that separates startup PMs who thrive from ones who drown is that the best ones prioritize bets.

A feature is a thing you’re building. A bet is a hypothesis about why building that thing will matter. The distinction is everything, because when the surface area shifts or when the founder comes in with a new direction, the features might change, but the underlying bets often don’t.

Think of it as a living stack of ranked bets instead of a roadmap. Each bet has a thesis: “We believe that if we do X, it will produce Y outcome for Z reason.” When new information comes in, you’re re-ranking. Some bets get stronger, some get killed, or some get restructured. But the stack itself persists, which means the team doesn’t feel like the ground keeps shifting under them.

This is how you protect velocity without resisting change. The team always knows what bet they’re working on and why. When the bet changes, they understand the reasoning. When it doesn’t, they have conviction to keep building.

If you need buy-in from six people to reprioritize, you’re operating like a big company inside a small one. That’s a cultural bug, rather than a process problem. The bet stack lets you move fast because the decision framework is always live.

The PM as Buffer, Not Barrier

Most PMs think their job is to push back on the founder, whether to protect the team, hold the line on the roadmap, or bring order to chaos in the room.

This is wrong, or at least, it’s incomplete. The real job is to know when pushing back actually matters, and to pick those moments carefully.

The startup PM’s real job is to be a buffer. Absorb the founder’s signal. Translate it without losing fidelity. Protect the team from whiplash without protecting them from reality. There’s a meaningful difference between those two things.

The PM who shields the team from every pivot is actually shielding them from the information they need to do their best work. The team instead needs to be protected from unfiltered change. They need someone who can take the raw signal from the founder, separate what’s strategic from what’s reactive, and deliver it in a way that’s actionable without being disorienting.

This is the whole game: absorb, translate, re-route. Don’t hold the line or cave immediately. Be the person who processes the signal fast enough that direction changes stop being crises and start being inputs.

The Anxiety Pivot vs. the Strategic Pivot

Not all direction changes are created equal, and learning to diagnose which kind you’re dealing with is one of the highest-leverage skills a startup PM can develop.

• The strategic pivot comes from new data. A design partner says something that genuinely reframes the problem. A competitor makes a move that changes the market dynamics. Customer behavior reveals something the team didn’t see before. The founder processes this and updates the direction. This is healthy. This is how startups are supposed to work.

• The anxiety pivot comes from fear. The founder saw a competitor’s LinkedIn post and panicked. They had a bad investor meeting and now they’re questioning the entire product thesis. They’re three months from running out of runway and suddenly every customer request feels existential. The direction change is driven by emotional reactivity wearing the costume of strategic thinking.

The response to each is completely different. With a strategic pivot, your job is to move fast, update the bet stack, re-scope the sprint, and get the team aligned on the new direction. With an anxiety pivot, your job is to slow things down, ask clarifying questions, and pressure-test the new direction against the existing thesis. Give the founder space to land before the team starts executing on something that might reverse itself in 48 hours.

At a big company, you negotiate with data. At a startup, you negotiate with conviction and timing. Knowing when to sprint and when to hold is the difference between a PM who amplifies the founder and one who just amplifies the chaos.

Ruthless Triage Is a Skill

Most PMs were never trained to kill their own work mid-flight. In big company environments, once something is scoped and staffed, it has its own gravity. There are stakeholders invested, dependencies mapped, OKR commitments attached, and promotion opportunities at play. Walking away from something in progress is a political act.

At a startup, it’s just another day.

Ruthless triage means looking at what’s in flight, acknowledging that the context has changed, and making the call to stop work on something that no longer serves the highest-value bet, even if the team already put 60% of the effort in. “We need to finish what we started” is a big company instinct. At a startup, sunk cost thinking will kill you.

This is uncomfortable because it means being the person who says “I know we’re halfway through this, and I’m telling you we’re stopping.” It means owning that call, explaining the reasoning, and absorbing the frustration from a team that just lost a week of work. But here’s the thing: shipping something that doesn’t move the needle is just as dangerous as shipping nothing. Velocity theater (i.e. closing tickets that don’t matter) is its own kind of failure. At least when you kill something, you free up capacity for something that might actually work.

Your Framework Means Nothing in the Trenches

MoSCoW. RICE. ICE. Weighted scoring. These frameworks were built for a reason, and in the right context they work. But they were built for teams with the luxury of time, data, and organizational complexity. At a startup, they’re often procrastination with better branding.

Here’s the real test of whether you know how to prioritize: can you defend your decisions in a 10-minute hallway conversation with the founder?

Imagine a conversation where the founder looks you in the eye and says “why are we building this and not that?” If you can’t clearly and succinctly articulate the logic with the bet, evidence, and tradeoff, then your prioritization process is a crutch.

The best startup PMs I’ve worked with don’t lead with frameworks. They lead with judgment. The framework might exist in the background as a sanity check, but the real work is happening in the conversations, the triage calls, and the moments where you have to make a decision with 40% of the information you’d normally want.

Shipping something small and real beats planning something large and theoretical every single time. The startup PM who can’t ship under uncertainty is merely a project manager waiting for conditions that will never arrive.

The Bottom Line

Stability is a tool, not a right. The startup PM’s job is to build a decision-making muscle so fast that direction changes stop being crises and start being inputs.

That means treating your roadmap as a hypothesis. Prioritizing bets over features, acting as a buffer between the founder and the team, and diagnosing whether a direction change is strategic or anxious before you react. And then being able to defend every decision you make in a conversation, under pressure, in real time.

None of this is comfortable or necessarily organized. But the startup PM who can operate this way by holding the ambiguity, processing the signal, and keeping the team shipping, is the most valuable person in the building who doesn’t have “founder” in their title.

If you’re waiting for the chaos to settle before you can do your best work, you’re going to be waiting forever. The chaos is the job. Get good at it.

Good luck out there — and always remember, keep grinding, but make it count.

P.S. If you’re a startup PM struggling to find your footing in this kind of environment, or a founder wondering why your PM keeps trying to “stabilize” instead of ship — book an intro call and let’s talk through it.

And yet, every time I talk to early-stage founders about hiring their first PM, the same pattern shows up: they write a job description that optimizes for someone who’s great at running a system. Not someone who can be the system. That distinction matters more than almost anything else in an early-stage hire, and most people miss it entirely.

This post is for PMs who are considering a startup and want to know what they’re actually walking into. It’s also for founders who are about to make their first product hire and keep reaching for the wrong profile. Either way, the core message is the same: the skills that made you successful at a big company might be the exact things that make you a liability at a startup.

The Skill Inversion

At a big company, your job as a PM is to work the system. There are established processes for discovery, prioritization, planning, and execution. There are stakeholders with defined roles. There’s historical data to ground your decisions. There are templates, rituals, and a shared vocabulary that everyone already speaks. Your value comes from navigating that system well, whether that’s running a tight sprint process, writing a crisp PRD that aligns multiple teams, or managing up to your VP with polished roadmap reviews.

At a startup, none of that exists. You are the system.

Most PMs have never had to operate like this, and the ones who struggle the most are often the ones with the most impressive resumes. They come in and immediately start asking the wrong questions: “What’s the process for submitting a feature request?” “Where’s the research repository?” “Who owns the roadmap?” “Can I see last quarter’s OKRs?”

These are reasonable questions at a company with 500 employees. At a startup with 12 people, they’re a yellow flag. They signal someone who learned how to operate inside a machine, not someone who knows how to build one.

Discovery, roadmapping, and prioritization frameworks were all invented to manage scale and complexity. They’re tools for coordinating large teams with competing priorities. You don’t have a scale problem at a 15-person startup. You have a clarity problem, a speed problem, and a survival problem. Those require different muscles entirely.

Lead Skills vs. Lag Skills

Here’s a framing I keep coming back to: most PM skills are actually lag skills. They help you manage complexity that already exists. You learn to run a design sprint because you have a design team. You learn stakeholder management because you have stakeholders pulling in different directions. You learn roadmap prioritization because you have more ideas than capacity. All of these are responses to existing conditions.

Startups need lead skills, i.e. the ability to create clarity from nothing. Before you can prioritize a roadmap, someone has to figure out whether there should even be a roadmap. Before you can run discovery, someone has to decide what’s worth discovering in the first place. Before you can align stakeholders, someone has to define who the stakeholders are and what they actually care about versus what they say they care about.

The startup PM’s job isn’t to build the right thing. It’s to figure out what “right” even means while also shipping. You will make decisions with 40% of the information you’re used to having. If you need a roadmap to feel confident about your next move, you’re not ready for a startup. Confidence at a startup doesn’t come from having a plan. It comes from trusting your judgment when there is no plan.

Your First 30 Days Are Triage, Not Strategy

I’ve talked to a lot of PMs who join startups and immediately try to implement the playbook they brought from their last company. They set up wiki templates, propose a quarterly planning cadence, build a RICE scoring model for the roadmap, or create a “better” Jira workflow with seven ticket statuses.

None of this is wrong, but it oftentimes is premature. And premature processes at startups have the potential to waste time and create a false sense of order that makes everyone feel productive while the real problems go unaddressed.

Your first 30 days at a startup should be spent on one thing: figuring out which fires are real and which ones the founder invented. I say that with love, because founders are wired to see urgency everywhere. Part of what makes them great at starting companies is the same thing that makes them terrible at prioritizing once the company exists. Everything is existential. Every competitor move is a threat. Every customer complaint is a signal that the product is broken.

Your job in those first 30 days is to be the person who separates signal from noise. Not by building a framework, but by talking to customers, reading the data (whatever exists of it), sitting in every meeting, and developing a gut sense for what actually matters.

The PRD is More Than a Requirements Doc

At a big company, a PRD exists to specify what gets built so that multiple teams can coordinate execution. It’s a contract between product, engineering, design, and whatever other functions need to align. It serves a real structural purpose.

At a startup, the PRD’s primary function is alignment between the PM, the founder, and maybe a few other leads. It’s the document where you hash out what you actually agree on, surface the assumptions you don’t agree on, and create enough shared context that engineering can start building without getting whiplash when the founder changes their mind three days later (which they will).

If you’re writing a startup PRD like you’d write one at Google or Amazon (with detailed requirements, edge cases, success metrics, and a migration plan), you’re over-engineering the artifact and under-investing in the conversation. The document matters far less than the process of writing it together. The PRD is the forcing function for getting aligned, not the evidence that you are aligned.

The Job: Translator in Chief

Big company PMs are optimizers. They take a known product with known users and find ways to make it incrementally better. They run A/B tests, move metrics, and reduce friction in existing flows.

On the flip side, startup PMs are translators. They sit at the intersection of three completely different worldviews and try to create a shared reality:

1. Founder vision: Often bold, directionally correct, and completely disconnected from what can actually ship this quarter. The founder sees the company in five years. The PM has to figure out what that means for this sprint.

2. Customer chaos: Usually a firehose of feedback, feature requests, complaints, and contradictory signals that can either sharpen your product instincts or paralyze you if you don’t know how to filter it. Early customers are not a representative sample. They’re the ones who took a chance on you, and their needs may or may not reflect the broader market you’re trying to serve.

3. Engineering reality: The set of constraints that actually determine what gets built. At a startup, the engineering team is small, the tech debt is accumulating faster than anyone wants to admit, and the gap between what the founder promised investors and what the codebase can support is a daily tension.

The startup PM’s job is to hold all three of these realities simultaneously and produce clarity. This is why I say the startup PM’s real job is creating shared reality, rather than managing a roadmap or running processes. Their job is to create the conditions under which a small team can make fast, high-quality decisions together.

The real question isn’t whether the founder or the PM is in charge. It’s whether the PM can hold the “why” when the founder is unavailable. If the PM can’t independently articulate and defend the product vision, the team loses momentum every time the founder walks out of the room.

What This Means for Hiring

If you’re a founder about to hire your first PM, stop looking for impressive resumes and start looking for people who’ve operated in chaos and produced clarity. The best startup PMs I’ve seen didn’t come from the most prestigious companies, but rather from experiencing chaotic environments, sometimes their own. Those are the ones where the org chart didn’t make sense, where the product strategy changed every quarter, and where the PMs had to figure things out without a playbook.

If you’re a PM considering a startup, here are a few honest questions to ask yourself:

• When you don’t know what to do next, do you reach for a framework or do you reach for a conversation? At a startup, the answer needs to be the conversation. Frameworks are useful when you have enough data and enough people to make them meaningful. When it’s just you and a handful of engineers, the framework is a security blanket.

• Have you ever been wrong publicly and kept going? Not wrong in a retrospective where everyone agrees the team “learned a lot.” Wrong in a way where you made a call, it didn’t work, everyone saw it, and you had to figure out what to do next anyway. Startup PMs who’ve never been wrong publicly aren’t taking enough swings.

• Can you ship without certainty? Can you actually make a decision, commit resources, and move forward when the data says you might be wrong? Because that’s every week at a startup.

As a side note, if you’re looking at PM certifications on a resume and seeing those as strong signals, pump the brakes. Certifications signal someone who learned the vocabulary before doing the work. At a startup, PMs need to be the ones who did the work before they had the vocabulary for it. Less frameworks and more instincts. And instincts only come from reps.

The Bottom Line

The startup PM has no playbook, and that’s the whole point. The value you bring isn’t your ability to follow a process, but rather your ability to create one from nothing, adapt it when it breaks, and throw it away when it stops serving the team.

Most “experienced PMs” are actually experienced at being a PM at a specific company (or size of company). Strip the context, infrastructure, and the team that supported them, and what’s left? That’s the real question. Some people have a decade of experience. Others have one year of experience repeated ten times. The startup will expose which one you are within the first month.

Startups don’t need product managers in the traditional sense. They need people who can think like a PM without needing to be treated like one with no title, team, or process to hide behind. The key is judgment, speed, and the willingness to be the person who creates order from chaos every single day.

If that sounds exhausting, it is. If that sounds exciting, you might be ready.

Good luck out there — and always remember, keep grinding, but make it count.

P.S. If you’re a founder hiring your first PMs and want to get the profile right, I can help advise on how to approach that process. Book an intro call if you want to chat!

But there’s a question I haven’t spent enough time on: how do you actually evaluate whether a role is right for you?

This matters more than ever. The tech industry has shed over 55,000 jobs in just the first few months of 2026. Companies are restructuring around AI, flattening orgs, and doing more with less. The power dynamic has shifted toward employers, and when the market is this tight, the temptation is to take whatever comes your way.

But desperation is how people end up in roles that look great on paper but fall apart in practice. You spend months ramping up, realize the role isn’t what you were told, and you’re back on the market with an awkward stint on your resume.

So let’s talk about how to evaluate a PM role like a PM would evaluate a product opportunity: with clear criteria, sharp questions, and a healthy dose of skepticism.

Read Between the Lines on Job Descriptions

PM job descriptions are starting to look the same and it’s not a coincidence. Companies are using AI to write job descriptions just like candidates are using AI to write resumes. The result is a sea of postings that all say “cross-functional collaboration,” “data-driven decision making,” and “own the roadmap end-to-end.” You could swap the company name on half of them and no one would notice.

This is a problem because the job description is supposed to be your first signal about what the role actually is. When every JD reads like it was generated from the same prompt, that signal disappears.

So what do you do? You go deeper and use AI to your advantage. Take the job description and feed it into Claude or ChatGPT along with the company’s recent earnings calls, blog posts, product updates, press releases, and Glassdoor reviews. Ask it to identify what’s actually unique about this role versus generic PM boilerplate. Ask it to surface what’s not mentioned because the gaps in a job description are often more telling than what’s included.

For lesser-known startups and early-stage companies, this kind of research is even more critical. There’s no brand name doing the work for you. You need to understand what the company actually does, who their customers are, what stage they’re at, and what the company org looks like before you can assess whether the role makes sense for you. Crunchbase, LinkedIn, the company’s own blog, and even their GitHub activity can give you a much richer picture than a JD ever will.

The bottom line: the job description is just a marketing document. Treat it like one.

Scope And Title Are Not the Same Thing

This is one of the most common traps I see PMs fall into, especially in this market. You get offered a “Senior PM” or “Staff PM” title and you think you’ve leveled up. But title without scope is just a word on a badge.

I wrote about title inflation a few weeks ago, and the problem is getting worse, not better. Startups hand out Director and VP titles because they can’t compete on comp. Big Tech companies have so many leveling bands that “Senior” means wildly different things at different orgs. I’ve seen “Principal PM” roles that are basically glorified feature PMs with no team, no budget, and no executive access - just “strategy”.

Here’s what actually matters: What will you own? What decisions will you make? Who will you influence? Those three questions tell you more about a role than the title ever could.

During the interview process, ask the hiring manager to walk you through the actual scope. What product area or surface does this role cover? How many engineers are on the team? Who does this PM report to, and how many layers are between you and the person who can say yes to a meaningful bet? What shipped in the last two quarters, and what’s the biggest open question on the roadmap right now?

If the answers are vague, that’s a signal. Either the role isn’t well-defined yet (which could be an opportunity or a trap, depending on the company), or the hiring manager doesn’t actually know what they need (which is almost always a trap).

Evaluate the Hiring Manager, Not Just the Company

Most candidates spend all their prep time researching the company its products, financials, and culture. That’s important, but they spend almost no time evaluating the person who will be their direct manager, which is arguably the single biggest factor in whether they’ll succeed or fail in the role.

Your hiring manager determines your scope, visibility, air cover, performance reviews, promotion trajectory, and how much of the political nonsense gets filtered before it reaches you. A great manager at a mediocre company is almost always a better bet than a mediocre manager at a great company.

Here’s how to evaluate them during the interview process:

• Pay attention to how they describe the team. Do they talk about specific people and what makes them great? Or do they give you a generic “we have a strong team” line? Managers who know and value their people will tell you about them. Managers who are checked out or self-absorbed won’t.

• Ask them about a product decision they disagreed with. How they answer this tells you everything about their relationship with leadership, their ability to navigate conflict, and whether they have the backbone to protect their team when things get political. If they can’t give you a real example, they either haven’t been tested or they fold every time.

• Ask what success looks like in the first 90 days. If they have a clear, specific answer, that means they’ve thought about what they need and they have a plan for you. If the answer is “just get up to speed and learn the product,” that’s a yellow flag. It might mean they don’t actually know what they need from this hire, which means you’ll be figuring it out on your own with no guardrails.

• Ask them what they wish they could change about how product works at the company. This is a great question because it forces honesty. Every org has dysfunction, but the ones worth joining are the ones where the leaders see it clearly and are actively working on it. If they tell you everything is great, they’re either lying or they’re not paying attention. Neither is a good sign.

Look For Signals On Team Health & Culture

The interview process gives you a window into how a team actually operates, even when no one is explicitly telling you. You just have to know what to look for.

How many people interview you, and how aligned are they? If you talk to four people and get four different descriptions of what the role is, that’s a team that hasn’t aligned on what they need. Pay attention to whether your interviewers are telling a coherent story or contradicting each other.

How do they talk about the PM who was in this role before? Is the role new, or is it backfilling someone who left? If it’s a backfill, ask why the person left. They might not tell you, but their body language and tone when you ask will tell you plenty. If the role has turned over multiple times in a short period, that’s a flashing red signal.

What’s the engineering-to-PM ratio? This one is underrated. A team with 20 engineers and one PM is fundamentally different from a team with 6 engineers and one PM. Both can work, but they require different skills, operating rhythms, and levels of autonomy. Make sure you know what you’re walking into.

What does the org chart look like, and has it changed recently? Frequent reorgs are one of the strongest predictors of a dysfunctional product org. If the team has been reorganized three or four times in the last year, that’s not “moving fast.” That’s leadership that can’t commit to a strategy. And the people who pay the price for constant reorgs are the PMs, because scope and ownership get reshuffled every time.

Watch Out For Red Flags In The Interviews Process

With over a decade working between big tech and startups, I’ve learned that the interview process tells you just as much about the company as the company’s answers do. The process is the product.

Below are some red flags to watch our for along the way:

1. The process drags on with no clear timeline. If a company takes three weeks between rounds, reschedules multiple times, or can’t give you a straight answer on when they’ll make a decision, that’s how they operate internally too. Slow hiring processes usually reflect slow decision-making cultures. You’ll feel that every day on the job.

2. They can’t articulate what “great” looks like. If you ask what separates a good PM from a great PM at this company and the answer is vague platitudes about “ownership” and “impact,” they haven’t thought deeply about what they value. That means your performance reviews will be a coin flip, and your promotion case will depend more on politics than output.

3. They skip the reverse sell. In a good interview process, there’s a moment where the company stops evaluating you and starts selling you on why this is a great place to work. If that never happens or if the entire process feels like a one-way interrogation, that tells you something about how they view the power dynamic. Companies that don’t bother selling the role to strong candidates usually don’t bother investing in their PMs once they’re hired, either.

4. The comp conversation is evasive. If a company won’t share the range early in the process, there’s usually a reason. In most cases, it’s because the range is below market and they’re hoping you’ll get emotionally invested in the role before you find out. Respect your time. Get the total comp range up front.

The Job Security Question Nobody Asks

Here’s the question most candidates are afraid to ask: How protected is this role?

In a tough tech market where lay offs are continuing to worsen and where AI is explicitly being cited as the reason for headcount cuts, this is an essential question.

You need to understand where this role sits in the company’s priority stack. Is this product vertical growing or in maintenance mode? Is the team being invested in or being “optimized”? Is the PM function seen as critical by the CEO and executive team, or is it viewed as overhead that could be compressed?

Some ways to get at this:

• Ask about the company’s last round of layoffs. If they’ve done layoffs recently, ask how the product org was affected. Were PMs cut? Were entire product teams eliminated? How did leadership decide what to keep and what to cut? Their answer will tell you how safe this specific role is.

• Ask what would happen if the company needed to cut 10% of headcount tomorrow. This is a pointed question, and you might not get a direct answer. But the reaction itself is useful. A confident hiring manager will tell you that this team is core to the business and well-protected. A nervous one will dodge the question.

• Look at the company’s spending patterns. If they just raised a big round but are hiring cautiously, that’s actually a good sign and it means they’re being disciplined. If they raised a round two years ago and are still burning through it with no clear path to profitability, your job security is only as good as their runway.

The goal isn’t to find a role that’s guaranteed safe, but rather to make sure you’re not walking into a role that’s already on the chopping block.

The First 90 Days Smell Test

Here’s the final filter I’d apply to any PM role: can you clearly envision what you’d be doing in the first 90 days?

If you finish the interview process and you can’t answer this question with specificity, something is wrong. Either the company hasn’t defined the role well enough, or the problems they’re solving aren’t clear enough for you to hit the ground running.

A well-defined PM role should give you enough signal to sketch out a rough plan: the product area you’d own, the stakeholders you’d need to build relationships with, the first problem you’d dig into, and how you’d establish credibility with the engineering team. You should be able to picture your first few weeks because the role and mandate are clear enough.

If you can’t picture it, ask yourself why. Is it because the role is genuinely ambiguous and you’d be defining it from scratch? That can be exciting at the right company, such as an early-stage startup where you’re the first or second PM and you have a founder who’s ready to let you run. But at a larger company, ambiguity in the role usually means you’ll spend your first six months just figuring out what you’re supposed to be doing while the org swirls around you.

The 90-day smell test is a simple heuristic, but it catches a lot of bad roles before you accept them.

The Bottom Line

The PM job market in 2026 is brutal. Companies have the leverage, hiring processes are longer, and the bar is higher than it’s been in years.

But “the market is tough” is not a reason to take a bad role. In fact, it’s a reason to be more selective, not less. A bad role in a tough market is worse than no role, because it burns six months of your career, puts another short stint on your resume, and puts you back on the market in an even weaker position.

Do the work. Research the company beyond the JD. Evaluate the hiring manager like they’re evaluating you. Read the team health signals. Watch for red flags in the process. Ask the hard questions about job security. And run the 90-day smell test before you sign anything.

The best PMs I know treat their own career decisions with the same rigor they bring to product decisions. They define success criteria, gather signal, stress-test assumptions, and don’t let urgency override judgment.

Do the same, and you’ll find the right role, not just any role.

Good luck out there — and always remember, keep grinding, but make it count.

If you’re a PM looking to evaluate your next move and want a thought partner in the process, I can work with you 1:1 on positioning, interviewing, and making the right decision.

If you’re an early-stage founder looking to hire, I can help advise on how to structure your first PM role and attract the right candidates.

Book an intro call if you want to chat!

But if the old playbook doesn’t work anymore, then what does?

That’s what this post is about: How PMs should be demonstrating their work to the market in 2026, and why the traditional resume + LinkedIn + behavioral stories trifecta is no longer enough to separate you from the pack.

The Resume Is Now Table Stakes

Let me be clear: I’m not saying your resume doesn’t matter. It does. But having a great resume in 2026 is like having a great GPA and test scores when applying to college - it gets you into the consideration set, but it’s not what gets you the offer.

Think about how college admissions shifted over the last couple of decades. There was a time when a 4.0 GPA and a strong SAT score was your ticket. Then schools moved to holistic admissions with essays, extracurriculars, demonstrated passion, leadership, and the full picture of who you are as a person. The numbers got you in the door, but the differentiator was everything else.

The PM job market has gone through the same shift, and it’s been accelerated by AI. Every PM now has access to tools that can polish a resume to near-perfection. ChatGPT can rewrite your bullet points with quantified impact in seconds. There are a dozen AI-powered resume optimizers that will tailor your resume to a specific job description and score it against ATS filters. The floor has been raised. Everyone’s resume looks good now (or at least it should).

So when a hiring manager has a stack of 200 resumes for a Senior PM role and 180 of them are well-formatted, keyword-optimized, and packed with “increased revenue by X%” bullet points, then what actually separates one candidate from another?

The differentiation happens everywhere else.

Your LinkedIn Is Your Living Source of Truth

If your resume is a snapshot in time, your LinkedIn profile is a living document. And in 2026, it’s likely the first thing that gets looked at, whether that’s before your resume, cover letter, or application.

Recruiters look at it. Hiring managers look at it. Your future peers look at it. People you’re networking with look at it. Everyone stalks everyone’s LinkedIn so let’s just be honest about that.

And yet, it’s staggering how many PMs have a LinkedIn profile that reads like either a graveyard of outdated experiences on one side of the spectrum or a copy-paste of their resume on the other side of the spectrum. Whether it’s a boring headline that says “Product Manager at [Company]”, a summary that’s either empty or reads like a generic job description, or experience entries that list typical PM responsibilities instead of outcomes.

Your LinkedIn needs to be proof of your personal brand and your accomplishments. It doesn’t need to be over-the-top. I’m not even asking you to become an influencer or write daily hot takes. But it needs to reflect what you’ve actually done, how you think, and ideally a bit of who you are as a person.

A few things that matter on your profile:

• Your headline should signal your positioning, not just your current title. If you’re a PM who specializes in marketplace products, say that. If you’ve worked at multiple companies, mention them. If you’ve built something, call that out. The headline is prime real estate, so don’t waste it on something generic.

• Your experience section should read like a narrative, not a job description. Every role should answer: what did you own, what did you ship, and what happened because of it? Hiring managers skim this in seconds. Make those seconds count.

• Your personality should shine. The best LinkedIn profiles I’ve seen from PMs don’t just list what they did but rather give you a sense of how they think and what drives them. That’s what makes someone memorable. And bonus points if you’re posting content that reflects your thinking.

The bottom line is that LinkedIn is a living, breathing source of truth. Your resume is static. Recruiters are going to your LinkedIn before they ever open your PDF. Treat it accordingly.

Build a Portfolio of Proof

In my post on the 360 PM, I talked about the shift from PMs who coordinate to PMs who create. That shift is equally important for your work day-to-day as it is about how you present yourself to the market.

The old way to demonstrate PM capability was behavioral stories. “Tell me about a time you influenced without authority” or “Walk me through a product you launched”. You’d prepare your STAR-format answers, rehearse them, and hope the interviewer liked your narrative. And to be clear, you still need to be good at this. Interviews still test for it and strong storytelling is still a core skill.

But behavioral stories are self-reported. They’re your version of events, filtered through your memory and polished for the interview. They tell the interviewer what you say you can do. They don’t show what you can do.

What stands out in 2026 is proof of work. Tangible artifacts that demonstrate you can build, think, and ship.

Here’s what building a portfolio of proof looks like in practice:

1. Build side projects that demonstrate your instincts. I don’t mean building the next startup. I mean using AI tools like Cursor, Lovable, Replit, or Bolt to spin up something real. A tool that solves a problem you care about. A prototype for a product idea you’ve been kicking around. A personal website that you built yourself rather than paying someone else to do it. Having these projects shows that you’re a PM who gets their hands dirty and builds, rather than one who waits for someone else to make their ideas tangible.

2. Write as proof of thinking. Consider writing about your work, whether that’s in a newsletter on Substack, an article on Meidum, or periodic posts on LinkedIn. These help demonstrate how you think. When a hiring manager reads a well-written perspective you published, they’re getting a window into your product framework, your ability to communicate clearly, and your taste in product. That’s more signal than a bullet point on a resume will ever provide. Writing is the most underrated career accelerator for PMs, and it’s one of the easiest to start.

3. Create case studies from your actual work. Take a product you shipped and write it up as a proper case study - the problem, your approach, the decisions you made, the trade-offs, the outcome, and what you’d do differently. You can abstract the confidential details and still show your thinking. A well-crafted case study can give a hiring manager more signal about your capabilities than a 45-minute behavioral interview because it shows the full arc of your decision-making, not just the highlight reel.

4. Prototype ideas during your interview process. This one is aggressive, but it works. If a company gives you a product sense or strategy challenge, don’t just present a slide deck. Build a rough prototype of your proposed solution and walk them through it. I’ve seen PMs do this and it completely reframes the conversation from “a candidate pitching an idea” to “a builder showing their work.” It signals initiative, technical fluency, and the kind of builder instinct that companies are actively looking for.

Stop Reading About AI and Start Using It

Every PM I talk to knows AI is important. They’ve read the thought pieces. They’ve seen the LinkedIn posts about Cursor and Claude and whatever the latest tool is. They know they should be building with AI.

But knowing and doing are different things, and the gap between them is where most PMs are right now.

There’s no shame in using AI tools to build your portfolio of proof. In fact, it’s the whole point. The PM who builds a prototype in a weekend using Cursor isn’t “cheating”, but instead demonstrating exactly the kind of resourcefulness and adaptability that companies want. They’re showing they can get from idea to artifact without waiting for an engineering sprint. That’s the 360 PM in action.

But using AI also goes beyond prototyping. Start using it to build workflows that improve your efficiency and ways of working. Use it to synthesize research. Use it to draft and iterate on your writing faster. Use it to analyze data. The PMs who are most effective with AI are going beyond using it as a search engine. They’re using it as a thinking partner and a building tool.

And finally, talk about it as much as you can. Share what you built. Share what you learned. Share what surprised you. When you show the market that you’re actively building with AI, you’re sending a signal that you’re adaptable, current, and willing to evolve your craft. In a market where companies are explicitly looking for PMs who can “flex across” functions and reduce handoffs, that signal matters enormously.

You have to show you are more than a great doc writer, deck builder, or technical project manager. Those skills are necessary but they’re not sufficient anymore. The PMs who are building a bench of projects (things they’ve shipped, prototyped, written about, and can speak to with depth) are the ones who stand out in a sea of polished resumes and rehearsed behavioral answers.

The Bottom Line

Your resume gets you in the door, your LinkedIn is your living source of truth, and your portfolio of proof (side projects, writing, case studies, prototypes) is what separates you from every other qualified PM in the pipeline.

The PM job market in 2026 is holistic, just like college admissions became holistic. The numbers (your resume, your title, your years of experience) still matter, but the full picture of who you are as a builder, thinker, and operator is what gets you the offer.

Start building. Start writing. Start showing your work. The tools have never been more accessible, the bar for getting started has never been lower, and the market is rewarding those who go beyond the traditional path.

Good luck out there — and always remember, keep grinding, but make it count.

If you’re a PM looking to build your portfolio and stand out in this market, I can work with you 1:1 on positioning, interviewing, and building the proof that gets you noticed.

If you’re an early-stage founder looking to hire, I can help advise on how to hire PMs and put the product foundations in place to grow.

Book an intro call if you want to chat!

The PM title landscape has shifted dramatically and the titling system is officially broken. Not because titles don’t matter (they do), but because companies, candidates, and the industry at large are using them incorrectly, inflating them when it’s convenient, and ignoring the structural shifts that AI and leaner orgs are forcing on all of us.

Let me break down what I’m actually seeing, where the market is headed, and what I think needs to change.

Stop Calling Your First PM Hire “Head of Product”

This one drives me crazy, and I see it constantly at early-stage startups.

Let’s set the scene: A founder raises a Seed or Series A round. They’ve been the de facto product person since day one. The business is growing, and they finally realize they need someone to take the day-to-day product work off their plate. So they post a job listing for “Head of Product.”

The problem? They don’t need a Head of Product. They need a Founding PM.

These are fundamentally different roles with fundamentally different profiles, and conflating them is one of the most common hiring mistakes I see founders make.

A Head of Product implies you’re optimizing for a product leader. Someone who sets the strategic direction, builds and manages a PM team, and operates at a high altitude. That role makes sense when you already have at least 1-2 PMs in place and you need someone to lead the function. It’s a leadership hire, not a builder hire.

A Founding PM is the person you hire when the PM function doesn’t exist yet. They’re the one who’s going to grind. They’re writing PRDs, talking to customers, doing QA, sitting in every standup, and probably helping with support tickets on the side. The profile you’re looking for is a mid-level or senior PM who is hungry to build, has enough experience to bring structure to chaos, but not so senior that they think their job is to set a vision and delegate.

When you call that role “Head of Product”, you attract the wrong candidates. You get people who expect to manage, not execute. You get people who want to set strategy from a distance instead of getting their hands dirty with the product every single day. And worse, you set inflated expectations on both sides that create tension the moment the founder (rightfully) stays deeply involved in product decisions.

If the person is your first PM, call it what it is - Founding PM / First PM / IC PM. Just don’t inflate the title to make the listing more attractive. You’ll end up with someone who thinks they’re a VP and acts like one, when what you actually need is someone who ships and rolls up their sleeves to wear multiple hats.

The Middle Management Layer Is Dying And It Should

Here’s my spiciest take: most PM middle management roles (PM Manager, Senior PM Manager, Group PM, Lead PM with directs) should not exist in 2026. They’ve already started to dwindle away, and within a few years, they’ll be at a minimum.

A huge chunk of these roles were created during the peak bloat years of tech. Companies were flush with capital, headcount was cheap, and the default response to growth was to add organizational layers. If a Senior PM wanted a promotion but there was no clear next role, the company would create a “Manager” track and give them a couple of direct reports. Problem solved, but only on paper.

But what actually happened? You created a layer of management where the person above them (a Director or VP) is still making the real strategic decisions, and the people below them (the ICs) are still doing the actual product work. The middle manager’s entire job became split between managing up and managing down. No IC work. No direct product impact. Just process, alignment, and career ladder maintenance.

And now, in the age of AI, this layer is getting squeezed from both sides. AI tools are making ICs dramatically more productive. A single strong PM can now do the research, synthesis, documentation, and prototyping that used to require a small team. Meanwhile, companies are flattening their org structures at a rapid pace. Middle managers made up a third of all layoffs in 2023. Gartner estimates that by 2026, one in five organizations will use AI to eliminate over half of their middle management positions.

This is a structural shift, and it’s the right move. The best PM orgs I’ve seen in 2026 are lean. Fewer layers. More experienced ICs operating with autonomy. Directors and VPs setting strategic direction, and Principal or Staff PMs executing at a high level directly beneath them, with no middle manager in between acting as a pass-through.

If you’re a PM Manager or Group PM reading this and feeling uncomfortable, I get it and I’ve been there myself. But the career path isn’t dead. It’s just different now. The path forward isn’t more management layers, but rather exceptional ICs who can operate at a Principal or Staff level, or can make the leap into a Director role where they’re actually setting strategy and making decisions, not relaying them.

Senior PM Is Both the Hottest Title and the Most Diluted in the Market

If I had to pick the single most common PM title in open job listings right now, it’s “Senior PM.” And if I had to pick the single most inconsistently defined PM title right now, it’s the same answer.

Senior PM has become the default hiring level for most companies lately. The logic seems straightforward: companies claim they don’t want to invest in training junior talent (more on that in a minute), and they want someone who can come in and execute immediately without a lot of hand-holding. A Senior PM with 4 to 6 years of high-volume, high-impact shipping experience is exactly what most hiring managers think they need.

And in many cases, they’re right. Senior PMs are in the sweet spot - experienced enough to operate with real autonomy, but still close enough to the work that they’re building product every day rather than spending their time in alignment meetings.

The problem is that the definition of “Senior” has become almost meaninglessly broad. I’ve seen Senior PM roles that require 3 years of experience and Senior PM roles that require 10. I’ve seen Senior PMs at one company doing work that would be considered Associate-level at another. Title inflation during the 2020-2022 boom meant that a lot of people carry “Senior” on their resume who got the title after 18 months in a hot market, not because they’ve actually operated at a senior level.

For hiring managers and founders, this means you need to look well beyond the title on the resume. What matters is whether the candidate has a track record of executing on a clearly scoped product area with real outcomes. Shipping features, moving metrics, and working cross-functionally at high velocity are all important aspects to look for in interviews. The title “Senior PM” tells you very little about whether they can actually do these things.

For PMs carrying the Senior title, the game right now isn’t about defending the title, but rather having the narrative to back it up. How you got to Senior and what you actually shipped at that level matters far more than the word itself.

The Future Belongs to Veteran ICs

If middle management is shrinking and Senior PM is getting diluted, where does the PM career path actually go?

To veteran IC roles - Principal PM, Staff PM, Senior Staff PM, or whatever your company calls the experienced IC track. This is where the future of product management lives.

These roles are designed for PMs with 6 to 8+ years of deep, battle-tested experience. PMs who have owned large-scope, high-impact, strategically complex product areas. PMs who can toggle between strategy and execution in the same week. PMs who don’t need a manager to tell them what to do and they also don’t want one.

This is the archetype I’ve been calling “the 360 PM” - one who can create, not just coordinate. Someone who can prototype, research, synthesize, ship, and lead through influence rather than authority. With AI tools in 2026, a strong Principal or Staff PM can cover a surface area that would have required a PM, a researcher, and an analyst three years ago.

Companies are catching on. More and more orgs are opening IC tracks that go all the way up, with compensation that matches or exceeds the management track. This is the right bet. Instead of building out middle layers of PM managers, companies should invest in fewer, stronger, more autonomous ICs who can drive outsized impact with a smaller footprint.

If you’re a PM in the 4 to 6 year range and you’re thinking about your next move, my strong advice is to start thinking about what it takes to get to Staff or Principal level. Not in terms of title, but in terms of capability. What does it look like to own a product area end-to-end? To mentor other PMs without managing them? To make strategic bets and execute on them directly? That’s the muscle you need to build.

We’re Abandoning the Next Generation And It’s Going to Cost Us

With all of this change, here’s my main worry: Companies have largely stopped investing in entry-level and junior PM talent. The hiring market in 2026 is almost entirely oriented toward Senior PM and above. When I look at open roles, the majority want 4+ years of experience minimum. Many companies won’t even consider candidates with less.

I understand the logic. In a world where companies are doing more with less, the instinct is to hire people who can hit the ground running. Why invest in growing a junior PM when you can hire a Senior PM who’s already proven?

Well, if the entire industry refuses to invest in junior talent, where do the next generation of Senior and Principal PMs come from? You can’t have a pipeline of experienced PMs in 5 years if you refuse to grow anyone today. The math simply doesn’t work, and companies are mortgaging the future to optimize the present.

This generation of early-career talent might be the most valuable cohort to invest in. They went through college with AI. They’ve been building with these tools since day one. Their appetite to use the latest technology is the highest of any experience band, not because it’s trendy but because it’s all they’ve ever known. They’re less likely to be bogged down by legacy process thinking, less focused on organizational politics, and more focused on learning and building.

The companies that are getting this right are running structured APM/RPM programs that bring in smart, driven builders right out of school. These programs pair junior talent with senior mentors, rotate them through product areas, and produce PMs who are ready to operate independently within 12 to 18 months. The ROI was real 10 years ago and it is still real today.

If you’re a company that has product market fit and you’re not running some version of an APM or junior PM development program, you’re making a short-sighted mistake. Find the young builders who’ve shipped side projects with AI, who can show they’re a jack of all trades, who are hungry to learn the craft. Invest in them. They’re your future Principal PMs.

The Bottom Line

If there’s one thread running through everything I’ve laid out, it’s that titles in 2026 are a lagging indicator. They tell you where someone has been (albeit not always accurately) and they tell you very little about what they can actually do.

The PM who thrives right now isn’t defined by whether their LinkedIn says “Senior” or “Staff” or “Head of Product.” They’re defined by their ability to build, ship, and create real outcomes in a world where the tools are better, the teams are smaller, and the expectations are higher than they’ve ever been.

For companies: Be intentional about how you title PM roles. Don’t inflate titles to attract candidates. Don’t create management layers you don’t need. Invest in the IC track. And for the love of product, invest in the next generation before it’s too late.

For PMs: Stop optimizing for title. Optimize for capability. The market will figure out the rest.

Good luck out there — and always remember, keep grinding, but make it count.

P.S. If you’re a PM navigating the title question as part of your job search or if you’re a founder thinking about how to set up your product team, let’s chat.

I also host a podcast where I interview experienced PMs and early-stage founders about growth, setbacks, and successes in their product journeys. Check out an episode, and subscribe directly for more videos every two weeks.