Stanford Online

Stanford CS153 Frontier Systems | Nikhyl Singhal from Skip on Product Management in the AI Era

For more information about Stanford's online Artificial Intelligence programs, visit: https://stanford.io/ai Follow along with the course schedule and syllabus, visit: https://cs153.stanford.edu/ In a CS153 guest lecture, Professor Mike Abbott shifts from technical topics to product, tracing how software moved from PRD-driven project management to founder-led consumer product building, and arguing AI is blurring the boundaries between design, engineering, and product. Nikhyl Singhal shares his background founding companies and leading product at Google, Meta, and Credit Karma, then explains four company phases—finding product-market fit, post-fit process and coordination, hypergrowth scale-and-expand, and late-stage reinvention—each requiring different product skills. He reflects on Google Hangouts as a lesson in solving real customer problems and iterating quickly. Singhal describes The Skip, a curated community and coaching effort focused on careers, and discusses AI’s impact: less value in information-moving PM work, more demand and pay for hands-on product builders with judgment, flatter orgs, anxiety from layoffs, and heightened risk for non-technical middle managers. Guest Speaker: Nikhyl Singhal is the founder of Skip (a community and coaching service for senior product leaders) and a three-time founder, CPO, and product executive with experience at Meta, Google, and Credit Karma. At Meta, he served as VP of Product, overseeing teams building messaging, groups, stories, and the main Facebook feed. Previously, he was Chief Product Officer at Credit Karma, where he led product management and design, scaled communications and operations as the company quadrupled headcount, and sponsored three acquisitions. At Google, he served as Product Leader for all real-time communication products, including launching and growing Hangouts (Google's video, voice, and text messaging solution pre-installed in Android and Gmail), and managing Photos across Google+, Android, Drive, and Picasa, plus helping launch Hangouts on Air on YouTube. He co-founded three startups, including SayNow (acquired by Google) and Cast Iron Systems (acquired by IBM). He now runs Skip Coach and hosts The Skip podcast and newsletter, having coached hundreds of product leaders. He has helped scale four top-100 mobile apps: Facebook feed, Credit Karma, Google Hangouts, and Google Photos. Follow the playlist: https://youtube.com/playlist?list=PLoROMvodv4rN447WKQ5oz_YdYbS74M5IA&si=DOJ5amlyRdyMJBhG

MAMike AbbotthostNSNikhyl Singhalguest

May 7, 2026·1h 3m·Watch on YouTube ↗

📖 CHAPTERS

1. 1

   Why product roles are being redefined: PM, design, and engineering are merging

   Mike Abbott frames the session as a shift away from purely technical founder talk toward product—and argues AI is collapsing traditional boundaries between product, design, and engineering. He contrasts old-school PRD-driven “project management” with founder-led consumer products and Apple’s designer–engineer model. The stage is set for a world where “vibe coding” changes who can build and how decisions get made.

2. 2

   Nikhyl’s background and the room’s confusion about product management

   Nikhyl introduces his Stanford-to-exec journey (founder + leadership at Google, Meta, Credit Karma) and his focus on careers and product leadership. He quickly diagnoses that many students don’t understand what PMs do and that interest in PM has dropped recently. He positions PM as the “glue” between building and selling.

3. 3

   A four-phase model: where product management shows up across the company S-curve

   Nikhyl lays out a lifecycle model of companies and explains how PM needs change by phase. Early stage is experimentation toward product-market fit (PMs often don’t make sense there). After PMF, PMs introduce consistency and coordination, and in hypergrowth they help scale and expand product lines; late-stage requires renewed innovation to fight the innovator’s dilemma.

4. 4

   Lessons from Google Hangouts: internal problems vs real customer needs

   In response to a question about Hangouts, Nikhyl explains why big-company initiatives can fail despite high priority. He argues Hangouts solved an internal consolidation problem more than a user problem, while WhatsApp won by nailing a narrow, reliable text-first wedge. He also highlights big-company difficulty sticking with non-obvious bets and emphasizes iteration speed as a competitive advantage.

5. 5

   Forward-deployed engineers vs PMs—and how AI changes customer insight gathering

   A question about forward-deployed engineers prompts a comparison to product management: both learn from real customer problems and feed insights back into the core product. Nikhyl argues AI is now extracting nuance at scale from many more signals (support chats, sales calls, feedback) and can summarize and prioritize them. This reduces reliance on humans as “information pullers” and shifts value toward judgment.

6. 6

   What Skip is: career ‘chapter’ thinking and building a talent-agency model for product leaders

   Nikhyl explains Skip as a long-term project to improve career outcomes by helping people think beyond their next job. He argues tech careers are made of many short chapters (15–18 jobs over 50 years), so sequencing matters. Skip aims to be a curated network and set of tools/content (including coaching-like guidance) grounded in real operator learnings rather than online hype.

7. 7

   The AI era paradox: higher anxiety, more building joy, and the end of ‘information mover’ jobs

   Nikhyl contrasts widespread student anxiety with excitement about building using AI tools—mirroring what he sees with executives. He claims AI is making the work more joyful for builders by removing status reports, meeting churn, and bureaucratic packaging of information. At the same time, leadership expects major layoffs, especially for middle managers whose value was coordination rather than hands-on building.

8. 8

   Is product management ‘dead’? Data says no—PM is evolving into product building

   Addressing layoffs (Salesforce, Block, Snap), Nikhyl argues the narrative that AI kills PM is overstated. He claims PM openings are at an all-time high, elite PM compensation is rising sharply, and companies still need decision-makers—just not bureaucratic organizers. The shift is from “manager” to “builder,” with PM/design/engineering blending into less siloed roles.

9. 9

   Big-company bets and founder control: Meta, the metaverse, and step-function growth pressure

   Nikhyl and Mike discuss Meta’s metaverse push as a founder-led, capital-intensive attempt to create the next computing platform—one that can’t be built by consensus. They contrast cultures (Meta/Apple vs Google) and highlight sunk cost fallacy risks. They also explain why big tech needs step-function bets: at massive scale, “small” wins don’t move the needle.

10. 10

    What’s most ‘bull’ in modern product work: theatrics, meetings, and info packaging

    Nikhyl criticizes modern product processes dominated by theatrics—slide decks, dog-and-pony shows, and layers of attribution far from the real experimenters. He argues AI will expose and replace much of this information choreography. A practical implication is the rise of “no meeting” or radically reduced-meeting cultures to maximize building time.

11. 11

    Community building and coaching: curation over scale, and AI as a replacement for generic advice

    Asked how Skip differs from other communities, Nikhyl argues most communities monetize and scale, attracting learners rather than top practitioners. His model is highly curated, time-efficient, and not designed to scale. He also predicts AI will outperform much of today’s generic coaching and community advice, forcing communities to become more distinctive and operator-led.

12. 12

    Advice for students: be modern with tools, invest in relationships, and think in systems

    Nikhyl answers what students should focus on to get strong tech roles: demonstrate modern, hands-on building ability; build durable networks; and develop a systems mindset for evolving abstraction layers. He argues brand names matter less than being current, and that the core challenge is no longer “can you build it?” but “should you build it, and how will it evolve?”

13. 13

    Looking back and looking forward: what he’d redo at Stanford, flat orgs, and when to leave a job

    Nikhyl reflects on what he’d change: stress less about grades, invest more in friendships, and value learning to solve unstructured problems with peers. He then addresses trends toward flatter organizations and why senior people take IC roles at rocket ships—because growth and modernity matter. He closes with guidance on when to move on: when you’re no longer being pulled forward or you’ve become comfortable.