Interact: A Word From Your Co-Hosts

In the last few years, disengagement at work has become a massive issue. We learned from Dr. Andre Martin’s episode that 53% of managers are burnt out and 1 in 3 employees leave their jobs in the first 90 days.This week, we sat down with Chuck Lafferty, VP of CRM at ADP, to discuss ADP’s approach to employee engagement and innovation. Chuck dives into building trust within teams, innovative techniques like ‘Survey Roulette’ to incorporate user feedback into development, and the critical role of understanding and caring for individuals.When employees feel valued, heard, and engaged in meaningful work, you see improved productivity and increased job satisfaction. The episode concludes with actionable steps to improve employee engagement through personalized interactions and empathetic leadership.Episode Highlights:01:51 How does Chuck define employee engagement?04:06 Can you measure employee engagement?12:05 How can managers engage individual developers?17:16 Survey Roulette and how it helps engage engineering teams.22:31 Winning in the workplace 23:45 The importance of separating the problem from the person25:30 How can you improve employee engagement?Show Notes:Starting Your Engineering Metrics Program Workshop Chuck LaffertyPayroll, HR and Tax Services | ADP Official SiteConfident CoderChuckLafferty (@ChuckLafferty) / XSupport the show: Subscribe to our Substack Leave us a review Subscribe on YouTube Follow us on Twitter or LinkedIn Offers: Learn about Continuous Merge with gitStream Get your DORA Metrics free forever

This week, our host Dan Lines sits down with Tara Hernandez, VP of Developer Productivity at MongoDB. Together, they explore the nuances of developer productivity and the impact of AI in engineering environments.Tara emphasizes that achieving developer productivity requires a focus on outcomes, reduced noise for developers, and a healthy balance between technology, processes, and communication. She also touches on the strategic framework of the 'three horizons' for conceptualizing your investment breakdown across different projects and how to maintain focused on meaningful development work.Episode Highlights:01:43 How should you think about developer productivity?09:09 Three pillars to improve developer productivity16:07 Automated does not equal autonomous24:46 Making the golden path the easy path for developers27:51 What’s exciting in developer productivity and AI?29:57 The three horizons38:34 Developer performance vs productivity data40:23 What is the right way to think about goal setting for noise reduction?Show Notes:Starting Your Engineering Metrics Program Workshop Tara HernandezMongoDBGitHubCloudBeesCircleCIAtlassianEvergreen CI in GitHubSupport the show: Subscribe to our Substack Leave us a review Subscribe on YouTube Follow us on Twitter or LinkedIn Offers: Learn about Continuous Merge with gitStream Get your DORA Metrics free forever

In the past year, ransomware attacks have been up almost 300%, with over 50% targeting small businesses. To help mitigate this increase, Microsoft is launching their new Security Copilot, and we sat down with their SMB Security Strategy Head, Binil Pillai, to learn more.We dive into the importance of SMBs assessing their security posture, how to leverage AI for efficient threat detection and response, and the role of Microsoft's partner ecosystem in providing comprehensive security solutions. The episode concludes with advice for SMB leaders on starting their security assessments and the benefits of integrating AI into their cybersecurity strategies.Episode Highlights:01:39 Why is SMB security a priority for Microsoft?07:34 Key security challenges for SMBs 09:26 How can SMBs leverage AI within security?16:28 How VPs of Engineering can use new tech to deal with threats20:25 Microsoft Security Copilot 24:30 Where is the best place to learn about Microsoft's security strategy?Show Notes:Microsoft Copilot for Security is generally available on April 1, 2024 | Microsoft Security BlogMicrosoft Copilot for Security: General Availability details - Microsoft Community HubMicrosoft 365 Business Premium | Microsoft 365Microsoft Defender for Business | Microsoft SecurityAutomatic attack disruption in Microsoft 365 Defender | Microsoft LearnMicrosoft Defender for Cloud | Microsoft SecurityWhat is Microsoft Defender for Cloud? - Microsoft Defender for Cloud | Microsoft LearnSolution Assessment Program (microsoft.com)Support the show: Subscribe to our Substack Leave us a review Subscribe on YouTube Follow us on Twitter or LinkedIn Offers: Learn about Continuous Merge with gitStream Get your DORA Metrics free forever

In this episode, host Conor Bronsdon talks with Melissa DePuydt, Sr. Director of Engineering at Upstatement. Melissa discusses how her background in journalism has uniquely positioned her to excel in engineering leadership roles. She highlights how thinking like a journalist has enhanced her ability to lead engineering teams effectively, particularly in planning, risk management, and decision-making.The conversation covers the importance of preparing for disruptions, conducting pre-mortems to anticipate challenges, and incorporating broad perspectives for effective problem solving. Melissa also shares insights on continuously learning and adapting by embracing one's unique background and experiences.Episode Highlights:00:20 Why do engineering leaders need to think like journalists?04:46 Preparing for disruptions as an engineering leader08:44 How pre-mortems work in practice: an example from the Atlantic12:47 How to get buy in from other leaders when changing processes 17:59 Eliciting buy-in from team members on pre-mortems22:15 How do we train engineers to think in a team sport mentality?26:51 Why is career switching a superpower?Show Notes:Melissa DePuydtUpstatement | A digital brand and product design studioSupport the show: Subscribe to our Substack Leave us a review Subscribe on YouTube Follow us on Twitter or LinkedIn Offers: Learn about Continuous Merge with gitStream Get your DORA Metrics free forever

On this week’s episode, host Conor Bronsdon sits down with Emily Nakashima, VP of Engineering at Honeycomb.io, to discuss how you can prepare to be a VP of Engineering, and how the role differs among companies. Being a VPE varies based on company size, culture, and the existing team's makeup, and Emily provides valuable advice for engineers aspiring to leadership positions.Emily also discusses using personality tests for better team dynamics and the need for regular self-evaluation as an integral part of career advancement. The conversation closes by talking about the impact of AI on the workforce, the importance of aligning engineering and business goals, and the potential of AI to enhance rather than replace human skills.Episode Highlights:01:27 Why does Emily think there isn't a standard VP of Engineering role?06:29 The archetypes of the VPE role10:15 How does the VPE role change as an organization grows?14:46 Preparing to become a VP of Engineering before you get the role20:11 How you can use personality tests in organizational design26:00 How is the VP of Engineering role changing in 2024?30:53 Teams are having to accept realities about production software with regards to AIShow Notes:Modern Practices for Goal Setting in Software Engineering Emily NakashimaEmily Nakashima (@eanakashima.bsky.social) — BlueskyObservability for Distributed Services | HoneycombStrengthsFinder 2.0 | EN - GallSupport the show: Subscribe to our Substack Leave us a review Subscribe on YouTube Follow us on Twitter or LinkedIn Offers: Learn about Continuous Merge with gitStream Get your DORA Metrics free forever

This week, host Conor Bronsdon welcomes back Kelly Vaughn, Director of Engineering at Spot AI, to talk about building influence as an engineering leader. Kelly shares insights on the importance of leadership skills for both individual contributor and managerial roles and outlines her three pillars of trust, communication, and empowerment. Conor and Kelly discuss strategies for staying technically fresh despite moving up in management, exploring the balance between staying close to product development and avoiding micromanagement. Lastly, they touch on the potential of AR/VR technology, with a focus on the business implications of Apple's Vision Pro and the future of immersive experiences.Episode Highlights:01:09 How should engineering leaders think about building influence?03:53 The impact of changing roles or companies on your performance 08:07 Why you lose important context when making assumptions09:32 How ICs can help manage their team10:49 Key ways to build influence and trust16:00 How important is trust when giving or recieving feedback?22:27 How do leaders stay close to their product as their org grows?28:58 Our thoughts on Apple Vision Pro and AR VR in generalShow Notes:Kelly VaughnLessons in Engineering Leadership | Kelly Vaughn | SubstackSpot AI: Video Intelligence for Better Decision-MakingRadical Candor | Feedback Training, Coaching & ConsultingSupport the show: Subscribe to our Substack Leave us a review Subscribe on YouTube Follow us on Twitter or LinkedIn Offers: Learn about Continuous Merge with gitStream Get your DORA Metrics free forever

On this week’s episode, host Conor Bronsdon is joined by Jason Krohn, Global Head of Delivery at Syngenta. Jason delves into how his teams at Syngenta leverage software engineering intelligence to achieve predictable delivery at scale. Jason also explores how aligning work with employees' passions contributes to success and retention at Syngenta. He discusses the challenges and solutions in implementing efficient DevOps processes and ensuring organizational buy-in for the vision. Additionally, Jason highlights the importance of empowering teams with autonomy and providing the necessary tools for proactive decision-making.Whether you're leading a small team or managing an enterprise, Jason's insights offer valuable lessons on driving efficiency, scaling effectively, and fostering a culture of continuous improvement.Episode Highlights: 1:46 Scaling teams that are empowered and autonomous 4:01: The four pillars for retaining talent in tech teams.12:51 Tackling organizational change 18:41 Using metrics to achieve predictable delivery 21:45 Why your engineering teams' need to care about metrics, not just be compliant 26:20 Addressing production delays and DevOps integration28:55 Leadership's role in communicating the 'why’33:05 The Importance of Coaching When Mentoring Show Notes:SyngentaJason KrohnSupport the show: Subscribe to our Substack Leave us a review Subscribe on YouTube Follow us on Twitter or LinkedIn Offers: Learn about Continuous Merge with gitStream Get your DORA Metrics free forever

This week, host Dan Lines welcomes back Zach Goldberg, CTO and author of the book 'The Startup CTO's Handbook: Essential Skills and Best Practices for High Performing Engineering Teams.’ Zach shares insights from his extensive career as a CTO and his journey in writing a book that condenses the wisdom of numerous other influential works into a single, comprehensive guide.We explore the three core sections of his book:Management Fundamentals: Interviewing, Hiring, Performance Management, Budgeting, etc. Technical Leadership Concepts: Developer Experience, Tech Debt, etc. Hard Technology Decisions: Pragmatism, Tech Stack, etc.Zach provides advice for not only CTOs but anyone in a technical leadership position, offering strategies to develop empathy and understanding within technical organizations.Episode Highlights: 1:59 From Startup CTO to Author and Executive Coach3:41 The Origin of Best Practices and Genesis of the Handbook  10:25 Why the Startup CTO’s Handbook isn’t just for CTOs 13:02 Part 1: Management Fundamentals Beyond Coding24:50 Part 2: Technical Leadership Concepts & Developer Experience30:57 Part 3: Technology Decisions from a Pragmatic PerspectiveShow Notes:The Startup CTO's Handbook: Essential skills and best practices for high performing engineering teamsSupport the show: Subscribe to our Substack Leave us a review Subscribe on YouTube Follow us on Twitter or LinkedIn Offers: Learn about Continuous Merge with gitStream Get your DORA Metrics free forever

It doesn’t matter if you have an innovative technical strategy if you’re not solving problems the business cares about… This week, host Conor Bronsdon sits down with Rob Zuber, CTO at CircleCI. They delve into the evolving role of engineering leaders, and the importance of building a technical strategy that aligns with overarching business goals.Throughout the conversation, Rob emphasizes the importance of focusing on customer needs, gathering direct feedback and maintaining strategic flexibility. If you’re interested in understanding the balance between technical strategy and business leadership, this episode provides a wealth of knowledge, strategies, and real-world examples.Episode Highlights:01:38 Crafting technical strategy for teams at CircleCI 07:26 How engineering leaders can make the most informed choices about their business17:47 Using postmortems to fuel a growth mindset 22:39 Applying hypotheses to be prepared for worst-case scenarios 27:43 Why CTOs need to focus on solving business problems first, then technical strategy30:30 Why engineering leaders need to form a close relationship with finance33:17 Advice for ICs or Directors on becoming a business leader39:17 Rob's approach to building trust and organizational design 44:36 How can I prepare for being a technical founder?55:12 What is CircleCI doing in ML?Show Notes:Modern Software EngineeringSupport the show: Subscribe to our Substack Leave us a review Subscribe on YouTube Follow us on Twitter or LinkedIn Offers: Learn about Continuous Merge with gitStream Get your DORA Metrics free forever

On this week’s episode, host Conor Bronsdon sit down with Guilherme Sesterheim, SAP DevOps SRE Engineer at AWS. Guilherme delves into applying Chaos Engineering and DevOps principles to SAP, a domain traditionally seen as risk-averse and resistant to rapid innovation.With expertise in both open-source technologies and SAP, Guilherme shares how he’s bringing modern practices to SAP environments at AWS. He explores how Chaos Engineering can be used to test and improve the resilience of SAP systems, focusing on HANA, SAP’s in-memory database. The discussion also touches on the challenges of integrating these practices within the SAP framework and the broader implications for SAP users and the tech industry.Episode Highlights:00:20 What does it mean to apply chaos engineering to testing SAP installation04:05 What does it mean to have DevOps around SAP?05:58 Guilherme’s approach to DevOps practices around SAP10:01 The challenge of handling installation and migration11:50 How to Start Applying Chaos Engineering to Your SAP Instance16:57 The 12 Scenarios When You Inject Failures on SAP19:24 How Guilherme ended up at AWS working on SAP23:14 What’s Next in DevOps Guilherme is Excited About?Show Notes:Wiring the Winning Organization - IT RevolutionSupport the show: Subscribe to our Substack Leave us a review Subscribe on YouTube Follow us on Twitter or LinkedIn Offers: Learn about Continuous Merge with gitStream Get your DORA Metrics free forever