<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Next Role Studio — Notes from the Studio</title>
    <link>https://blog.nextrole.studio/</link>
    <description>Plain-English writing on how hiring systems read your resume, the resume fixes that actually matter, and how to hire a job-search service without getting burned.</description>
    <language>en-us</language>
    <lastBuildDate>Thu, 05 Nov 2026 19:35:00 GMT</lastBuildDate>
    <atom:link href="https://blog.nextrole.studio/rss.xml" rel="self" type="application/rss+xml" />
    <image>
      <url>https://nextrole.studio/assets/logo-tile.png</url>
      <title>Next Role Studio — Notes from the Studio</title>
      <link>https://blog.nextrole.studio/</link>
    </image>
    <item>
      <title>The two-week silence problem: when to follow up, and what to say</title>
      <link>https://blog.nextrole.studio/posts/the-two-week-silence-and-follow-up-timing.html</link>
      <guid isPermaLink="true">https://blog.nextrole.studio/posts/the-two-week-silence-and-follow-up-timing.html</guid>
      <pubDate>Thu, 05 Nov 2026 19:35:00 GMT</pubDate>
      <category>The search, week by week</category>
      <author>The Next Role Studio team</author>
      <description>Two weeks of silence after an application or interview isn't a verdict — it's usually a queue. A plain-English follow-up clock: when to write, what to say, and when to move on.</description>
    </item>
    <item>
      <title>Why your applications vanish: the ATS screen, explained</title>
      <link>https://blog.nextrole.studio/posts/why-applications-vanish-ats.html</link>
      <guid isPermaLink="true">https://blog.nextrole.studio/posts/why-applications-vanish-ats.html</guid>
      <pubDate>Thu, 05 Nov 2026 14:00:00 GMT</pubDate>
      <category>How hiring systems work</category>
      <author>The Next Role Studio team</author>
      <description>You never hear back, so you assume a person read your resume and said no. Usually, no person was involved. What actually happens to your application between hitting submit and the silence — parsing, keyword matching, and the knockout questions — and the structural fixes that get your resume in front of a human.</description>
    </item>
    <item>
      <title>Resume fixes that actually move the needle (and the ones that don't)</title>
      <link>https://blog.nextrole.studio/posts/resume-fixes-that-matter.html</link>
      <guid isPermaLink="true">https://blog.nextrole.studio/posts/resume-fixes-that-matter.html</guid>
      <pubDate>Thu, 05 Nov 2026 13:00:00 GMT</pubDate>
      <category>Resume craft</category>
      <author>The Next Role Studio team</author>
      <description>Some resume changes decide whether you get interviews. Most of the popular ones don't. A straight split between the fixes worth your weekend — numbers on your bullets, the posting's own words, a six-second scan test — and the cosmetic ones worth skipping.</description>
    </item>
    <item>
      <title>What a managed job search should never promise you</title>
      <link>https://blog.nextrole.studio/posts/what-a-managed-search-should-never-promise.html</link>
      <guid isPermaLink="true">https://blog.nextrole.studio/posts/what-a-managed-search-should-never-promise.html</guid>
      <pubDate>Thu, 05 Nov 2026 12:00:00 GMT</pubDate>
      <category>Choosing a service</category>
      <author>The Next Role Studio team</author>
      <description>If a service guarantees you a job, the guarantee is the product. Placement promises, percentage-of-salary fees, applications sent in your name without your say — the red flags, and the questions to ask anyone who offers to run your search. Including us.</description>
    </item>
  </channel>
</rss>
