<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Leadership on Kianoosh's Blog</title><link>https://kianoosh.dev/tags/leadership/</link><description>Recent content in Leadership on Kianoosh's Blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 08 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://kianoosh.dev/tags/leadership/index.xml" rel="self" type="application/rss+xml"/><item><title>Being a good leader: Static definition or a moving target?</title><link>https://kianoosh.dev/posts/2026-01-08-being-a-good-leader-static-definition-or-a-moving-target/</link><pubDate>Thu, 08 Jan 2026 00:00:00 +0000</pubDate><guid>https://kianoosh.dev/posts/2026-01-08-being-a-good-leader-static-definition-or-a-moving-target/</guid><description>&lt;p>In this blog post, Will Larson shares his retrospective on how the definition of a good leader has evolved over his time in the industry. He categorizes his observations into three eras:&lt;/p>
&lt;p>#️⃣ &lt;strong>Late 2000s&lt;/strong>: Leaders were straightforward. They didn’t organize regular 1:1 meetings but focused on identifying and removing obstacles for their teams.&lt;/p>
&lt;p>#️⃣ &lt;strong>2010s&lt;/strong>: With business budgets essentially unlimited, companies focused on hiring as many engineers as possible. The main goal was to attract and retain top engineering talent. Engineering managers were expected to stop coding from day one and instead focus entirely on recruitment, retention, and motivation.&lt;/p></description></item><item><title>The Long Game: Surviving the Forty-Year Career</title><link>https://kianoosh.dev/posts/2025-12-30-the-long-game-surviving-the-forty-year-career/</link><pubDate>Tue, 30 Dec 2025 00:00:00 +0000</pubDate><guid>https://kianoosh.dev/posts/2025-12-30-the-long-game-surviving-the-forty-year-career/</guid><description>&lt;h2 id="the-sprint-vs-the-marathon">The Sprint vs. The Marathon&lt;/h2>
&lt;p>In our industry, it is easy to get caught up in the immediate: the &amp;ldquo;IPO hunt,&amp;rdquo; the constant job-hopping for a salary bump, or the rush to ship the next feature. We optimize for the next two years, often at the expense of the next twenty.&lt;/p>
&lt;p>I’ve been reflecting on Will Larson’s concept of &lt;em>&amp;ldquo;The Forty-Year Career.&amp;rdquo;&lt;/em> His argument is a necessary counter-narrative: instead of burning out for short-term wins, we should focus on compounding gains over decades.&lt;/p></description></item><item><title>The Human System: Applying Engineering to Leadership</title><link>https://kianoosh.dev/posts/2025-12-26-the-human-system-applying-engineering-to-leadership/</link><pubDate>Fri, 26 Dec 2025 00:00:00 +0000</pubDate><guid>https://kianoosh.dev/posts/2025-12-26-the-human-system-applying-engineering-to-leadership/</guid><description>&lt;h2 id="the-transfer-of-fundamentals">The Transfer of Fundamentals&lt;/h2>
&lt;p>In a recent article, Mallika Rao (Engineering Manager at Netflix) revisits a familiar friction point in our industry: the transition from maker to manager. She argues that when engineers move into leadership roles, they often stop applying the systems thinking they developed through years of hands-on engineering.&lt;/p>
&lt;p>This is a massive missed opportunity.&lt;/p>
&lt;p>We spend years learning how to optimize throughput, manage load, and debug complex interactions. Yet, when we step into management, we often treat the team as something entirely different, governed by vague intuition rather than structural logic. Rao suggests that systems thinking isn&amp;rsquo;t just for code—it is an essential toolkit for leadership.&lt;/p></description></item><item><title>Discipline Under Pressure: Shipping Without Messing Up</title><link>https://kianoosh.dev/posts/2025-08-20-discipline-under-pressure-shipping-without-messing-up/</link><pubDate>Wed, 20 Aug 2025 00:00:00 +0000</pubDate><guid>https://kianoosh.dev/posts/2025-08-20-discipline-under-pressure-shipping-without-messing-up/</guid><description>&lt;p>&lt;img src="https://kianoosh.dev/images/squid-game-umbrella-cookie-1536x913.jpg" alt="squid game umbrella cookie">&lt;/p>
&lt;h2 id="the-reality-of-urgency-in-startups">The Reality of Urgency in Startups&lt;/h2>
&lt;p>It’s crucial for every senior software engineer, technical leader, or anyone accountable for delivering technical solutions to know how to handle urgent tasks wisely. Let’s call this person a &lt;em>leader&lt;/em> — and today, that’s you.&lt;/p>
&lt;p>In some industries, or at certain stages of a company’s lifecycle, urgent requirements hit technical teams constantly. I currently work as a technical lead at a startup (&lt;a href="https://www.linkedin.com/company/donetech/">Done&lt;/a>), where the rules of the game seem to change every other week.&lt;/p></description></item></channel></rss>