<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>automaticdev.team</title>
    <link>https://automaticdev.team/</link>
    <description>Recent content on automaticdev.team</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 26 Apr 2026 14:57:13 -0400</lastBuildDate>
    <atom:link href="https://automaticdev.team/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>When Will I Be a Senior Engineer?</title>
      <link>https://automaticdev.team/people/senior-engineer/</link>
      <pubDate>Sun, 26 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://automaticdev.team/people/senior-engineer/</guid>
      <description>&lt;p&gt;Rather than time spent or indvidiual experiences, I go back to the &lt;a href=&#34;https://automaticdev.team/people/knowledge-skills-behaviors/&#34;&gt;knowledge, skills, and behavior&lt;/a&gt;   of a senior engineer. Not only what you know, but how you show up for your team.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Bare Metal Agile</title>
      <link>https://automaticdev.team/process/bare-metal-agile/</link>
      <pubDate>Sun, 26 Apr 2026 14:57:13 -0400</pubDate>
      <guid>https://automaticdev.team/process/bare-metal-agile/</guid>
      <description>&lt;p&gt;A simplified take on development process that prioritizes predictability, flexibility and delievering end-user value.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Steering Committee</title>
      <link>https://automaticdev.team/process/steering-committee/</link>
      <pubDate>Sun, 26 Apr 2026 14:57:13 -0400</pubDate>
      <guid>https://automaticdev.team/process/steering-committee/</guid>
      <description>&lt;p&gt;A lightweight steering committee can give product and engineering teams a practical way to create transparency, align priorities, and make capacity tradeoffs without turning planning into a heavyweight governance exercise.&lt;/p&gt;&#xA;&lt;p&gt;The goal is not to relitigate every prior commitment. The goal is to review current objectives, inspect the delivery pipeline, and decide what should move next based on value, readiness, and available capacity.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Knowledge, Skills, Behavior</title>
      <link>https://automaticdev.team/people/knowledge-skills-behaviors/</link>
      <pubDate>Tue, 16 Dec 2025 00:00:00 +0000</pubDate>
      <guid>https://automaticdev.team/people/knowledge-skills-behaviors/</guid>
      <description>&lt;p&gt;Engineering roles should have a well understood definition of what should be known, tasks to be accomplished, and expections of how you show up day to day for your team.&lt;/p&gt;&#xA;&lt;p&gt;This following is a high level list of things that every &lt;strong&gt;Entry Level Engineer&lt;/strong&gt; should strive for.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Engineering Organization Accountability</title>
      <link>https://automaticdev.team/people/engineering-org-accountability/</link>
      <pubDate>Fri, 28 Nov 2025 00:00:00 +0000</pubDate>
      <guid>https://automaticdev.team/people/engineering-org-accountability/</guid>
      <description>&lt;p&gt;Clear accountability is what keeps an engineering organization aligned as it grows. Roles do not need to be rigid, but they do need clear ownership boundaries so strategy, delivery, architecture, and people leadership are all consistently covered.&lt;/p&gt;&#xA;&lt;p&gt;This model separates organizational leadership, delivery execution, and technical leadership into distinct responsibilities. That separation reduces ambiguity and makes coordination easier across engineering, product, and other partner teams.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Director of Product Engineering</title>
      <link>https://automaticdev.team/people/director-of-engineering/</link>
      <pubDate>Sun, 07 Jan 2024 00:00:00 +0000</pubDate>
      <guid>https://automaticdev.team/people/director-of-engineering/</guid>
      <description>&lt;p&gt;Below is a real job posting for a Director of Product Engineering. It was used it as a reference while constructing a job posting for a similar role at my company.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Engineering Manager</title>
      <link>https://automaticdev.team/people/engineering-manager/</link>
      <pubDate>Thu, 28 Dec 2023 00:00:00 +0000</pubDate>
      <guid>https://automaticdev.team/people/engineering-manager/</guid>
      <description>&lt;p&gt;A engineering manager is accountable for building a software delivery organization that is efficient, predictable, and high quality. The role also carries responsibility for helping create a production environment that is secure, reliable, and scalable.&lt;/p&gt;&#xA;&lt;p&gt;This is not just a people-management role. It sits at the intersection of delivery systems, engineering culture, technical enablement, and organizational execution.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Engineer Onboarding</title>
      <link>https://automaticdev.team/process/engineer-onboarding/</link>
      <pubDate>Mon, 12 Jun 2023 00:00:00 +0000</pubDate>
      <guid>https://automaticdev.team/process/engineer-onboarding/</guid>
      <description>&lt;p&gt;The following is based on an actual template used to onboard fully remote software developers. Names have been changed to protect the guilty.😀&lt;/p&gt;</description>
    </item>
    <item>
      <title>About</title>
      <link>https://automaticdev.team/about/</link>
      <pubDate>Sun, 21 Jul 2019 12:59:08 -0400</pubDate>
      <guid>https://automaticdev.team/about/</guid>
      <description>&lt;p&gt;My name is &lt;a href=&#34;https://brianwaustin.com/&#34;&gt;Brian Austin&lt;/a&gt; and I am an Engineering Manager  leading high-performing remote, distributed software engineering teams.&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;“Engineering without cruft”&lt;/em&gt; is my commitment to removing waste in how we plan, build, and operate software, while preserving the rigor that keeps systems reliable.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;My goal as an engineering manager:&lt;/strong&gt; build teams where people can do their best work, where processes help rather than hinder, and where platforms make shipping high‑quality software the natural outcome of everyday practice.&lt;/p&gt;&#xA;&lt;p&gt;I believe that the most successful teams are built with a relentless focus on three core areas: &lt;strong&gt;People&lt;/strong&gt;, &lt;strong&gt;Process&lt;/strong&gt; and &lt;strong&gt;Platform&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
