Michael Kubba | Working for Apple, Tesla, and Google

Being an Engineer · 15 Jul 2022 · 59m · Episode 27

What this episode covers

Michael Kubba, COO at Fellow, discusses his career leading hardware teams at Apple, Tesla, and Google. He details the intense design and manufacturing challenges of the Apple TV remote, the vertical integration and mission-driven culture at Tesla, and the product definition struggles of Google Glass at Google X. Kubba emphasizes the importance of rapid prototyping, clear product development phases, and becoming a temporary expert in cross-functional areas to succeed in hardware engineering.

Other shows on the same ground, closest first.

  • Embedded.fm · 1h 32m

    47: Bridge of Toothpicks

    Nathan Tuck, a manager at NVIDIA working on the Tegra K1-64 CPU architecture, joins hosts Christopher and Elecia White to discuss the evolution of the hardware industry, career paths, and management challenges. The conversation covers the shift from big companies like SGI and HP to startups, the difficulties of remote work, and the pitfalls of agile methodologies and rigid scheduling in engineering. They also explore different types of burnout, from physical exhaustion to organizational fatigue, and the importance of maintaining conceptual integrity in product design.

  • TRADEOFFS · 48m

    T-24-004 : Tom George - Hardware Startup Engineer to Google Product Lead

    Tom George, now a Product Team Lead at Google leading the Pebble initiative, recounts his journey from early hardware startups like Maritime Broadband and QuadLogic to his current role in Sustainable Cities. He details the engineering trade-offs of building satellite communication systems for cargo ships, including the failure of using commercial stepper motors in marine environments, and the organizational challenges of separating R&D from sustaining engineering at QuadLogic. George explains his decision to halt production at Sidewalk Labs when the Pebble sensor was not ready for scale, and his subsequent pivot at Google away from hardware manufacturing toward policy and urban planning solutions.

  • The Amp Hour · 1h 09m

    Vellicate Videogame Vocation

    Jeff Kaiser, founder of the MightyOhm electronics kit business, discusses his transition from self-employment to joining Valve as a hardware engineer. He details Valve's unique flat organizational structure, the rigorous interview process, and the importance of maintaining a public portfolio of open-source hardware projects to demonstrate engineering breadth. The conversation also covers the scaling challenges of the Pebble Kickstarter campaign and the legal implications of Twitter's Innovators Patent Agreement.

  • Go/No-Go · 1m

    Welcome to Go/No-Go

    Hosts Jon Bruner and Alex Hao introduce the new podcast Go/No-Go, which explores the critical decisions in designing, manufacturing, and shipping hardware products. They announce that the first episode will feature an interview with Tony Fidel, known for his work on the iPod, iPhone, and Nest Learning Thermostat, discussing his experiences and the future of AI-enabled hardware. The show is produced by Lumafield, which utilizes industrial CT scans to analyze products ranging from athletic equipment to aerospace components.

  • Product Startup · 28m

    108: Hardware Design Tips from Apple & Intel Leader

    Kapil Kane, Director of Innovation at Intel and former Product Design Lead at Apple, explains how startups can apply the rigorous validation processes used by tech giants to their own hardware products. He details Intel’s internal accelerator, Growth Acts, which uses a business model canvas and validation plans to test assumptions before prototyping, contrasting this with Apple’s focus on pure technical execution for products like the iPod Shuffle and MacBook Air. Kane emphasizes that successful hardware requires a triad of solid technology, user experience, and a viable business model, urging founders to be coachable and demonstrate conviction through working prototypes rather than just ideas.

The summary, chapters and topics are generated from the episode’s audio by this directory, not written by Being an Engineer. The episode itself belongs to its publisher.