"We need an SAP person" is one of the most common requests we hear, and one of the hardest to fill as written. SAP covers dozens of modules and very different kinds of work. A few decisions up front make the search shorter and the first month far more productive.
1. Functional, technical, or both?
Functional consultants (FI/CO, MM, SD, PP and others) translate business processes into SAP configuration. Technical consultants (ABAP, Basis, integration) build, connect and run the system. Few people are strong in both, so decide which gap you are really filling.
2. Which modules, and how deep?
Name the modules and the processes behind them. "SD with pricing and output determination" is a role someone can recognise themselves in. "SAP SD" is not.
3. ECC or S/4HANA?
SAP has set the end of 2027 for mainstream maintenance of SAP ECC 6.0, so many teams are planning or running a move to S/4HANA. Experience on a migration is different from day-to-day support on an existing system. Say which one you need.
4. What does done look like?
A go-live date, a set of enhancements, a backlog of tickets cleared? A clear outcome helps you decide between a contract role for a defined project and a full-time hire for the long term.
5. Who will they work with?
Name the internal process owner, the partner (if any) and the hours they need to overlap with. Consultants ramp up much faster when they know who signs off on their work.
Settle these five and the job description almost writes itself. If you would like a second opinion on an SAP role, talk to our team.