Uploaded November 2025 | Updated September 2026, 1 week ago

---

Join this week's Vercel Community Session and ask our CTO anything!

Chapters
00:00 | Welcome and introductions
03:21 | What is the most important metric for engineering teams?
05:35 | What is a bad metric to measure engineering teams?
06:46 | How Vercel decides what to build: Bottoms-up vs. top-down
10:04 | Balancing customer requests with the existing product roadmap
12:04 | How to build and staff effective engineering teams
13:54 | The role of the CTO's office and scaling leadership
17:05 | Q&A: Removing default Vercel domains for SEO
20:53 | How Google’s culture influenced Vercel's engineering paths
22:56 | What kind of AI agents are customers successfully shipping to production?
27:07 | Automating the community team's workflow with v0
30:16 | How to engineer products that can adapt to new tools without rewrites
34:14 | How Vercel's tech stack has changed over the years (Go, databases, and Kubernetes)
39:24 | Exciting future trends: Workflows, AI agents, and the next 15 years
43:14 | Architecting for observability, reliability, and error recovery in AI workflows
47:21 | Vercel's approach to feature flags, backwards compatibility, and instant rollbacks
50:53 | Thoughts on "vibe coding" vs. "vibe engineering"
55:04 | What makes the Vercel community truly impactful?
57:44 | Upcoming features: Post-quantum cryptography on the edge
01:00:24 | Outro and upcoming community events