Head Of Engineering At Sublime Security On Development Cycles, Process, And Tooling With Sumeet Jain Distributed. podcast

35:02

In this latest episode of the Distributed podcast, host Jack Hannah interviews Colin Sidoti, Clerk Cofounder & CEO, to discuss what’s allowed them to grow so rapidly and deliver such an incredible developer experience for users. Colin reflects on how limited process fosters growth and allows his team of engineers and designers to excel. Colin also provides insight into the nontraditional ways Clerk streamlines work, including their hiring practices and unique team dynamics. Highlights: Understanding how Clerk has grown through a highly autonomous team culture Colin's insights on the importance of fluid communication in a distributed team The pivotal role the DX Guide plays in creating an amazing product Empowering teams by trusting their instincts and encouraging adaptability In this episode, we cover: (00:00) – Kicking things off with Colin Sidoti (03:26) – Product development at Clerk (08:29) – Remote work dynamics: synchronizing across time zones (12:54) – Importance of fluid communication: using Tuple for efficient syncs (14:44) – The role of DX Guide: maintaining high standards in product experience (22:28) – Building a culture of customer-centric development (17:40) – Evolving product offerings: from auth to billing and beyond (25:56) – Hiring for passion: finding team members who care deeply (31:55) – Simplifying user onboarding: eliminating friction for developers (33:34) – Impact of removing friction: boosting adoption with minimal steps Where to connect further: Connect with Colin Sidoti on X and Clerk Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah…

1
Principal Engineer at John Deere on how extreme programming saved his startup 40:57

9 days ago40:57

40:57

Engineering teams whose work leaves an impact thrive on trust, collaboration, and the appropriate technical practices. In this episode of the Distributed podcast, host Jack Hannah sits down with Ryan Bergman, Principal Engineer at John Deere, to explore the impact of Extreme Programming (XP) and agile practices on software development. Ryan shares how XP principles helped stabilize a struggling startup, why pair programming is essential for team cohesion, and how behavior-driven development (BDD) builds confidence in large-scale systems. They also discuss the challenges of remote collaboration, lessons from scaling software at John Deere, and what it takes to align distributed teams around a shared technical vision. Highlights: Rescuing a struggling startup by embracing Extreme Programming to improve collaboration, code quality, and technical execution Strengthening engineering teams with pair programming and the right balance of structure and flexibility Managing large-scale software development at John Deere Building trust across distributed teams through clear communication, shared technical vision, and an emphasis on psychological safety Using Behavior-Driven Development (BDD) to create reliable, well-tested systems that give teams confidence in their software In this episode, we cover: (00:00) – Kicking Things Off with Ryan Bergman (01:10) – Ryan’s Journey: From Graphic Arts to Engineering (03:59) – Discovering XP: How Extreme Programming Saved a Startup (08:09) – Pair Programming and Agile Coaching: Rebuilding from the Ground Up (14:14) – Navigating Large-Scale Systems at John Deere (16:22) – The Power of Trust: Autonomy, Collaboration, and ‘Vampire Rules’ (21:37) – Building Strong Engineering Teams Through Open Knowledge Sharing (26:49) – Pair Programming Pitfalls: Fixing What Doesn’t Work (37:11) – Behavior-Driven Development: Creating Confidence in Complex Systems Where to connect further: Connect with Ryan Bergman on LinkedIn and check out John Deere Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah…

1
Founder & CEO of DNSimple on bootstrapping and embracing async with Anthony Eden 39:56

16 days ago39:56

39:56

Anthony Eden started DNSimple as a remote first, mostly asynchronous company in 2010 before it was cool. In this episode of the Distributed podcast, host Jack Hannah sits down with Anthony, Founder and CEO, to discuss the intricacies of remote-first companies. Anthony shares his journey of building DNSimple as a remote-first company, highlighting how asynchronous communication and flexible structures foster a thriving tech culture. The discussion touches on what shapes a successful organization and the challenges he’s faced over the years. Anthony also shares his experience with Shape Up and how it’s improved his team’s productivity and trust in each other. Highlights: Remote work norms and fostering collaboration across different time zones Anthony’s journey with Shape Up How to facilitate trust among team members DNSimple’s culture of collaboration In this episode, we cover: (00:00) - Kicking things off with Anthony Eden (00:55) - Founding DNSimple: Anthony’s journey to remote work (02:47) - Embracing remote work: the time zone challenge (04:02) - Company growth and team structure at DNSimple (06:56) - The shift to Shape Up: solving development challenges (10:42) - Facilitating trust and commitments in remote teams (16:06) - Asynchronous collaboration tools (21:45) - Aligning remote work practices: learning from experiments (31:20) - The human side of remote work: building emotional connections (35:43) - Conclusion: looking ahead with a growth mindset in remote work References mentioned: DNSimple’s time tracking experiment Shape Up Where to connect further: Connect with Anthony Eden on LinkedIn Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah…

1
Spotify engineer on the role of trust with Pavel Hubich 39:26

23 days ago39:26

39:26

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 continents Why hybrid work can unintentionally create communication bubbles—and how teams can bridge the gaps The role of standups, casual rituals, and structured collaboration in building trust remotely Using mob programming and Architecture Golf to reduce context switching and improve team alignment Finding a balance between focus, flexibility, and human connection in a remote-first world In 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 out Where to connect further: Connect with Pavel Hubich on LinkedIn Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah…

1
Building global teams, connections, and culture with Nick Cash from Jam City 35:51

4 weeks ago35:51

35:51

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 dynamics Reducing friction with clear processes and effective communication tools The importance of synchronous collaboration for solving complex problems Building connections through programs like Jam City University How fostering team relationships leads to better project outcomes In 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 Perceptions Where to connect further: Connect with Nick Cash on LinkedIn More about Jam City Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah…

1
Head of Engineering at Sublime Security on development cycles, process, and tooling with Sumeet Jain 37:07

5 weeks ago37:07

37:07

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 edge How the team uses Slack and Notion to manage tasks and streamline communication The importance of making work visible to foster camaraderie in a remote team How prioritizing customer feedback drives development decisions Maintaining speed and focus while ensuring quality in a rapid delivery environment In 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 matters Products mentioned: UGMONK Analog Wood Card Holder Aranet4 CO2 Monitor Where to connect further: Connect with Sumeet Jain on LinkedIn Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah…

1
Chris Oliver on bootstrapping GoRails and building remote teams 43:01

6 weeks ago43:01

43:01

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 leadership Balancing asynchronous and synchronous collaboration for remote teams How Chris built a sustainable business that works for him, not the other way around The tools and processes that enable GoRails to thrive remotely In 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 experience Referenced: Railscasts by Ryan Bates Michael Gerber’s Book: The E-Myth on Amazon Where to connect further: Connect with Chris Oliver on X and GitHub More about GoRails Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah…

1
How former Apple and Google senior engineer thinks about code quality & remote work with Mike Bland 46:58

7 weeks ago46:58

46:58

How do grassroots efforts drive big changes in the world of remote work? In this episode of the Distributed podcast, Jack Hannah sits down with Mike Bland, Developer Experience Platform Architect at EngFlow, to discuss his journey from Google and Apple to leading remote teams. Mike shares insights from his time running Testing Grouplet at Google, starting the Quality Culture Initiative at Apple, and how those experiences shape his approach to building effective remote teams today. From fostering grassroots initiatives to using intentional communication to build trust, Mike highlights the tools and strategies that enable distributed teams to thrive. Highlights: Lessons from Google’s Testing Grouplet and Apple’s Quality Culture Initiative The importance of intentional communication in remote work Using forums, training, and shared goals to align distributed teams In this episode, we cover: (00:00) – Kicking Things Off with Mike Bland (02:30) – What Is Testing Grouplet? A Story of Change at Google (08:55) – Lessons Learned from Apple’s Quality Culture Initiative (16:43) – Building Grassroots Communities to Drive Cultural Change (17:54) – Key Challenges for Scaling Communication at EngFlow (22:36) – Creating Effective Synchronous and Asynchronous Touchpoints (30:52) – Using Code Reviews to Build Trust in Distributed Teams (37:11) – Balancing Autonomy and Collaboration for Engineers (45:19) – Final Takeaway: Communication and Remote Work Resources: The Rainbow of Death: https://mike-bland.com/the-rainbow-of-death Essentialism by Greg McKeown: https://gregmckeown.com/books/essentialism/ Grouplets: https://mike-bland.com/2011/09/20/grouplets.html Where to connect further: Connect with Mike Bland on LinkedIn and his website More about EngFlow Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah…

1
How Fortune 500 Engineering Manager approaches hybrid work with Rachel Trana from Grainger 35:22

8 weeks ago35:22

35:22

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 teams Why pair programming is a core practice for sharing context and building communication skills The importance of clear, concise status updates in daily workflows Strategies for improving onboarding processes in evolving work environments In 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 Communication Resources: Connect with Rachel Trana on LinkedIn More about Grainger Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah…

1
Creating high-performing remote engineering teams with Carlos Rosão from NewStore 41:47

9 weeks ago41:47

41:47

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 Rosã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 practices How NewStore uses pair programming and rotation to prevent silos and enhance collaboration Why in-person meetups still matter for distributed teams Practical tips for improving communication and ownership in remote settings In this episode, we cover: (00:00) – Kicking Things Off with Carlos Rosã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 Performance Where to connect further: Connect with Carlos Rosão on LinkedIn Visit Tales of Engineering Leadership More about NewStore Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah…

1
How Snyk Staff Engineer thinks about scaling remote teams, leadership, and rituals with Ben Grohbiel 36:11

10 weeks ago36:11

36:11

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 why The role of SpeedBacks and pairing in driving continuous team improvement How Snyk structures its remote teams for collaboration and efficiency The debate around remote vs. hybrid vs. in-person setups—and what really matters Navigating autonomy and accountability in startups vs. scale-ups In 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 question Where to connect further: Connect with Ben Grohbiel on LinkedIn and check out Snyk Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah…

1
How staff engineers approach leading remote teams with Cassia Scheffer from Wealthsimple 39:49

11 weeks ago39:49

39:49

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 belonging How schema validation enables distributed ownership and better decision-making Why mentoring and pair programming improve collaboration and learning Strategies for driving alignment through clear documentation The role of curiosity in planning, problem-solving, and building strong teams In 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 Collaboration Referenced: Organizational Culture and Leadership by Edgar H. Schein: https://www.amazon.com/Organizational-Leadership-Jossey-Bass-Business-Management/dp/1119212049 Where to connect further: Connect with Cassia Scheffer on LinkedIn More about Cassia on her website More about Wealthsimple Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah…

1
Dave Farley on remote work, AI, and the future of software engineering 44:59

12 weeks ago44:59

44:59

How does human connection shape the way we build software? In this episode of the Distributed podcast, host Jack Hannah talks with Dave Farley, renowned software engineer, author, and expert in modern software development. Dave shares insights from his 40-year career, covering everything from extreme programming to the role of AI in software engineering. He explains why pair programming is one of the most underrated practices and how fostering trust in remote teams leads to better collaboration and creativity. Dave also explores the trade-offs of remote and hybrid work, the importance of high-quality engineering practices, and why continuous delivery remains essential for building world-class software. Highlights: Why software development is a team game and not a solo endeavor How pair programming boosts productivity and code quality Lessons from ThoughtWorks on scaling extreme programming with large teams The evolving impact of AI on software engineering How remote teams can not only build trust but maintain it In this episode, we cover: (00:00) – Kicking Things Off with Dave Farley (01:33) – Dave Farley’s Path From Early Computing to Today (05:42) – Leading a Distributed Team: First Remote Experience (07:58) – Solving Remote Work Challenges Through Human Connection (11:46) – Building Trust: The Key to Strong Software Teams (15:55) – Pair Programming: The Secret to Better Collaboration (18:55) – Overcoming Resistance to Pair Programming in Teams (28:35) – How AI Is Changing Software Development Forever (36:29) – Test-Driven Development as the Future of AI Coding (40:06) – The Biggest Challenge of Remote Work: New Teams (43:14) – Finding the Right Balance Between Remote and Office Where to connect further: Connect with Dave Farley on LinkedIn and his website Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah…

1
Valentina Servile, Thoughtworks Lead Developer, on how to win remote work 40:07

13 weeks ago40:07

40:07

How do you foster collaboration and trust in distributed engineering teams? In this episode of the Distributed podcast, Jack Hannah talks with Valentina Servile, Lead Software Developer at Thoughtworks and author of Continuous Deployment. Valentina shares how her teams leverage practices like pair programming, collective code ownership, and streamlined processes to succeed in a remote-first world. They also discuss managing cognitive load, communicating effectively across time zones, and her strategies for replacing outdated practices like pull requests with more dynamic approaches. Highlights: Why pair programming improves team dynamics and code quality The role of trust and alignment in distributed teams Automating quality gates for faster, safer workflows How to foster collective code ownership in remote teams In this episode, we cover: (00:00) – Kicking Things Off with Valentina Servile (01:59) – The Realities of Remote Work at Thoughtworks (02:13) – How Kickoffs Build Trust and Clarity in Remote Teams (04:22) – Structuring In-Person Meetings for Maximum Impact (08:20) – Effective Communication Between Distributed Teams (12:00) – A Cautionary Tale: When Remote Work Fails (16:02) – Pair Programming as a Management and Productivity Tool (21:55) – Why Collective Code Ownership Improves Team Performance (26:13) – Rethinking PR Reviews: Avoiding Bottlenecks in Remote Development (38:41) – The Struggle to Disconnect: Managing Notifications and Overload Referenced: Lean Inception by Paulo Caroli: https://caroli.org/en/livro/lean-inception-how-to-align-people-and-build-the-right-product/ Where to connect further: Connect with Valentina on LinkedIn Check out Valentina’s book, Continuous Deployment Email Valentina at valentina.servile@gmail.com More about Thoughtworks Follow Tuple Want to hear more? Check out distributed.fm Connect with Jack Hannah…

1
Kent Beck on why software development is an exercise in human relationships 50:05

14 weeks ago50:05