<?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>Scaling on Girish Shekhar</title><link>https://blog.girishshekhar.com/tags/scaling/</link><description>Recent content in Scaling on Girish Shekhar</description><generator>Hugo -- 0.163.3</generator><language>en-us</language><lastBuildDate>Wed, 15 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.girishshekhar.com/tags/scaling/index.xml" rel="self" type="application/rss+xml"/><item><title>Principal Engineers Don't Scale by Doing More. They Scale by Moving Out.</title><link>https://blog.girishshekhar.com/posts/pe-roles-intentionality/</link><pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.girishshekhar.com/posts/pe-roles-intentionality/</guid><description>Most senior engineers think about what role they play on a team. Fewer think about how long they should play it — and what happens when they don&amp;rsquo;t move on. This post examines two complementary frameworks for PE role clarity, and why intentional role transitions — not just role awareness — are what actually let Principal Engineers scale their impact across an organization.</description></item></channel></rss>