Podcast Explorer
Any timePast weekPast monthPast year

23 subjects for “hiring great engineers”

4:28

Building the Engineering Team

Published Apr 6, 2026

How Vidio (Indonesia's #1 Streaming Platform) Built Great Engineering Culture—Now Supercharged by AI

Tommy explains how he built the team from five people: hire for hunger, smartness, and growth rather than tech stack familiarity — 'hire for attitude and not just pure aptitude'. He discusses using extreme programming practices like pair programming for onboarding, defining culture early, growing the team to 200 across four offices, and achieving ~7-year average engineer tenure. He notes pride that Geekhunter headhunters listed Vidio as the top company to poach from.

0:56

Hiring world-class engineers at Flint

Published Dec 3, 2025

Being a founding engineer at an AI startup

Briefly asked what it takes to hire world-class engineers in Silicon Valley, Michelle says it comes down to showing that you deeply care about the team, building high trust, and having a big vision that the company will change the world.

7:59

Hiring for Builders, Spikes and Craftsmanship

Published Sep 18, 2026

Building Tools for Defenders 🛡️ — with Rahul Raina

Rahul outlines what TRM looks for in hires: exceptional problem framing and first-principles thinking (even more important in the AI era to counter lazy, sloppy thinking), a track record of making things happen without being asked (including in personal lives — athletes, dancers, former Navy SEALs), and being a 'humble mastercraft person' who keeps honing their craft. Asked about the role of specialists versus generalists, he says they aren't at odds: the best engineers are T-shaped, deep in a spike but broad in applicability, and TRM hires for spikes while expecting people to care about real-world customer outcomes, not technology for its own sake.

2:57

Gardeners and Great Engineers

Published Sep 17, 2026

AI Skills with Matt Pocock

Matt embraces the gardener metaphor: entropy makes weeds inevitable, and diagnosing them before they become problems might be the essential skill now. He reframes engineers as their agents' platform team, building environments for agents to succeed. Asked what makes a great software engineer, he answers with one word — introspection: the ability to observe your own process and encode it into something AI can work with, citing Lars Gramml at Vercel building a software factory for the AI SDK.

6:22

Faire and AI-Driven Engineering

Published Apr 1, 2026

Scaling Uber with Thuan Pham (Uber’s first CTO)

Tuan describes Faire: ~1,000 people, ~300 engineers plus data science, hybrid three days in office, with hubs in SF, Waterloo, and Toronto. He then discusses AI at Faire: boosting search/recommendation as an AI shopping consultant, swarm coding with orchestrated agents producing dramatic output lifts—their best engineers doubled business impact—and the next frontier of building features on older entangled codebases. He argues AI levels the playing field but great engineers (curious, fearless, innovative) still differentiate 2-3x, and complacency is death.

3:59

Hiring and career advice

Published Jan 21, 2026

How AWS S3 is built

The guest describes hiring all kinds of engineers, from early-career to 15-year veterans, unified by a deep sense of ownership and personal commitment to preserving customers' bytes. Her advice: relentless curiosity and creativity—drawing your own lines rather than coloring within them—and staying current with research, such as applying formal methods to storage systems and rethinking failure.

5:34

Hiring exceptional hardware teams

Published May 17, 2026

Why the next AI boom is physical AI | Caitlin Kalinowski (ex-OpenAI, Meta, Apple)

Caitlyn explains that for zero-to-one fields you can't hire people who've done the exact same thing because it doesn't exist yet; she sources talent from autonomous vehicles — which share the sensing stack, safety trade-offs, and hardcore engineering — and seeks strong generalists who transfer learnings across fields, alongside builders of the new thing and scalers of other things. She champions truly AI-native ~20-year-olds who use AI from the ground up and work much faster, arguing they can teach the rest how to think; she pushes back on the narrative that AI erased junior roles, insisting teams need both senior and junior people even if smaller. She adds that mission alignment unifies teams bridging AI researchers and hardware folks, and that after the checkboxes she relies on gut feel for the 'spark': motivated to learn and by excellence, open to updating, and hungry to win.

2:42

Hiring profiles and the ambition ceiling

Published Jun 21, 2026

What happens after coding is solved? | Fiona Fung (Claude Code & Cowork)

Lenny asks about the two hiring profiles from Fiona's talk. Fiona describes hiring creative builders with product sense who own products end-to-end - idea, build, feedback, iterate, polish - and deep systems experts for the parts that still need trust-but-verify, noting that when she joined Claude Code the product-generalist team lacked systems and distributed-systems expertise. Lenny then raises the theme of ambition, sharing a 10x engineer's realization that previously 'hard' ideas are now trivially possible with Claude Code, so the question becomes how ambitious you can be. Fiona resonates, describing a non-mobile engineer who shipped a mobile feature with Claude as a partner - AI has lifted the ceiling of what anyone can do.

13:22

Hiring T-Shaped Fast Learners

Published Nov 27, 2025

How to Build Product Development Teams 🛠️ — with Rob Zuber

Rob describes his ideal hire profile: T-shaped people (deep in one or two areas, broad skills) from the IDEO metaphor, valuing rate of learning over current skills—especially critical in the LLM era. Depth should vary across team members since you're building a team, not clones. He shares stories about hiring his first engineer who switched the stack from Python to Rails, building a data center with zero experience in 1998, and why every early hire is a huge fraction of the company.

10:46

Hiring Quiet Engineers and AI Workflows

Published Feb 25, 2026

Mitchell Hashimoto’s new way of writing code

The best engineers Mitchell has hired are notoriously private 9-to-5ers with no social media or GitHub presence who are locked in during work hours — resumes from unknown companies with zero public contributions signal deep knowledge. He reflects that context-switching to social media destroys flow, and that he himself thinks through code, products, and CLIs in bed at night, giving him an edge because he never turns thinking off. On hiring in the AI era, he'd require AI-tool competency and would want every engineer to always have an agent running — for research, planning, or slow background tasks — while turning off notifications so the agent never interrupts him. He describes how he forced himself to reproduce his own work with Claude Code, learned planning steps and test harnesses improve results, and advises skeptics to reproduce their research (not necessarily coding) with an agent.