LutzTalk is where real systems builders talk about the technology that actually keeps people connected.

In this episode, Austin sits down with Philip Lemaster, Software Engineer at Meta, whose path into engineering was anything but traditional. From studying psychology at the University of North Carolina at Charlotte and working as a medical assistant in healthcare, to building APIs for financial platforms and now contributing to account access systems that serve billions of users, Philip’s career is a study in how human systems and technical systems intersect. Austin and Philip dig into what it means to build infrastructure people rarely see but constantly rely on. They talk about designing REST APIs for high-stakes financial applications, maintaining reliability at scale, balancing privacy with usability inside global identity systems, and why communication and mentorship are just as critical as clean code.

If you’re curious how psychology, healthcare, investing platforms, Meta-scale infrastructure, and game development all connect—and what responsibility really means when you’re writing code that billions depend on—this one’s for you.

LutzTalk is where real systems builders talk about the technology that actually keeps people connected.

In this episode, Austin sits down with Neil Schneider, Safety and Health Specialist at the Occupational Safety and Health Administration, whose career path is a complex mix of both technical interest and engineering excellence. From studying civil engineering at the University of Louisiana at Lafayette and working as a drilling engineer at Baker Hughes, to leading complex safety investigations across multiple industries, Neil’s career is a case study in how field experience shapes systems thinking. Austin and Neil dig into what it really means to understand risk inside complex environments. They talk about real-time engineering thousands of feet underground, how small process failures turn into major incidents later, and why communication, documentation, and technical clarity determine whether safety systems actually work.If you’re curious how oil fields, federal investigations, drones, podcasting, and engineering discipline all connect—this one’s for you.

LutzTalk is where real systems builders talk about the technology that actually keeps people connected.

In this episode, Austin Lutz turns the mic inward and reflects on the path that led him here. From early curiosity about networks and media, to years spent building, operating, and designing communication systems, this episode is about how mentors, lived experience, and hands-on work shape the way builders think. It’s a look at how understanding systems comes from observation, failure, and patient explanation, not memorization or shortcuts.

Austin walks through the thread that connects dial-up modems, home networks, enterprise infrastructure, voice, video, and collaboration platforms. He explores how each stage added a layer to his systems intuition, and how the generosity of mentors who explained their thinking created a foundation that still guides his work today. This episode is about the pipe more than the payload, and about why sharing how we think matters just as much as shipping outcomes.

If you’re interested in the human and technical networks behind modern communication—and why this podcast exists as a place to document that thinking in the open—this one’s for you.

LutzTalk is where real systems builders talk about the technology that actually keeps people connected.

In this episode, Austin sits down with Jai Misra, Software Engineering Manager at Cisco Meraki, whose path into engineering started nowhere near a computer science classroom. From studying Globalization and Arabic at Gettysburg College and working in immigration advocacy, to leading engineering teams responsible for platforms used at global scale, Jai’s career arc is a case study in how perspective shapes architecture.

Austin and Jai dig into what it really means to build software that lasts. They talk about the difference between consultancy speed and enterprise durability, why well-architected systems save you years of pain later, and how leadership, mentorship, and documentation quietly determine whether a team thrives or burns out.

If you’re curious how someone with a non-traditional background ends up leading serious engineering work at Cisco Meraki—and what that says about the future of software development—this one’s for you.