What actually makes an SAP skill scarce
Scarcity in SAP is rarely about the module. It is about the combination — and combinations multiply faster than the market grows.
Rufouss Practice Team
24 August 2026
CIO · Programme Director · Talent Lead
- Scarcity compounds. Module, industry, seniority and availability each cut the pool, and they multiply rather than add.
- A market that looks large in aggregate can be empty at the intersection a programme actually needs.
- The search that finds the person is usually the one that started before the requirement existed.
The question
A programme director says the market is short of SAP EWM consultants. It is not, particularly. There are thousands of people whose profile says SAP EWM. What the programme actually needs is someone who has taken a warehouse live rather than configured one in a sandbox, who has done it in a comparable industry, at a seniority that can hold a room, and who is free in six weeks.
Each of those four conditions is reasonable on its own. Together they behave very differently from how they read.
Why it is harder than it looks
Filters do not add up. They multiply. If a quarter of the people with the module on their profile have genuinely delivered a go-live, and a third of those have the industry, and half of those are senior enough, and a fifth of those are available inside the window, a pool of four thousand becomes something like thirty. Change any one assumption and the answer moves by a factor.
This is why aggregate market figures are so misleading in SAP hiring. The market is large at the level of the module and close to empty at the intersection. A search that returns nine hundred names has not found nine hundred candidates; it has found nine hundred profiles that share one attribute with the requirement.
There is a second compounding factor that rarely appears in the brief. Scarcity is not stable. The pool for any given combination changes every month as people start, finish, extend and become unavailable. A candidate map built eighteen months ago describes a market that no longer exists.
A better way to think about it
Two things follow, and they are both about sequence rather than effort.
Decide which condition is genuinely fixed. Most requirements arrive with four hard constraints and no ranking. Almost always one or two are firm and the rest are preferences that were written as requirements. Knowing which is which is the difference between a shortlist and a long silence — and it is a decision the hiring organisation has to make, not the search partner.
Accept that the useful search happened earlier. A search that begins when the requirement lands is starting from a cold market at the moment the pressure is highest. The searches that produce people in days are the ones where the market segment was already read, segmented and spoken to before anyone needed anything — and where whoever is doing the screening can tell a genuine delivery record from a well-written profile.
What it looks like in practice
A requirement that has been ranked reads differently. Instead of senior SAP EWM consultant, oil and gas, Bengaluru, six weeks, it reads: must have taken EWM live at least twice; industry preferred but not essential; will consider remote for the first month; six weeks is firm because of the cutover date.
The second version is not a weaker requirement. It is the same requirement with the trade-offs made deliberately by the person who owns the outcome, rather than made accidentally by whoever gives up first.
The market for SAP consultants is not short of people. It is short of the specific combination a programme needs on the date it needs it — which is a different problem, and it is not solved by searching harder.
- Rufouss field observationRecurring patterns across SAP staffing requirements. No market-size figures are published here.
Written by the senior SAP practitioners who run Rufouss assessment, testing and automation engagements.
Three more on this.
Contract, contract‑to‑hire or permanent: choosing the shape of an SAP hire
A permanent hire for a project-shaped need creates a problem eighteen months later. A contractor for a permanent capability creates one immediately. The choice is usually made on budget lines rather than on the work.
2 min read S/4HANABuilding regression into the S/4HANA release rhythm
SAP ships on its own schedule. A regression suite that is rebuilt for each release will always be behind it.
4 min read AutomationWhat should you automate first in SAP?
Sustainable automation starts with stable, repeatable and business-critical processes rather than automation-volume targets.
4 min readWorking on something like this?
No question is too simple, and none is too complicated. Ask us what we have seen — there is no charge for a conversation.
