Product, Delivery & Technology Finance
Agile Delivery — read this first
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.
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 did | Who does it now at a product company | What it is called |
|---|---|---|
| Facilitating ceremonies | The engineering manager, or the team itself | Not a role — a few hours a week |
| Removing blockers | The engineering manager and the TPM | Part of managing or programme work |
| Backlog management | The product manager | Product management |
| Cross-team dependencies | The technical program manager | TPM — 194 postings |
| Process improvement | The team, or a platform/DevEx function | Developer experience |
| Metrics and reporting | The TPM or the engineering director | Programme 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.
What this role tests
Themes, and where to learn them
These chapters are shared across every role that tests them, so preparation here compounds rather than being spent once.
Practice questions across all themes → · Back to Product, Delivery & Technology Finance →