<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Team on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/team/</link>
    <description>Recent content in Team on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 06 Jul 2022 09:55:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/team/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>On-Call Culture That Doesn&#39;t Burn Out Your Team</title>
      <link>https://blog.turboawesome.win/2022/07/on-call-culture-that-doesnt-burn-out-your-team/</link>
      <pubDate>Wed, 06 Jul 2022 09:55:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2022/07/on-call-culture-that-doesnt-burn-out-your-team/</guid>
      <description>On-call is a forcing function for reliability — when engineers are paged for their own systems, the feedback loop on quality is immediate. Done badly, it burns out your team. The practices that keep it sustainable.</description>
    </item>
    <item>
      <title>Hiring Senior Engineers: What the Interview Loop Can&#39;t Tell You</title>
      <link>https://blog.turboawesome.win/2021/07/hiring-senior-engineers-what-the-interview-loop-cant-tell-you/</link>
      <pubDate>Wed, 07 Jul 2021 14:02:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2021/07/hiring-senior-engineers-what-the-interview-loop-cant-tell-you/</guid>
      <description>After running hiring loops for senior engineers at the European fintech firm, the pattern was clear: the things that determined whether a hire was successful were almost never well-measured by our interview process.</description>
    </item>
    <item>
      <title>Writing Technical RFCs That Actually Get Read</title>
      <link>https://blog.turboawesome.win/2021/02/writing-technical-rfcs-that-actually-get-read/</link>
      <pubDate>Wed, 24 Feb 2021 09:07:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2021/02/writing-technical-rfcs-that-actually-get-read/</guid>
      <description>Most technical RFCs fail at their primary purpose: creating alignment before building. The failures are almost always structural — missing context, buried decisions, or no clear ask. Here&amp;#39;s the format that worked.</description>
    </item>
    <item>
      <title>Engineering Velocity at a Startup: What Actually Made Us Fast</title>
      <link>https://blog.turboawesome.win/2021/02/engineering-velocity-at-a-startup-what-actually-made-us-fast/</link>
      <pubDate>Tue, 09 Feb 2021 13:41:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2021/02/engineering-velocity-at-a-startup-what-actually-made-us-fast/</guid>
      <description>After two years at a fast-moving fintech startup, the things that actually determined how quickly we shipped were not the tools or the process — they were much simpler and harder to fix than that.</description>
    </item>
    <item>
      <title>From IC to Lead: The First 90 Days Managing a Technical Team</title>
      <link>https://blog.turboawesome.win/2020/05/from-ic-to-lead-the-first-90-days-managing-a-technical-team/</link>
      <pubDate>Wed, 13 May 2020 13:44:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2020/05/from-ic-to-lead-the-first-90-days-managing-a-technical-team/</guid>
      <description>The transition from individual contributor to technical lead is the career move that most engineers underestimate. The skills that made you good at the IC role don&amp;#39;t automatically transfer — here&amp;#39;s what the first 90 days actually taught me.</description>
    </item>
  </channel>
</rss>
