<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Transition on Jeremiah Windle</title><link>https://7f57629a.jeremiahwindle.pages.dev/tags/transition/</link><description>Recent content in Transition on Jeremiah Windle</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 01 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://7f57629a.jeremiahwindle.pages.dev/tags/transition/index.xml" rel="self" type="application/rss+xml"/><item><title>MSP to Enterprise: Skills That Transfer and Gaps You Need to Close</title><link>https://7f57629a.jeremiahwindle.pages.dev/blog/msp-to-enterprise-skills/</link><pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate><guid>https://7f57629a.jeremiahwindle.pages.dev/blog/msp-to-enterprise-skills/</guid><description>Four years in an MSP seat gives you something that&amp;rsquo;s genuinely hard to get in enterprise IT: breadth under pressure. When you&amp;rsquo;re responsible for network infrastructure across 40 different organizations simultaneously — each with different tools, different configurations, and different stakes — you develop a kind of situational awareness that pure deep-dive engineers often don&amp;rsquo;t have.
But it also leaves gaps. Real ones. This post is an honest accounting of both.</description></item></channel></rss>