One thing I noticed across several recent job postings: employers are making a clearer distinction between delivery leadership and Agile/Agile transformation roles.

For example, a VA modernization engagement is hiring a Technical Program Manager whose role is "not an expectation that one person will personally conduct Agile coaching, configure Jira, or build every PVO artifact." A construction company seeking a Director of Technical Program Management emphasizes portfolio operating model design and delivery predictability—not SAFe coaching or cultural transformation as the primary mandate. A federal contractor's Transition Lead role centers on sequencing dependencies, readiness criteria, and knowledge transfer across technical domains—execution leadership, not methodology implementation.

By contrast, roles that do emphasize Agile methodology expertise tend to be titled explicitly as Scrum Master or Agile Coach positions, often with stated expectations around "driving continuous improvement initiatives" and "coaching Agile teams."

The practical implication: if you're a program or delivery leader, there's a real market distinction between roles that want you to optimize how work gets done and roles that want you to teach or transform how teams *think* about doing work. Both are valuable. But mixing them can create ambiguity about what success actually looks like—and diffuse your accountability.

Worth asking yourself: Am I being hired to deliver outcomes, or to shift organizational practices? And does the role description clarify which one is the primary measure of success? Because the better hiring managers do seem to be making that call explicit now.

Curious whether you're seeing this distinction in the roles you're evaluating or building.

Evidence and methodology: https://ai.intelligence.strategichonesty.com/reports/real-postings-from-g-iii-apparel