<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Training / Certification - Podcasts</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Training / Certification Podcasts feed</description>
    <item>
      <title>Podcast: Building Engineering Culture Through Autonomy and Ownership</title>
      <link>https://www.infoq.com/podcasts/engineering-culture-autonomy-ownership/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Training+%2F+Certification-podcasts</link>
      <description>&lt;img src="https://res.infoq.com/podcasts/engineering-culture-autonomy-ownership/en/smallimage/engineering-culture-podcast-thumbnail-500x500-1759219964258.jpg"/&gt;&lt;p&gt;In this podcast Shane Hastie, Lead Editor for Culture &amp; Methods spoke to Marcos Arribas about building and scaling engineering culture as an organisation grows, emphasizing autonomous teams, ownership mentality, progressive feature rollouts with flags, small pull requests, strategic AI adoption, and the importance of hiring junior engineers for long-term organizational growth.&lt;/p&gt; &lt;i&gt;By Marcos Arribas&lt;/i&gt;</description>
      <category>Teamwork</category>
      <category>Culture</category>
      <category>Training / Certification</category>
      <category>Engineering Culture Podcast</category>
      <category>Quality</category>
      <category>Productivity</category>
      <category>Culture &amp; Methods</category>
      <category>podcast</category>
      <pubDate>Fri, 03 Oct 2025 09:05:00 GMT</pubDate>
      <guid>https://www.infoq.com/podcasts/engineering-culture-autonomy-ownership/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Training+%2F+Certification-podcasts</guid>
      <dc:creator>Marcos Arribas</dc:creator>
      <dc:date>2025-10-03T09:05:00Z</dc:date>
      <dc:identifier>/podcasts/engineering-culture-autonomy-ownership/en</dc:identifier>
    </item>
  </channel>
</rss>
