alphalist.CTO Podcast - For CTOs and Technical Leaders

Latest Episodes:

#138 From Hacker News to W3C: How One Amazon Engineer Accidentally Shaped the Future of AI Browsers // Alex Nahas, MCP-B May 21, 2026

Show notes

How a browser-based fix for an enterprise auth problem became a W3C web standard and what it means for how AI agents will interact with the web.

Alex Nahas, founder of MCP-B and initiator of the WebMCP web standard, joins Tobias to explore one of the most underappreciated shifts happening in AI: the browser as the primary runtime for agentic systems.

Key topics covered:

What MCP actually is: an RPC framework for calling tools across processes, not the complex protocol it's made out to be
The OAuth problem: why MCP's push towards OAuth locked out most enterprise infrastructure still running on SAML
The WebMCP solution: running an MCP server in client-side JavaScript so agents can use the browser's existing auth context
How a Hacker News post posted under anesthesia got 400 upvotes and caught the attention of Google and Microsoft
Chrome 146 natively supports WebMCP, and what that means for adoption
The chicken-and-egg problem: why website owners won't add WebMCP support until clients support it, and vice versa
Agent identity: why agents don't need their own credentials and can operate as a subset of the user's identity
Real-time bidding for agents: the emerging market where advertisers bid to inject results into agent contexts

- The agentic web in two years: headless browsers, intent-based interfaces, and agents that only surface the UI you need.

[~04:30] "The browser itself is like the perfect sandbox we've been iterating on for so long now." — Alex Nahas [~06:30] "MCP is just an RPC framework. It's super simple. Basically just a wrapper around API documentation." — Alex Nahas [~13:00] "My first memory coming back was me arguing with people on Hacker News who didn't understand it." — Alex Nahas [~16:30] "Agents don't need their own identity. They can have an identity that's like a subset of the user who spun them off." — Alex Nahas [~32:30] "This reminds him of the dawn of programming — where everyone was just doing things and nobody really knew what they were doing, but people were just trying to figure things out." — Alex Nahas [~43:00] "Believe in yourself." — Alex Nahas

#137 - Only Three Search Engines Left Standing: One of Them Powers Your AI with JP Schmetz // Chief of Ads @ Brave May 07, 2026

Show notes

Thirty years building search infrastructure — and why the AI industry quietly depends on it.

SHOW NOTES

Jean-Paul Schmetz has been close to search infrastructure for nearly three decades — as founder of Clix, the European search engine that eventually became part of Brave, and now as Chief of Ads at Brave Software. In this conversation with Tobi, he opens up the hood on one of the internet's most misunderstood infrastructure layers.

Key topics covered:

The three independent search indices: why only Google, Bing, and Brave could answer every query on earth if the others disappeared
How AI grounding works — and how most AI products are either paying for Brave Search API or quietly scraping Google
The SERP API ecosystem: legal exposure, unit economics, and why Jean-Paul gives it a two-year shelf life
Google's origin story: the NDA, the 120% revenue share strategy, and why they spent years pretending to lose money
What it takes to build a search index from scratch — and why it's still a 10-year problem
The Inktomi story: the $1M autocomplete investment no one else was willing to make
Why Brave is profitable selling shovels to the AI gold rush — and what that looks like at $10M/month in infrastructure
Agents and the web: why most people won't know what to do with 50 agents, just like they didn't know what to do with 50 employees
What Jean-Paul would tell his 1996 self: think simpler, invest more aggressively, and stop underestimating capital

TIMESTAMPS: [to be added]

QUOTES:

[17:49] "Google was not better. It was just simply that they were driving you to queries they could answer better." — Jean-Paul Schmetz

[37:44] "There are more countries in the world that build atom bombs than countries that have a search engine." — Jean-Paul Schmetz

[49:08] "You're driving these Formula 1s with the wheels not properly attached." — Jean-Paul Schmetz

[01:28:45] "It's easy to appear intelligent when you list all the things that can go right, but it's much more courageous to actually claim what can go wrong." — Jean-Paul Schmetz

#136 - AI Writes Code: Who Architects the Consequences? with Neal Ford // Software Architect & Author Apr 23, 2026

Show notes

Fitness functions, agentic guardrails, and why experienced architects matter more than ever in the AI era

Show Notes: Neal Ford has spent decades thinking about how software systems hold together over time. In this episode, Tobias sits down with Neal to ask the question nobody is asking loudly enough: when AI agents write the code, who is responsible for the architecture?

We dive into:

-** Neal's origin story: **from journalism to mechanical engineering to computer science, and why writing made him a better architect

**AI as an "advanced beginner": **why LLMs pattern-match instead of reason, and why that distinction matters deeply
**Behavior vs. Capabilities: **the trap of building demos that scale to 60 users but collapse at 60,000
**Architectural fitness functions: **how to use deterministic guardrails to constrain non-deterministic code generation
Architecture Definition Language (ADL): using pseudocode to wire constraints into agents before they start building
LLMs as interpolators: generating platform-specific fitness functions in Java, .NET, or Python from a single pseudocode spec
**Legacy modernization: **why AI is best suited for re-engineering existing codebases, and what COBOL whispering looks like in practice
Ephemerality as a new architectural dimension: the first question every CTO should ask before building anything
**The future of developers and architects: **why experienced engineers are multiplied by AI — and 0 × 10 is still zero
The AI hype cycle: RAD, no-code, and now agents — same pattern, same blowback, different speed
Advice for CTOs: understand capabilities, govern what your agents build, and let life surprise you

Chapters: [00:00] Intro & welcome: Neal Ford — Software Architect & Author [00:28] Neal's journey: from journalism to computer science [02:10] Writing as a superpower in software architecture [03:45] AI as an "advanced beginner": the Dreyfus scale applied to LLMs [07:20] Behavior vs. Capabilities: the gap everyone is ignoring [11:05] Architectural fitness functions: guardrails for agentic systems [16:30] Architecture Definition Language (ADL) & LLMs as interpolators [21:00] Fitness function-driven architecture in practice [25:15] Legacy modernization: COBOL whispering and agentic re-engineering [30:40] Ephemerality: the new architectural dimension for CTOs [34:10] The future of developers, architects, and pull requests [38:50] The AI hype cycle: fads vs. trends [42:15] AI pricing models and the Silicon Valley playbook [44:30] Easter egg: choosing computer science over CIS — and why it paid off [46:00] Advice to his younger self: let life surprise you [47:10] Conclusion & final thoughts

#135 - From Legacy to Innovation: Yahoo's Modernization & AI with Lee Zen // CTO @ Yahoo Jan 29, 2026

Show notes

Modernizing Yahoo in the private-equity era: legacy constraints, shipping velocity, and AI-native consumer products

Yahoo is far more than a nostalgia brand—it’s a broad consumer platform operating at huge scale. In this episode, Tobias sits down with Lee Zen (CTO @ Yahoo) to explore how the company is modernizing in the private-equity era, and what “innovation” looks like when you’re also responsible for decades of legacy systems.

We dive into:

Yahoo’s consumer portfolio: Mail, Finance, Sports, News, Search—and what that implies for platform strategy
What changes under private equity: priorities, focus, and modernization constraints
Modernization in real terms: cloud adoption, legacy trade-offs, and sequencing big bets
Shipping velocity as a leadership lever: faster learning cycles over perfect planning
Organizational mechanics for rapid experimentation at consumer scale
AI in engineering: where it helps, where it creates new bottlenecks, and “AI as a coworker”
AI in the product (real use cases): mail catch-up, news key takeaways, finance and fantasy-sports insights
The hardest problems at consumer scale: cost optimization, velocity, and quality without regressions
Career reflections: imposter syndrome, self-belief, and staying hands-on as a CTO**

Chapters:

[00:00] Intro & welcome: Lee Zen (CTO @ Yahoo) [00:28] Lee’s journey & Yahoo’s evolution [01:14] Early computing: DOS, QBasic, and the builder origin story [03:43] Academic background: CS + AI foundations [05:20] Yahoo today: portfolio breadth & what private equity changes [08:54] Modernization: cloud, legacy constraints, and technical trade-offs [17:44] Leadership & org design: enabling speed and experimentation [22:52] AI integration: tool vs. coworker, and the future of engineering [31:38] AI across Yahoo’s consumer products: mail, news, finance, sports [32:21] Avoiding “AI labels”: enhancing UX with human + AI judgment [33:26] Consumer-scale engineering challenges: cost, velocity, and quality [34:28] Easter egg: side projects and reflecting on the past [35:34] Advice to his younger self: self-belief, self-love, imposter syndrome [36:28] Conclusion & final thoughts

#134 - From Inner to Outer Loop: Agentic Coding, Stacking PRs, and the Cursor Merger with Greg Foster // CTO @ Graphite Jan 15, 2026

Show notes

Solving the "Outer Loop" bottleneck: Agentic coding, Stacked PRs, and the future of the CTO role with Graphite's Greg Foster

The "Inner Loop" of coding (typing syntax) has been solved by AI. The new bottleneck is the "Outer Loop"—reviewing, testing, and merging the flood of code that agents generate.

In this episode, Greg Foster (CTO of Graphite, now part of Cursor) explains why this shift drove their merger and what it means for the future of engineering.

We dive into:

The Outer Loop Crisis: Why fast code generation breaks traditional review processes (and how to fix it).
Agentic Engineering: The 2029 vision where engineers become "architects of agents" and writing code trends to zero.
Stacked PRs: Why smaller, dependent changes are the only way to maintain velocity at scale.
Metrics that Matter: Why "PRs per engineer" is actually a valid proxy for velocity (velocity = speed + vector).
The Cursor Merger: Combining the best text editor (Inner Loop) with the best review platform (Outer Loop).
Provenance in Git: The need for storing "prompts" and AI attribution directly in commit history.
Advice to Young Engineers: Why understanding the business model is as important as reading O'Reilly books.

Chapters:

[00:00] Intro: Greg's journey from iOS apps to Airbnb infrastructure
[01:25] Graphite & The Pivot: Bringing "Phabricator-style" tools to GitHub
[03:52] Reinventing the Pull Request: Stacked PRs and Merge Queues
[13:20] The Velocity of Dev Tools: When Copilot/Cursor changed the game
[20:41] Metrics: Is "PRs per engineer" a vanity metric or a velocity proxy?
[24:22] Jevons Paradox: Why 2x productivity means more engineers, not fewer
[26:30] The Merger: Why Graphite joined Cursor (Inner + Outer Loop)
[33:30] Provenance: Storing AI prompts in Git history
[52:00] The 2029 Vision: Writing code -> Zero. Reviewing Agents -> 100%.
[56:17] Future of CI: Auto-generated sandboxes with agentic QA
[59:26] Advice to his younger self: Understand the business, not just the code

#133 - Build the Learning Machine: AI Adoption, Flow Metrics, and the Future of the CTO Role with Eric Bowman Dec 15, 2025

Show notes

From “dangerously skip permissions” to the Andon cord: voluntary adoption, flow metrics, and how agents change what CTOs optimize for

Partner Tradegate Direct: Europe’s most direct online broker – trade for free, efficiently, and directly on the stock exchange. Trade directly here

TOPdesk: Discover the future of internal IT in the DACH region with the "Inside ITSM 2026" report – featuring exclusive data on AI, DEX, and collaboration from 6,000 IT professionals. Download the report here

In this episode, Eric Bowman (CTO @ King.com) breaks down how AI is changing programming, creativity, and technical leadership. We talk about what “living on the edge” looks like with modern AI tools, why “AI is just technology” is still the right mental model, and how CTOs can build organizations that stay fast, adaptable, and focused on time-to-value.

We dive into:

Eric’s journey: TomTom → Zalando → CTO at King.com
What “living on the edge” with AI means in real engineering workflows
The future of programming: what shifts when AI becomes a default collaborator
Why AI creativity is different from human creativity (and why that matters)
What an “ideal” tech organization looks like in an AI-first era
Time-to-value and time-to-learning as the CTO’s north star
The Andon cord concept applied to software delivery
How the CTO role evolves as AI reshapes execution, leverage, and expectations
Motivating engineers to embrace AI without turning it into a mandate
Voluntary adoption as a rollout principle (and where it breaks)
Jevons paradox and why “cheaper” AI can still increase total spend
Practical reflections and advice for tech leaders navigating the shift

Chapters:

[00:53] Meet Eric Bowman: CTO of King.com [02:24] Eric's Journey in Tech [03:25] Living on the Edge with AI [05:43] The Future of Programming with AI [09:51] Navigating the Complexities of AI [22:03] AI Creativity vs. Human Creativity [28:41] Building the Ideal Tech Organization [29:04] Focusing on the Tech Field [29:21] The Future of SaaS [29:50] AI as Just Technology [33:03] Building a Learning Machine [33:32] The Onan Cord Concept [35:29] Time to Value and Learning [38:23] The Evolving Role of CTOs [41:04] Motivating Engineers to Embrace AI [46:02] Voluntary Adoption of Tools [51:35] Jevons Paradox and AI [53:55] Reflections and Advice [56:12] Conclusion and Farewell

#132 - Clarity Over Tooling: Velocity & Building Teams Without Drama with Loïc Houssier // CTO @ Superhuman Mail Nov 27, 2025

Show notes

From acquisition carve-outs to 100ms interaction rules: Engineering velocity through team clarity, not tool proliferation

Partner TOPdesk: Discover the future of internal IT in the DACH region with the "Inside ITSM 2026" report – featuring exclusive data on AI, DEX, and collaboration from 6,000 IT professionals. Download the report here

Outline How do you maintain execution velocity while building quality products? Loïc Houssier (CTO of Superhuman Mail, formerly Superhuman) offers a contrarian perspective: the answer isn't better tools or frameworks—it's radical clarity about team missions and strategic alignment.

With experience spanning French defense contractors (Orange, Thales), navigating DocuSign's complex French acquisition, and now steering Superhuman through its Grammarly acquisition/rebrand, Loïc brings a unique European-to-SF perspective on technical leadership.

Key insights for engineering leaders:

Execution & Velocity • PR per engineer per week as the "less bad" metric - track trends, not absolutes across teams • Clarity drives speed: clear team missions eliminate dependency bottlenecks and headquarters approval loops • Most velocity gains come from strategy clarity, not tooling improvements • Vertical team alignment: minimize cross-team dependencies by organizing around experiences (calendar team, compose team) • Focus quarterly: solve one major problem per quarter (velocity this quarter, quality next quarter)

Technical Architecture Decisions • Monorepo philosophy: resist microservices until genuine pain necessitates splitting • 100-millisecond interaction rule: every UI interaction must complete under 100ms • Offline-first architecture: sync happens in background, all actions execute locally • Gmail/Outlook API integration over IMAP for modern email clients • Modulith with domain-driven design over distributed microservices

Team Organization • Guild structure: formalize existing technical conversations (iOS guild, backend guild, AI guild) • Guild leaders surface quarterly problems and negotiate engineering time with product • Platform team + vertical feature teams = minimal dependencies • Full-stack teams owning specific experiences prevent feature factory mentality • Aligned autonomy: clear objectives, flexible execution methods

Framework Skepticism • Spotify model: "mostly marketing" according to actual Spotify engineers • GitLab remote-first: ~70% there, not the paradise portrayed • Context matters more than best practices from big tech • Apply frameworks as inputs, not blueprints - adapt to your specific context • Agile manifesto written by senior architects who knew each other - doesn't translate directly to teams fresh from college

Product & Design Philosophy • Laser-focused personas (professionals with heavy email volume) vs. Gmail's everyone approach • Four hours per week user time savings from better email UX • Design-centric like Linear: quality experience for narrow audience beats mediocre experience for everyone • Promotion frameworks should align with product goals: bake quality into career ladders if quality matters

Acquisition Integration • DocuSign French carve-out: Ministry of Finance blocked some assets, created split structure • Execution during acquisition demonstrates team value beyond revenue/customers • French labor law calculated as risk, not blocker - opportunity cost of not entering EU market • Smooth landings possible: kept redundant roles due to EU market subtleties

Cultural Observations • US mindset: "we might die tomorrow" drives urgency vs. EU "we're already successful" complacency
• European social safety nets enable higher risk-taking than perceived - losing your job in France is manageable • US risk-taking constrained by healthcare costs, college tuition, lack of safety net • Europeans are "grumpy" seeing empty glass, Americans see half full with optimism

Chapters:

[00:51] Superhuman, Grammarly, and the rebrand to Superhuman Mail
[01:47] Why Grammarly became Superhuman: AI-native productivity suite vision
[06:18] Career journey: Math PhD track to security researcher at Orange and Thales
[08:18] Submarines and defense contracts: Building the muscle to learn deep tech fast
[09:53] DocuSign's French acquisition: Navigating labor law and Ministry of Finance approvals
[12:16] Execution velocity: Getting shit done fast as a competitive advantage
[15:43] Personal secret sauce: Learning fast, working with smarter people, execution focus
[18:58] PR per engineer per week: The "less bad" velocity metric
[22:26] Vertical team alignment and minimizing cross-team dependencies
[24:22] Monorepo philosophy: Resist microservices until it's genuinely painful
[27:02] Framework skepticism: Why Spotify and GitLab models are "mostly marketing"
[30:41] Quarterly focus: Solve one major problem every three months
[32:30] Guild structure: Formalizing existing technical conversations
[36:14] Platform teams + vertical feature teams = ownership without dependencies
[38:31] The Linear of email: Laser-focused personas and design-centric approach
[40:25] Four hours per week saved: The value proposition for heavy email users
[42:05] 100-millisecond rule: Offline-first architecture for instant interactions
[46:16] Google's engineer-driven culture and the Gmail maintenance problem
[48:38] Promotion frameworks determine product quality
[50:02] Career advice: Take more risk in Europe - safety nets enable experimentation

#131 - AI Product Strategy: When to Build and When to Wait with Matthias Keller // CPO @ Kayak Nov 13, 2025

Show notes

From Alexa to LLMs: Platform experiments, distribution challenges, and how AI is democratizing feature development in travel tech

Tradegate Direct: Europe's most direct online broker – trade for free, efficiently, and directly on the stock exchange. Trade directly here

In this episode, Matthias Keller (CPO @ Kayak) shares strategic lessons about making AI product decisions under uncertainty. With 12 years at Kayak and experience spanning multiple AI waves—from Alexa to LLMs—Matthias offers a masterclass in knowing when to invest early and when to wait.

We dive into:

Strategic framework for evaluating emerging AI platforms (Alexa, ChatGPT, Vision Pro, Apple Intelligence)
Why Kayak's 2016 Alexa experiments failed and what that taught them about timing
The shift from "will this work?" (voice) to "it should work" (LLMs) and why that matters
Competing with distribution giants: Google Flights has massive advantages, so when do you innovate vs. wait?
Real talk on platform bets: early ChatGPT plugins, evaluating ROI on new platforms
How LLMs democratized AI development—engineers now build AI features without data scientists
User expectation shifts: the "why" questions and what they mean for product strategy
Commercial complexity: airlines control content, credit cards worth more than tickets
The "if you build it they may come, if you don't they won't" mindset for CTOs
Balancing first-mover advantage with execution realities in your org

This conversation offers actionable frameworks for product and engineering leaders navigating AI strategy decisions.

Chapter 1: From Sensors to Travel Tech (00:00 - 09:00) Matthias shares his unconventional path from measuring train wheel vibrations and wireless sensors on mountains to joining Kayak 12 years ago. He discusses the growing complexity of travel booking as airlines unbundled services, creating 15+ ticket options instead of just economy, business, and first class.

Chapter 2: Competitive Landscape & Google Flights (09:00 - 13:00) The challenges of competing in a space where Google Flights has massive distribution advantages. Matthias explains how Kayak maintains its edge through innovation like "hacker fares" (combining one-way tickets from different airlines) and comprehensive comparison across hundreds of partners.

Chapter 3: Platform Evolution - From Alexa to LLMs (13:00 - 28:00) A deep dive into Kayak's platform experiments, from 2016's Alexa skills and Facebook Messenger bots to today's AI mode. Matthias reflects on what worked (flight tracking), what didn't (voice checkout), and the key differences that make LLMs more successful than earlier voice assistants.

Chapter 4: AI Mode & Conversational Search (28:00 - 41:00) How Kayak integrated LLM-powered search across their products, not just as a separate experience. Matthias discusses engagement patterns, the importance of explaining when AI helps versus traditional search, and fascinating user behaviors like asking "why" they should book specific options.

Chapter 5: Distribution in the AI Era (41:00 - 46:00) The "dam breaking" moment when airlines and travel providers might embrace AI platforms for distribution. Discussion of commercial barriers, ecosystem control, and how the industry balance between direct booking and meta-search might shift.

Chapter 6: AI Democratizing Development (46:00 - 50:00) Matthias explains how LLMs enable software engineers to build AI features without data scientists, using examples like Kayak's price check feature that uses vision AI to compare flight prices from screenshots.

#130 - From PhD Research to DuckDB: Building the Next Generation of Analytical DBs with Mark Raasveldt // CTO @ DuckDB Oct 16, 2025

Show notes

How single-node performance and embedded analytics are revolutionizing database architecture for modern applications

Tradegate Direct: Europe's most direct online broker – trade for free, efficiently, and directly on the stock exchange. Trade directly here

In this episode, we dive deep into the world of analytical databases with Mark Raasveldt, the co-founder and CTO of DuckDB Labs. Mark takes us through his fascinating journey from academic research to building one of the most talked-about databases in the industry.

We explore:

How DuckDB emerged from academic research at CWI Amsterdam
The technical philosophy behind embedded analytical databases
Why single-node performance still matters in the age of distributed systems
The challenges of building a database system from the ground up
Open source business models and the DuckDB Labs approach
The evolution of columnar data formats and Parquet optimization
How DuckDB is making high-performance analytics accessible to all developers
The future of analytical data processing and embedded systems

This conversation offers unique insights into database architecture, performance optimization, and the intersection of academic research and commercial success.

#129 - $32B Lessons: Building CTO Teams, Rapid Innovation, and Staying Customer-Connected with Solal Raveh Sep 18, 2025

Show notes

What Wiz's $32B acquisition teaches about scaling CTO teams, rapid innovation, and customer-centric leadership

Tradegate Direct: Europe's most direct online broker – trade for free, efficiently, and directly on the stock exchange. Trade directly here

What does it take to build a company worth Google's $32 billion acquisition? Solal shares the hard-won lessons from scaling technical teams during one of the fastest-growing security companies in history.

Key leadership insights from the episode:

• CTO Office Evolution: How Wiz split technical leadership into 3-4 specialized tracks focused on domain expertise rather than geography • The Geographic Cloning Failure: Why hiring locally for technical roles created dissatisfaction and duplication instead of excellence
• Remote Team Success: Building global CTO teams around container security, API infrastructure, and runtime protection expertise • Incubation Philosophy: Moving from building teams to rapid POC development - like their 3-hour response to the Shy Hulud NPM exploit • Customer-Centric Engineering: How every CTO team member stays connected to customer challenges rather than waiting for inbound requests • Innovation Metrics: The challenge of measuring incubation success vs finished features, plus P99 performance tracking for enterprise readiness • People-First Leadership: Why focusing on people and customer problems trumps pure technical automation • Security Industry Insights: Making security "not scary" through gamification and community engagement

Technical Context (18% of episode): • Agentless API scanning that maps entire cloud environments in minutes vs weeks • Graph database visualization of attack paths from code credentials to AWS admin access • Risk contextualization: Why a CVSS 9.9 vulnerability on unused images can wait, but the same vulnerability across 10,000 live VMs demands immediate action • AI agent "Mika" that correlates threat intelligence with specific infrastructure data

Chapters:

[01:49] - What makes Wiz worth $32 billion: People and technology combined
[04:08] - Technical architecture: Agentless scanning to graph databases to agent validation
[10:56] - Personal journey: From assembly coding to customer-focused engineering
[14:18] - CTO office structure: Splitting technical leadership into specialized domains
[17:30] - Three-fold CTO mission: Foresight, gray areas, and team incubation
[19:35] - Evolution from team building to rapid POC development
[23:30] - Security industry paradigm shifts: Vulnerabilities, identities, and AI challenges
[25:30] - Log4Shell response: Community support and agentless advantage
[34:17] - Major failure: Why geographic CTO team cloning doesn't work
[40:09] - CTO metrics challenges: Measuring innovation vs finished features
[43:16] - Missing hands-on work: The balance between leadership and building
[45:44] - Time travel advice: Focus more on people than automation

Our TOPPODCAST Picks

Follow Us

Stay Connected

alphalist.CTO Podcast – For CTOs and Technical Leaders

- The agentic web in two years: headless browsers, intent-based interfaces, and agents that only surface the UI you need.

Related Podcasts

Links

Stay Connected