Distributed.

Trust, collaboration, and adaptability define the best engineering teams.In this episode of the Distributed podcast, host Jack Hannah sits down with Pavel Hubich, Software Engineer at Spotify, to explore the realities of remote and hybrid work. Pavel shares his journey navigating career shifts, relocations, and the challenges of distributed collaboration. He opens up about why he prefers working in person, how hybrid work can create communication bubbles, and what teams can do to foster trust despite physical distance.They also discuss the impact of structured rituals like daily standups and the Swedish tradition of Fika, how mob programming transformed his team’s efficiency, and why balancing autonomy with connection is critical for engineers working remotely.Highlights:Navigating career transitions from frontend to backend engineering while relocating across continentsWhy hybrid work can unintentionally create communication bubbles—and how teams can bridge the gapsThe role of standups, casual rituals, and structured collaboration in building trust remotelyUsing mob programming and Architecture Golf to reduce context switching and improve team alignmentFinding a balance between focus, flexibility, and human connection in a remote-first worldIn this episode, we cover:(00:00) – Kicking things off with Pavel Hubich(01:24) – From EPAM to Spotify: Pavel’s software journey(05:18) – Relocating to San Francisco for on-site work(08:01) – Why Pavel prefers the office over remote(13:56) – Rituals and loading screens: creating mental transitions(16:03) – The real challenge of remote work: earning trust(18:24) – Standups and Fika: building connection remotely(21:45) – When high output doesn’t equal team cohesion(26:29) – How mob programming brought the team back together(29:53) – Using architecture golf to share context and collaborate(34:29) – Making hybrid work without creating bubbles(36:25) – Building trust without burning outWhere to connect further:Connect with Pavel Hubich on LinkedInFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

How do you foster connection and collaboration in a remote-first world?In this episode of the Distributed podcast, host Jack Hannah sits down with Nick Cash, Senior Vice President & Head of Technology at Jam City, to explore the unique challenges and opportunities of leading a hybrid team across the globe. Nick shares insights into Jam City’s hub-and-spoke organizational structure, the importance of reducing friction in communication, and the value of synchronous collaboration. He also discusses strategies for empowering engineers, fostering connections across teams, and building a culture of trust and innovation in a remote-first environment.Highlights:Jam City’s hybrid approach to remote-first work and global team dynamicsReducing friction with clear processes and effective communication toolsThe importance of synchronous collaboration for solving complex problemsBuilding connections through programs like Jam City UniversityHow fostering team relationships leads to better project outcomesIn this episode, we cover:(00:00) – Kicking Things Off With Nick Cash(04:44) – Optimizing Product Lifecycle and Team Agility(08:35) – Integrating Processes with Flexibility(12:34) – Fostering Occasional Team Interactions(14:40) – Balancing Mentorship and Independence(19:06) – Effective Team Communication Boosts Productivity(22:44) – Fostering Success at Jam City(25:44) – Leveraging Curiosity for Networking Success(27:17) – Jam City's Global Talent Strategy(32:23) – Exploring Meetings vs. Problem-Solving Calls(34:37) – Comparing In-Person and Virtual Collaboration PerceptionsWhere to connect further:Connect with Nick Cash on LinkedInMore about Jam CityFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

What happens when a fully remote team prioritizes speed, flexibility, and customer feedback?In this episode of the Distributed podcast, Host Jack Hannah talks to Sumeet Jain, Head of Engineering at Sublime Security, about how they manage one-week development cycles to stay agile and responsive to their customers’ needs. Sumeet shares how the team’s reliance on Slack and Notion streamlines workflows and minimizes friction, helping engineers stay connected even across time zones.They also discuss how making work visible, listening to customers, and maintaining a balance between speed and quality are key to Sublime’s success in a fast-paced remote environment.Highlights:Why a one-week development cycle gives Sublime a competitive edgeHow the team uses Slack and Notion to manage tasks and streamline communicationThe importance of making work visible to foster camaraderie in a remote teamHow prioritizing customer feedback drives development decisionsMaintaining speed and focus while ensuring quality in a rapid delivery environmentIn this episode, we cover:(00:00) – Kicking things off with Sumeet Jain(01:13) – Catching the software bug with a Penny Hardaway fan site(02:21) –  Running a fully remote team across North America(03:20) – Why Sublime chose one-week engineering cycles(07:00) – Inside the Monday planning ritual and company alignment(11:39) – How customer feedback drives weekly priorities(14:08) – Rethinking under promise and over deliver culture(19:02) – Principles behind Sublime’s lightweight operations(22:59) – Using emoji reactions to create tasks in Slack(28:47) – Organizing work through “T channels”(34:01) –  Sumeet’s favorite remote work gear and why air quality mattersProducts mentioned:UGMONK Analog Wood Card HolderAranet4 CO2 MonitorWhere to connect further:Connect with Sumeet Jain on LinkedInFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

How do you transition from a solo founder to leading a thriving remote team?In this episode of the Distributed podcast, Host Jack Hannah sits down with Chris Oliver, Founder of GoRails and Host of the Remote Ruby podcast, to discuss his journey from working solo to building a successful three-person remote team. Chris shares a candid look at how he overcame the challenge of scaling a business, the importance of asynchronous communication, and how he created a system that fosters remote collaboration. Highlights:Strategies for transitioning from solo work to team leadershipBalancing asynchronous and synchronous collaboration for remote teamsHow Chris built a sustainable business that works for him, not the other way aroundThe tools and processes that enable GoRails to thrive remotelyIn this episode, we cover:(00:00) – Kicking things off with Chris Oliver(00:42) – The origin of GoRails: From tutorials to product market fit(04:03) – Challenges of solopreneurship and the decision to expand(06:28) – Adapting processes for a team environment(09:27) – The value of pair programming in remote work(12:46) – Balancing asynchronous and synchronous communication(18:35) – Creating a calm company culture at GoRails(37:16) – Encouraging entrepreneurship and lessons from experienceReferenced:Railscasts by Ryan BatesMichael Gerber’s Book: The E-Myth on AmazonWhere to connect further:Connect with Chris Oliver on X and GitHubMore about GoRailsFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

Mike Bland, a Developer Experience Platform Architect at EngFlow with a rich background at Google and Apple, shares his insights on forging effective remote work cultures. He discusses the grassroots origins of Google's Testing Grouplet and the quality culture initiative from Apple, revealing how these experiences inform his strategies today. Mike emphasizes the critical role of intentional communication and the power of trust within distributed teams. He also highlights the challenges of balancing autonomy and collaboration in remote environments.

What makes hybrid and remote teams successful? In this episode of the Distributed podcast, Jack Hannah sits down with Rachel Trana, Senior Engineering Manager at Grainger, to explore strategies for thriving in flexible work environments. Rachel shares how practices like pair programming, effective status updates, and intentional onboarding can help teams stay aligned and productive. She also talks about the unique challenges of fostering communication and connection in a hybrid setup, offering practical advice for leaders and team members alike.If you’re navigating hybrid or remote work and looking for ways to make teamwork seamless, this conversation is full of tips and insights to take back to your team.Highlights:How to create effective kickoffs for hybrid and remote teamsWhy pair programming is a core practice for sharing context and building communication skillsThe importance of clear, concise status updates in daily workflowsStrategies for improving onboarding processes in evolving work environmentsIn this episode, we cover:(00:00) – Kicking Things Off with Rachel Trana(02:30) – Grainger’s Flexible Hybrid Work Approach(04:11) – The Importance of Kickoffs and Context in Team Success(08:36) – How Pair Programming Builds Communication and Technical Skills(16:22) – A Story of Success: Effective Pairing in Complex Projects(17:34) – The Role of Status Updates in Keeping Teams Aligned(22:04) – Rethinking Onboarding for Hybrid Teams(26:32) – Lessons Learned from a Heavy-Handed Approach to Process Change(31:47) – Navigating the Challenges of Isolation in Hybrid Work(33:55) – Final Takeaway: Alignment and CommunicationResources:Connect with Rachel Trana on LinkedIn More about GraingerFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

What does it take to build high-performing remote teams in a distributed world? In this episode of the Distributed podcast, host Jack Hannah chats with Carlos Rosão, Director of Software Engineering at NewStore, to uncover the strategies that make remote engineering teams thrive. Carlos shares how NewStore fosters autonomy, balances standardization with flexibility, and uses pair programming to reduce miscommunication and encourage collaboration. From prioritizing customer needs to scaling engineering practices across distributed teams, this episode offers insights for leaders and team members navigating remote work.Highlights:The balance between empowering teams and standardizing best practicesHow NewStore uses pair programming and rotation to prevent silos and enhance collaborationWhy in-person meetups still matter for distributed teamsPractical tips for improving communication and ownership in remote settingsIn this episode, we cover:(00:00) – Kicking Things Off with Carlos Rosão(05:16) – NewStore’s Approach to Distributed Work and Time Zone Collaboration(07:04) – Building Trust and Fostering Connections in Remote Teams(11:05) – Balancing Autonomy and Alignment in Team Decision-Making(19:15) – The Role of In-Person Gatherings for Onboarding and Team Cohesion(24:22) – How Customer Feedback Drives Product Innovation at NewStore(36:23) – Final Takeaway: Scaling Distributed Teams and Fostering High PerformanceWhere to connect further:Connect with Carlos Rosão on LinkedInVisit Tales of Engineering LeadershipMore about NewStoreFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

How do feedback loops shape high-performing engineering teams?In this episode of the Distributed podcast, host Jack Hannah talks with Ben Grohbiel, Staff Engineer at Snyk, about the interplay between leadership, technical excellence, and collaboration in remote teams. Ben shares his journey from running a web dev shop to leading platform teams and eventually transitioning from engineering management back to an individual contributor role.Ben also discusses the habits and rituals that help teams stay aligned, the importance of feedback loops in decision-making, and how structuring remote teams for success requires more than just good tooling—it’s about fostering the right culture.Highlights:Transitioning from engineering manager to staff engineer: what changed and whyThe role of SpeedBacks and pairing in driving continuous team improvementHow Snyk structures its remote teams for collaboration and efficiencyThe debate around remote vs. hybrid vs. in-person setups—and what really mattersNavigating autonomy and accountability in startups vs. scale-upsIn this episode, we cover:(00:00) – Kicking things off with Ben Grohbiel(03:39) – Transition from engineering management to staff engineer(04:27) – Challenges of managing a large remote team(07:10) – The importance of feedback loops in high-performing teams(10:40) – "Speedbacks": A unique approach to rapid peer feedback(14:09) – Effective communication between teams through pairing(17:17) – A startup experience where everything clicked(23:00) – The very first team experience on Snyk(27:09) – The debate around remote, hybrid, and in-office work(30:18) – Driving effective information flow in remote teams(34:14) – The future of remote work: Unanswered questionWhere to connect further:Connect with Ben Grohbiel on LinkedIn and check out SnykFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

What’s the right way to operate as a hybrid team in today’s engineering landscape? In this episode of the Distributed podcast, Jack Hannah speaks with Cassia Scheffer, Staff Software Engineer at Wealthsimple, to explore her best practices for mentoring and collaborating in a remote-first environment. Cassia shares insights on balancing hybrid work cultures, the power of pair programming, and how distributed ownership empowers engineers to make better decisions. She also reflects on the challenges of feeling disconnected in hybrid setups and how Wealthsimple prioritizes customer-focused values to align teams.Highlights:The importance of balancing hybrid work cultures to foster a sense of belongingHow schema validation enables distributed ownership and better decision-makingWhy mentoring and pair programming improve collaboration and learningStrategies for driving alignment through clear documentationThe role of curiosity in planning, problem-solving, and building strong teamsIn this episode, we cover:(00:00) – Kicking Things Off With Cassia Scheffer(00:45) – Wealthsimple’s Hybrid Model and Remote-First Approach(02:38) – Why Pair Programming is Essential for Remote Engineering(04:56) – How Wealthsimple’s 400-Person Engineering Team Stays Aligned(06:58) – Scaling Communication: From Growing Pains to Real-Time Decision Making(10:18) – A Leadership Crisis and the Culture Clash That Followed(13:48) – How Hybrid Work Creates Visibility and Belonging Challenges(19:00) – API Platform Engineering: Driving Adoption Across 30 Teams(30:42) – Coaching Engineers: Pairing as a Tool for Growth and Problem-Solving(38:52) – Final Takeaway: Curiosity as the Key to Effective CollaborationReferenced:Organizational Culture and Leadership by Edgar H. Schein: https://www.amazon.com/Organizational-Leadership-Jossey-Bass-Business-Management/dp/1119212049Where to connect further:Connect with Cassia Scheffer on LinkedInMore about Cassia on her websiteMore about WealthsimpleFollow TupleWant to hear more? Check out distributed.fmConnect with Jack Hannah

Dave Farley, a pioneering software engineer and author renowned for his expertise in continuous delivery, delves into the crucial role of human connection in software development. He champions pair programming as a key practice for boosting productivity and code quality. Farley discusses the trade-offs of remote work, emphasizing the importance of building and maintaining trust among distributed teams. He also explores AI's evolving impact on software engineering, warning against neglecting teamwork in the face of technological advancements.