Why pre-screen SAP consultants before the client-facing interview
SAP resumes are long and hard to read. The same project appears on several of them, module lists cover far more ground than any one consultant owned, and years of experience say nothing about whether the person configured anything or sat in support. A short screen surfaces which modules they actually held, whether they have been through a cutover, and how they behaved when the data migration was wrong on the day it mattered.
What actually matters when screening SAP Consultant candidates
- 01
Technical proficiency
Probe the modules they genuinely configure, plus enough process knowledge to know what the business is doing.
- 02
Systems and trade-offs
Test how they judge standard configuration against custom development when the client insists on their own process.
- 03
Evidence and rigour
Check how they diagnose a process failing in production across configuration, data, and integration.
- 04
Collaboration and communication
Assess how they handle a client whose requirements shift mid-implementation with the go-live date unchanged.
Pre-screening questions to ask SAP Consultant candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Module depth
3 questions01Which specific SAP modules are you familiar with, and which have you configured yourself?
Listen forA clear split between modules they configured and modules they worked alongside, with depth in one or two rather than shallow coverage of eight.
Claims equal depth across many modules, or cannot separate what they configured from what the wider team delivered.
02Have you had any experience with SAP S/4HANA, and what changed in your work?
Listen forConcrete differences they handled: the simplified data model, Fiori adoption, custom code remediation, and whether it was a conversion or a new implementation.
Confirms S/4HANA experience but cannot name anything that differed from the older release in practice.
03Can you discuss your experience customising SAP solutions?
Listen forA stated preference for standard configuration, with named cases where custom development was justified and what it cost at the next upgrade.
Reaches for custom development by default, or has no view on the maintenance burden custom objects create.
Data and cutover
3 questions04Can you discuss your experience with SAP data migration?
Listen forThe tools they used plus the messy part: cleansing legacy records, reconciliation after load, and what they did when balances did not match on the first attempt.
Describes migration as a technical load with no reconciliation step, or has never been present for a production cutover.
05Can you explain your role in the implementation or upgrade of SAP at your previous employer?
Listen forTheir specific scope inside a named phase, with decisions they owned rather than a description of the programme they were attached to.
Describes the whole programme in the first person, or a role that turns out to be support after go-live.
06How do you handle troubleshooting in an SAP environment?
Listen forA diagnosis path they own: reproducing in a lower environment, reading dumps or logs, isolating configuration from data, and when they raise it with SAP.
Opens a ticket with SAP as a first step, or cannot describe an issue they traced to root cause themselves.
Projects delivered
3 questions07Can you discuss a time when you implemented a new process or system using SAP?
Listen forThe business process before and after, what the change was meant to fix, and evidence the new process was actually used six months later.
Describes a configuration change with no business process behind it, or no idea whether adoption held.
08Can you tell me about a time when you improved the efficiency of an SAP system?
Listen forA measured improvement: run time, close duration, manual steps removed, with their own contribution separated from the team's work around it.
Claims an improvement with no measure attached, or gains that came entirely from a hardware or release upgrade.
09Have you ever been involved in a failed SAP implementation? If so, how did you handle it?
Listen forA direct account with their own part included: what was missed in scoping or data, what they raised at the time, and what they do differently now.
Claims never to have seen a project go wrong, or places the entire failure on the client without any self-assessment.
Working with users
3 questions10How comfortable are you creating and delivering training for end users?
Listen forTraining built around the users' actual tasks, with material they wrote themselves and an account of the group that resisted the new process.
Hands training to a change team, or describes end users as the reason implementations run into difficulty.
11How do you typically handle user issues after an SAP implementation?
Listen forA hypercare approach with triage: which issues were defects, which were training gaps, and how they stopped the same question arriving fifty times.
Treats post go-live support as someone else's phase, or has left every project before hypercare started.
12Have you ever had to adapt your strategy due to project changes?
Listen forA scope or timeline change with the trade-off named: what was dropped, who agreed it, and how the go-live date survived or moved.
Absorbs every change without renegotiating scope, or describes changes as the client failing to know their own requirements.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Technical proficiency
35%5Configures their modules independently and understands the business processes behind the configuration.
Systems and trade-offs
25%5Pushes clients toward standard configuration where it holds, and can justify each customisation they allowed.
Evidence and rigour
25%5Isolates configuration, master data, and integration causes systematically rather than escalating to the vendor first.
Collaboration and communication
15%5Manages scope and go-live risk transparently, raising the trade-off with the client before the date is at risk.
SAP resumes list far more modules than any one consultant owned. A one-way video screen lets you hear which parts they actually configured and how a cutover went before you put them in front of a client.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for an SAP consultant take?
Fifteen minutes across eight to ten questions, answered async. Enough to confirm module ownership, migration experience and S/4HANA exposure before a client-facing interview where the candidate meets the people who will work with them.
Should I screen for specific modules or general SAP experience?
Screen for the modules you run. A consultant strong in finance is not interchangeable with one strong in supply chain, and the resume rarely distinguishes what they configured from what they sat next to on the same programme.
Evaluating answers
What is the strongest signal when screening an SAP consultant?
A specific account of a project that went wrong, including their own part in it. Consultants with several implementations behind them describe the data problem or the scope change plainly. Those without describe every project as a success.
How do I judge whether a consultant is genuinely S/4HANA experienced?
Ask what changed for them, not whether they have used it. Listen for the simplified data model, Fiori adoption, and how they handled custom code during conversion. Vague answers usually mean training exposure rather than a delivered project.
Go deeper on this role
Sanat has been hiring since 2012 and watching the recruitment industry change up close ever since, and turned that screening process into Hirevire's video screening platform. LinkedIn
