Lakshya

Product, Delivery & Technology Finance

Agile Delivery — read this first

Delivery · 1 Scrum Master posting

If you are aiming at a Scrum Master or Agile Coach career, read this before you spend another month on it. The data is unambiguous and it is not what the certification market implies.

Across 20,376 postings from 189 public company job boards, this atlas found one Scrum Master posting, zero Agile Coach, zero Release Train Engineer and zero Iteration Manager — against 400 Program Manager and 194 Technical Program Manager.

TITLE COUNTS ACROSS 20,376 POSTINGS Program Manager 400Technical Program Manager 194Project Manager 46Delivery Manager / Lead 12Scrum Master 1Agile Coach 0Release Train Engineer 0Iteration Manager 0
The dedicated agile-ceremony roles have effectively disappeared from these employers. The work did not vanish; the standalone job did. Facilitating a standup, running a retrospective and managing a backlog were absorbed into the engineering manager and the program manager, and hiring now happens under those titles.

An important honesty caveat

This corpus is product companies and technology vendors on public ATS boards. It systematically under-covers IT services firms, consultancies and large non-technology enterprises — and those employers do still hire Scrum Masters and agile coaches in volume, particularly in India. So the honest statement is narrower than the headline: the dedicated agile role has largely gone at product companies, and persists in services and enterprise IT. If you are targeting Infosys, TCS, Accenture or a bank's delivery organisation, that market is real. If you are targeting a product company, it is not.

Where the work actually went

What a Scrum Master didWho does it now at a product companyWhat it is called
Facilitating ceremoniesThe engineering manager, or the team itselfNot a role — a few hours a week
Removing blockersThe engineering manager and the TPMPart of managing or programme work
Backlog managementThe product managerProduct management
Cross-team dependenciesThe technical program managerTPM — 194 postings
Process improvementThe team, or a platform/DevEx functionDeveloper experience
Metrics and reportingThe TPM or the engineering directorProgramme management

What to do about it, concretely

  • If you have agile delivery experience, target TPM and Program Manager. That is where your actual skills — dependency management, cross-team coordination, risk, communication under uncertainty — are being bought, at 594 postings between them.
  • The gap you must close is technical depth. Technical depth is named in only 24% of delivery postings, which sounds forgiving, but the TPM interview will ask you to reason about an architecture and a failure mode. You do not need to code; you need to be able to hold a technical conversation without deferring every question.
  • Drop the ceremony vocabulary from your CV. A CV built around Scrum events, velocity and SAFe configurations reads as process administration to a product-company hiring manager. The same experience described as dependency management, risk, and delivery of a named outcome reads entirely differently — and it is the same work.
  • Get one measurable delivery outcome. Not ‘improved team velocity’, which is a team-relative and gameable number. Something like cycle time from commit to production, or a programme delivered against a date with a stated scope.
  • If you stay in services, that is a legitimate market — but understand that the ceiling and the compensation differ, and that the certification stack that opens doors there does very little at product companies.

Why the certifications do not transfer

CSM, SAFe and PMI-ACP are widely held and cheaply obtained, which is precisely why they carry little signal at product companies. Where certifications still open doors in this atlas — OSCP for offensive security, for example — it is because they are hard and demonstrate a verifiable skill.

The artefact that does carry signal here is a delivery you can describe in numbers: what was committed, what shipped, what slipped, what you did about it, and what you changed afterwards.

The book for this field

Product & Delivery

Prioritisation that survives contact, writing that lets engineering start, discovery when your users are not consumers, measurement and its failure modes, dependencies and honest status, saying no well, pricing and unit economics, and scoping a non-deterministic feature.

CHAPTER 5Dependencies, critical path and honest statusThe core of delivery work: knowing which of six teams can actually move the date.READ THE CHAPTER →CHAPTER 4Measuring a productMetrics, OKRs, and the specific ways each is gamed. Named in only 14% of postings, which is itself a finding.READ THE CHAPTER →CHAPTER 6Stakeholders, and saying no wellThe skill named in 81% of product and 90% of delivery postings — higher than anything technical.READ THE CHAPTER →

All 13 chapters in Product & Delivery →

Cross-cutting

Skills every archetype tests

These are shared across every field on this site — the same question asked in different vocabulary — so preparation here compounds rather than being spent once. The book above is specific to your field.

Measuring what resists measurementTested in every field on this site under a different name — evals, SLOs, DORA, ablations. Named in 59% of AI and 42% of platform postings, and almost nobody studies it deliberately.READ THE CHAPTER →Discovery before solutionThe decisive round in three separate archetypes, with the lowest pass rate of any stage.READ THE CHAPTER →

Practice the 11 Product questions →  ·  Back to Product, Delivery & Technology Finance →