From Dishwasher to Engineering Manager

The episode features Mike discussing his career trajectory from dishwasher to line cook to engineering manager, and how those early experiences fundamentally shaped his approach to development work. Mike argues that while the technical skills from dishwashing are minimal, the life skills are substantial and often overlooked.

The first major lesson discussed is thriving in chaos. Mike explains that in a kitchen, unexpected breakdowns constantly occur—sink failures, equipment malfunctions, orders piling up—yet work must continue. This taught him to accept chaos as part of the process rather than panic. He contrasts this with developers who freeze during production incidents. Mike credits his kitchen experience with giving him the resilience to handle major outages calmly, treating them as procedural problems to solve step-by-step rather than catastrophic events. Matt adds that some people simply cannot adapt to chaotic environments and may need to steer their careers toward positions without high-pressure incidents—which is also a valuable self-discovery.

The second lesson is leadership and team management. When Mike became a line cook lead, he learned to position people in roles matching their strengths, cross-train staff across all kitchen stations, and identify who could teach others effectively. He explicitly rejects trial-by-fire management without support, noting that screaming at someone without backing them up creates resentment and doesn't build capability. Instead, he advocates servant leadership where managers work alongside their teams, understanding technical details deeply, and strategically applying pressure only when someone is ready. He applies this directly to managing developers: putting backend specialists in frontend roles temporarily to build full-stack understanding, identifying which people excel at teaching, and knowing when to jump in to prevent team members from completely failing.

Attention to detail is the third lesson. In restaurants, small oversights—slightly warm eggs, dirty plates, missed orders—have serious consequences like food poisoning and customer loss. This taught Mike to value seemingly tedious processes like temperature checks and deployment checklists, even when they seem redundant. Matt expands on this with his factory experience, where noticing small details helped him understand the entire system's flow and anticipate needs (like empty carts appearing after product moves). Both speakers emphasize that paying attention reveals patterns and helps you understand your position within larger systems, which is crucial for being effective and getting promoted.

The final lesson is understanding motivation. Mike's motivation comes from never wanting to return to kitchen work, which drives him to continually improve and maintain options. Matt's motivation came from a different angle: finding pride in building good infrastructure systems. He discovered this through his R&D role where he designed networking systems and became emotionally invested in systems he created. He notes this same motivation pattern appears in his gaming habits—he builds infrastructure rather than slogging through dangerous environments. Both speakers acknowledge that different people are motivated by different aspects of work, and discovering what motivates you personally is as important as the technical skills.