Lenny's Podcast in 3 minutes

Here is The Daily FM summary of the Lenny's Podcast: Product | Career | Growth that aired on Sunday August 9th. Lenny spoke with Adam Ward, Cursor’s head of talent and a veteran recruiting leader who previously helped scale teams at Facebook and Pinterest, about how to build unusually high-talent-density companies in an AI-era hiring market he rates “an 11” out of 10 for competitiveness. [1]

Ward described today’s market as a tale of two cities. Elite AI researchers and certain technical builders can receive extraordinary, even NBA-sized offers, while many other qualified people are struggling to find work. He sees this as a broader reset in how labor gets done: AI is raising demand for people with broad judgment, technical fluency, and the ability to work across functions.

One fast-rising role is the forward-deployed engineer: someone technical enough to understand and deploy sophisticated products, but also able to sit with executives and customers, explain tradeoffs, and solve real implementation problems. Ward thinks this may be a natural next step for full-stack engineers. At the same time, narrow specialization is becoming less valuable. Companies increasingly want engineers with product sense, designers who can build, and individual contributors with taste, curiosity, and systems thinking. [2]

The heart of the conversation was Ward’s critique of conventional recruiting, which he calls the “funnel of doom.” Most companies contact a hundred people, hear back from twenty, filter them through interviews, and hire whoever remains. But, he argued, those twenty respondents are not necessarily the best twenty people—they are simply the people who happened to respond. This leads to “remainder hiring,” where companies select from an already suboptimal pool. [3]

His alternative is to treat every critical hire more like an executive search. First, define precisely what excellence means for the specific role: not just resume logos, but the abilities that matter, such as collaborating with designers, translating frameworks into products, or breaking large problems into manageable pieces. Second, map the small group of people—perhaps fifty worldwide—who might truly be exceptional fits. Ask trusted contacts highly specific questions rather than vague ones like, “Who’s the best product engineer?” Then relentlessly and personally pursue those people over weeks, months, or even years. [4]

At Cursor, recruiting is a company-wide sport. Employees actively post impressive people, products, and online posts in a “Hiring Ideas” Slack channel, then rally around how to reach them. Ward emphasized that “caring is free”: candidates remember whether a company made them feel wanted and understood. The hiring manager’s first conversation is especially important, and the process should be tailored to the individual rather than treated as a standardized funnel.

Cursor also relies heavily on work trials and collaborative projects, because real work samples provide stronger evidence than interview conversations alone. The company briefly tried removing them, Ward said, but its confidence in hiring decisions dropped sharply. The trial is designed to be flexible and role-specific, whether it involves engineering, product, or a customer challenge for go-to-market candidates.

A surprising takeaway was that the offer is not the end of recruiting. Ward said closing begins from the first conversation, by understanding someone’s motivations and making every interaction reinforce them. Even after an offer is accepted, Cursor continues “preboarding” with dinners, community, and sometimes a company laptop, because candidates can still renege in this unusually competitive market.

For early-stage founders, Ward warned against expecting one first talent hire to both urgently fill roles and build the entire recruiting system. Those are competing jobs. His broader message: if talent really is a company’s top priority, leaders must personally invest the time, care, and accountability that claim requires. Thank you for listening to Lenny's Podcast in 3 minutes from The Daily FM. See you next time!

Here is The Daily FM summary of the Lenny's Podcast: Product | Career | Growth that aired on Sunday August 2nd. Lenny spoke with Tom Verrilli, Chief Product Officer at Whatnot, former CPO at Twitch, and former product leader at Twitter, in a wide-ranging conversation about why one of the most senior product executives in tech thinks companies should hire far fewer product managers. [1]

Tom’s most provocative line was that Whatnot’s product team was built around the idea, “we regret that product management exists.” He did not mean PMs are useless. His point was that product management should not be treated as an automatic headcount ratio, where every six engineers get a designer, an engineering manager, and a PM. In his view, that model has often “infantilized” engineers and designers by keeping them away from customer context, tradeoff decisions, and product judgment. PM skill is a muscle, he argued, and if only PMs exercise it, everyone else’s product muscles atrophy. [2]

At Whatnot, that philosophy shows up in a very lean team: a little over 20 PMs supporting a fast-growing live shopping marketplace. Rather than permanently attaching PMs to every engineering team, Whatnot maps them to important problems. Every six months, senior leaders define what must be true for the business, choose the most important projects, and assign clear owners. Sometimes that owner is a PM, but sometimes it is an engineer or designer. Everyone is expected to bring product thinking, go through product review, and do the work of understanding users and tradeoffs. [3]

Tom was especially blunt about hiring. He said more than 31,000 people applied for PM roles at Whatnot over two years, and they hired one. The candidates who trend down are those who mostly talk about stakeholder management, alignment, and politics. Whatnot looks for people who can think at both the macro and micro level: understand the system, define the end state, and then show impatience about validating it quickly. Tom argued that many PMs at large companies have been rewarded for “product theater” rather than building, deciding, and learning. [4]

A big theme was the return of senior product leaders to individual contributor work. Tom said tech made a mistake by promoting its best PMs into director roles where they stopped actually doing product work. At Whatnot, even managers spend most of their time as ICs, and Tom says he still spends about half his time directly in the work: reading support tickets, pulling data, querying the codebase, writing specs, and sitting with engineering and design. His analogy was simple: if you have Messi, you want him on the field. [5]

AI, he said, makes this model much easier. PMs can now explore codebases, estimate scope, pull nuanced data, and spot regressions without constantly interrupting engineers or waiting on data scientists. But he cautioned that AI does not remove responsibility; bad analysis and bad code are still your problem. The leverage goes to people with strong judgment.

Tom also shared several operating lessons. One was “know, then go”: think through risks and scale effects, but do not let vague concerns from legal, finance, or other teams freeze progress. Another was “play the accordion”: zoom out to understand the bigger system and long-term implications, then zoom back in and ship the next concrete version. He used Whatnot’s marketplace listings as an example, where a local seller convenience can create major consequences for search, discovery, and buyer growth.

The most surprising moment may have been Tom’s example of Whatnot’s live commerce magic: he recently bought a fresh California spiny lobster from a seller livestreaming seafood coming off the boats in San Diego, shipped overnight to his door. For him, that captured why agentic commerce will not replace everything. Sometimes shopping is not about high-intent efficiency; it is social, serendipitous, and human.

The episode ended with Tom reflecting on Twitter, where he learned that true product-market fit can survive enormous organizational chaos, but weak leadership can delay obvious decisions for years. His broader takeaway was humble: Whatnot’s model may not work everywhere, but in the AI era, PMs should get back to the roots of the craft—understanding customers, understanding the business, understanding the technology, and helping teams make better decisions faster. Thank you for listening to Lenny's Podcast in 3 minutes from The Daily FM. See you next time!

Here is The Daily FM summary of the Lenny's Podcast: Product | Career | Growth that aired on Sunday July 26th. Lenny spoke with Dianne Penn, Anthropic’s head of product for AI Research and Labs, and the company’s first technical product manager, about what it has been like to help build Claude from the early days through today’s coding and agentic breakthroughs. [1]

Dianne said Anthropic’s early advantage was not obvious from the outside. When she joined in 2023, there were only about five product engineers, one engineer on the API business, and no clear identity yet beyond “another chatbot.” But internally, she said, the culture was already strong: mission-driven, bottom-up, fast, and deeply tied to research. One surprisingly charming example was “Golden Gate Claude,” a 24-hour experiment where Anthropic turned up an interpretability feature related to the Golden Gate Bridge, causing Claude to mention it obsessively in every answer. Dianne said only a small number of people saw it, but internally it proved Anthropic could turn research into playful product experiences quickly. [2]

A major theme was how Claude became associated with coding. Dianne said that in 2023, nobody put Anthropic, Claude, and coding in the same sentence. But she noticed people were starting to use models not just for autocomplete, but for writing long-form code. Training Opus 3 with that in mind became an early inflection point. Later, Opus 4.5 and Claude Code created an even bigger moment: Dianne argued that frontier models need frontier products for users to really feel their magic, and Claude Code gave the model a vehicle. [3]

They spent a lot of time on how product management is changing in AI. Dianne’s sharpest line was that “evals are the new PRDs.” She does not mean PRDs are dead, but for model work, the key product artifact is often a precise evaluation that captures a user pain point. If someone says Claude hallucinated or failed at instructions, the PM’s job is to dig into transcripts, understand what actually failed, and turn that into a measurable eval researchers can improve against. Her phrase was that PMs now need to “sweat the tokens as much as the pixels.” [4]

Lenny also brought up Gary Tan’s idea of “token maxing”: if you spend heavily on AI now, you can live like someone in 2028. Dianne reframed that as experimentation. The best people at Anthropic, she said, spend a lot of time with new models, but they also experiment in public internally, sharing discoveries so others can build on them. [5]

On Anthropic Labs, Dianne described a small, founder-like group chasing discontinuous bets such as Claude Code, MCP, Skills, and Claude Design. The trick is being strongly opinionated about the area, but flexible about the exact prototype.

The most practical career takeaway was that managers and senior PMs cannot stay abstract. Dianne said anyone leading AI product teams has to use the models hands-on, ship with them, read user feedback, and enjoy the technology. First-principles thinking, curiosity, low ego, ambition, and deep user empathy matter more than pattern-matching from old SaaS or consumer playbooks.

Near the end, Dianne reflected on burnout, parenting, and the human role in an AI future. Her view was that judgment, persistence, inner voice, and curiosity will remain crucial. And inside Anthropic, staying sane depends on team trust: people backing each other up, entering what they call the “hive mind,” and treating this intense work as a team sport rather than an individual burden. Thank you for listening to Lenny's Podcast in 3 minutes from The Daily FM. See you next time!

Here is The Daily FM summary of the Lenny's Podcast: Product | Career | Growth that aired on Sunday July 19th. Lenny spoke with Elizabeth Stone, Netflix’s Chief Product and Technology Officer, about how AI is changing product work, engineering, hiring, company culture, and entertainment itself. [1]

A central theme was that AI is blurring job boundaries. Lenny framed the moment as one where PMs can ship code, designers can write PRDs, and engineers can do more product thinking, leaving many people wondering, “What is my job anymore?” Elizabeth said Netflix is definitely seeing that confusion, but she views it as a normal “storming” phase that comes with transformative technology. Her take was not to put AI “back in the box,” but to add better guardrails: clear source-of-truth data, testing standards, production controls, and, most importantly, human accountability. AI can help create prototypes, code, and analyses, but people still own the outcomes. [2]

Elizabeth argued that AI lets PMs, designers, and data scientists move much farther before engineering has to step in, especially for prototyping and hypothesis testing. But she pushed back on the idea that functions will disappear. She said great engineering, great data science, and great creativity are still scarce. The job boundaries may blur, but craft excellence still matters. [3]

One of the biggest takeaways was Netflix’s growing emphasis on “systems thinkers.” Elizabeth said AI makes local, one-off solutions more risky and less efficient. As agents and tools operate across many systems, companies need common infrastructure, design systems, reliable data definitions, and paved paths that help everyone move faster without creating chaos. Her practical advice for building systems thinking was simple: whatever problem you are solving, zoom out one level. Ask what broader customer, business, or platform problem it connects to, and whether your solution will scale or help others. [4]

They also discussed how Netflix’s famous culture has aged into the AI era. Lenny noted that traits from Netflix’s old culture deck—high agency, autonomy, talent density, fast experimentation, and top-of-market pay—sound a lot like how today’s top AI labs operate. Elizabeth described Netflix culture as “excellence as an operating system.” The key ingredients, in her view, are exceptional talent, trust, risk-taking, accountability, and resisting the big-company instinct to solve every problem with more process. One notable moment was her point that when failures happen, Netflix tries to rely on blameless retros and learning rather than adding layers of bureaucracy. [5]

They revisited the “Keeper Test,” Netflix’s practice of asking whether you would fight to keep someone if they said they were leaving. Elizabeth emphasized that it is not only a tool for letting people go; it is also a way to give strong positive feedback to people doing extraordinary work.

On hiring, Elizabeth said Netflix still needs junior talent, despite AI making some tasks easier. Younger employees bring AI fluency, openness to new tools, and fresh instincts about entertainment. But Netflix still has to teach craft, judgment, and responsibility.

Finally, they explored AI in entertainment. Elizabeth said Netflix already uses AI and machine learning in personalization, localization, production tools, subtitles, dubs, promotional assets, and creative workflows. But she was skeptical of entertainment with no humans at the center. AI may expand what creators can do, but storytelling, she argued, remains deeply human.

The episode closed with lighter notes: Elizabeth recommended Into Thin Air and Liar’s Poker, praised Eight Sleep, shared two life mottos from her parents, and talked about preparing to ride alongside part of the Tour de France route. Thank you for listening to Lenny's Podcast in 3 minutes from The Daily FM. See you next time!