SAP consultant screening questions: modules, full-cycle implementations and contract terms
On this page
- Functional, technical, architect or support: place the candidate
- Module depth: configured, specified or used
- Implementations, rollouts and migrations: counting the go-lives
- ECC, S/4HANA and why timing matters to clients
- Certification status and how to check it
- Contract terms, travel and the partner chain
- How SAP resumes overstate experience
- Knockout checklist and scorecard
- Questions people ask
SAP consultant screening questions should pin down three things: which modules the candidate configured with their own hands, how many projects they took from design to go-live, and what role they played on each. Then cover the contract basics SAP work lives on: rate and basis, travel pattern, end dates, and whether their certification is current. A consultant with real depth names the company code structure they built, the integration point that failed in testing and the week of hypercare after cutover. An inflated resume lists eight modules and "5 full-cycle implementations" that turn out to be support tickets and one testing stint.
IT contractor screening questions covers W2, 1099 and corp-to-corp terms, rate math and right to represent for any contractor. This page adds what is specific to SAP: module and project depth, migration experience, the implementation partner relationship, and the travel expectations that end SAP processes late. For the platform's nearest neighbor in CRM, see Salesforce administrator screening questions.
Functional, technical, architect or support: place the candidate
| Role in practice | What the work produces | Question that places them | Common mismatch |
|---|---|---|---|
| Functional consultant (FI/CO, MM, SD, PP, EWM and others) | Business process design, configuration, functional specs, testing, user training | "What did you configure yourself on your last project?" | Key user or super user on the client side, described as consultant |
| Technical consultant (ABAP, integration, Basis) | Code, interfaces, system administration, performance, upgrades | "What did you build or run, and in which system landscape?" | Ran transports, described as Basis administration |
| Solution architect | Cross-module design, integration decisions, fit-gap | "Which design decisions were yours, and who signed them off?" | Senior functional lead in one module, titled architect |
| Support or AMS consultant | Incidents, small changes, month-end support on a live system | "How many tickets a week, and what was the biggest change you delivered?" | Years of support listed as implementation |
| Project or program manager | Plans, cutover, partner management, steering committees | "What was the budget and team size, and what went wrong at cutover?" | Workstream lead described as program manager |
Module depth: configured, specified or used
SAP resumes list modules the way engineering resumes list languages. Pick the one or two modules the client needs and go deep on each. You do not need to know SAP to hear whether the candidate knows their own configuration.
| Question | What a strong answer sounds like | Red flags |
|---|---|---|
| Which module did you spend most of the last three years in, and which sub-areas? | One primary module with sub-areas named, for example "FI, mainly accounts payable, asset accounting and the month-end close; some CO product costing." | Six modules at equal depth. |
| Tell me about something you configured that the business still uses. | A specific setup and the business reason: a pricing procedure, a release strategy for purchase orders, a new company code, warehouse putaway rules. | Only "handled configuration." |
| Where does your module hand off to the others, and what went wrong at that point? | A real integration issue: goods receipt postings landing in the wrong account, billing not flowing to finance, a costing run failing on missing master data. | Has never looked beyond their own module. |
| When configuration could not meet a requirement, what did you do? | Pushed back on the requirement, used standard functionality differently, or wrote a functional spec for a developer, with an example. | Every gap became custom code. |
| How did you test your configuration? | Unit tests, integration test cycles with other workstreams, user acceptance testing with named business users, and a defect they found late. | Testing was "the client's job." |
| Which master data did you own, and how was it loaded? | Knows the objects (materials, business partners, vendors, customers) and the load tool used on the project. | Data was someone else's problem, for a go-live role. |
Implementations, rollouts and migrations: counting the go-lives
"Full-cycle implementation" is the most stretched phrase on SAP resumes. Break each project into phases and ask which ones the candidate was on. A useful frame is SAP's own Activate phases (discover, prepare, explore, realize, deploy, run), because many S/4HANA projects use that vocabulary.
Worked example (invented candidate)
The resume says "4 full-cycle S/4HANA implementations in 5 years." You ask for each project, the phases on it and the dates:
- Project 1: explore through hypercare, 14 months. Full cycle.
- Project 2: joined in realize, left two months before go-live. Build and testing only.
- Project 3: a country rollout of an existing template, 6 months including go-live. Rollout, not a new design.
- Project 4: post-go-live stabilization, 9 months. Support.
The accurate line for the submittal: one full-cycle implementation, one rollout go-live, plus build and support experience. Still a good candidate, and now the client will not find the gap in the first interview.
- "Was it greenfield, brownfield or a selective data transition?" Strong: knows which approach and why the client chose it. Red flag: does not know how the old system's data got to the new one.
- "What was your role at cutover weekend?" Strong: specific tasks, such as loading open items, reconciling balances or validating the first postings. Red flag: was not there.
- "What broke in the first week after go-live?" Strong: a concrete hypercare issue and the fix. Red flag: nothing, on a real go-live.
- "Were you with the implementation partner, the client or a subcontractor?" Strong: a clear answer and who they reported to. Red flag: vague, which matters for verifying the project.
- "S/4HANA Cloud (public or private edition) or on-premise?" Strong: knows the deployment and what it limited. Red flag: cannot say.
ECC, S/4HANA and why timing matters to clients
Per SAP's maintenance strategy page, mainstream maintenance for SAP Business Suite 7 core applications runs until the end of 2027, with optional extended maintenance to the end of 2030 (as of September 2026). That is why so many clients are in, or planning, a move to S/4HANA, and why they ask for migration experience specifically.
- ECC only: valuable for support and for the discovery work on a migration, where someone must understand what the old system does. Ask whether they have had any S/4HANA training or sandbox time.
- S/4HANA configuration without a migration: knows the new system, but may not have handled data transition or custom code remediation.
- Migration experience: ask which parts they touched: simplification item checks, custom code, data migration, finance data reconciliation, business partner conversion. The answer tells you which migration role they fit.
Certification status and how to check it
SAP certifications are not required on most projects, but partners and clients sometimes ask for them, and partners may need certified consultants for their own program status. Two facts, as of September 2026:
- Certifications need a yearly assessment to stay valid. SAP's staying certified FAQ describes a short assessment each year; missing it means the certification is no longer valid.
- The digital badge shows the status. SAP issues digital badges through Credly, and the badge shows as expired when a certification lapses. Ask the candidate for the badge link rather than a certificate PDF with a date on it.
An old ECC-era certification with no current badge is common among experienced consultants and not a problem in itself. It only matters when the client or partner has asked for current certification.
Contract terms, travel and the partner chain
| Question | What a strong answer sounds like | Red flags |
|---|---|---|
| The client wants Monday to Thursday on site every week for the first six months. Can you commit to that? | A clear yes, a limit ("every other week"), or a no you can take to the client now. | "Probably," then a remote-only request after the offer. |
| How do you need travel expenses handled: included in the rate or billed separately? | Knows their position and a number if expenses are included. | Has not thought about it, for a travel-heavy role. |
| What rate do you need, on what basis? | A rate and whether it is W2, 1099 or corp-to-corp. Do the conversion math in IT contractor screening questions before you answer. | A rate with no basis. |
| When does your current project end, and could it extend? | A date and the likelihood of extension, especially near a go-live, when extensions are common. | Available "immediately" while mid-cutover on another project. |
| Has anyone else submitted you to this client or its implementation partner? | A direct answer. SAP projects often run through a partner with several staffing vendors, so double submissions happen. | Unsure, or already submitted through another vendor for the same project. |
| Are you legally authorized to work in the US, and will you now or in the future need visa sponsorship? For corp-to-corp, who is your employer of record? | Direct answers. | None. Ask every candidate the same way. |
How SAP resumes overstate experience
| Pattern | What it looks like | How to check |
|---|---|---|
| Project count inflation | "6 full-cycle implementations" | Phases and dates per project, as in the worked example |
| Module list | FI, CO, MM, SD, PP, QM, PM, WM | "Which one did you configure every week last year?" |
| Super user as consultant | Client-side business role listed as SAP consultant | "Were you employed by the client or a partner, and did you have configuration access?" |
| Support as implementation | Years of tickets on a live system | "What was the biggest change you designed, and did it go through a project?" |
| Partner logo borrowing | A large partner's name with an unclear link to them | "Who paid you: the partner, a subcontractor or your own company?" |
| "S/4HANA" as a label | ECC work described with S/4HANA terms | "Which release, which deployment, and what changed for your module compared with ECC?" |
Knockout checklist and scorecard
Must-ask on every SAP screen
- Role type: functional, technical, architect, support, project management.
- Primary module and sub-areas, with one configuration still in use.
- Each project with phases, dates, employer and deployment type.
- Cutover role and a hypercare issue.
- ECC, S/4HANA and migration experience, separately.
- Certification badge status, if the client asked.
- Travel pattern, rate and basis, end date, prior submissions, work authorization.
Knock out, or flag to the client before submitting, if:
- The client needs a go-live lead and the candidate has never been on a project through cutover.
- The required module is one they have only used, not configured.
- The client requires on-site travel the candidate cannot commit to.
- The candidate has already been submitted to the same project through another vendor.
| Area | 1 | 2 | 3 | 4 |
|---|---|---|---|---|
| Module depth | End user or super user | Support and small changes | Configured core processes | Designed the module and its integrations |
| Project experience | No projects | Partial phases | One or more go-lives | Several go-lives, leading a workstream |
| S/4HANA and migration | ECC only | S/4HANA training or sandbox | S/4HANA configuration | Led migration work in their area |
| Contract fit | Travel or rate deal-breaker | Two open questions | One open question | All aligned |
Put the project breakdown straight into the submittal with the candidate's own description of cutover. "One full-cycle S/4HANA go-live; 'I reconciled the open AP items on cutover night'" is stronger and safer than an inflated project count. The candidate submittal template shows the format, and Interview Signal can capture those quotes while you talk, without a bot joining the call.
Questions people ask
What does 'full-cycle implementation' mean on an SAP resume?
It usually means the consultant worked on a project from blueprint or explore phase through build, testing, go-live and hypercare. Ask which phases they were actually on the project for, because many consultants join after design or leave before go-live and still count the project.
Do SAP certifications expire?
Under SAP's current program, certified people must pass a short stay-certified assessment each year to keep a certification valid, and the digital badge shows as expired if they miss it. Check the badge status rather than the year the exam was passed.
Why does ECC versus S/4HANA experience matter so much?
SAP's mainstream maintenance for the Business Suite 7 core applications, which include ECC, runs until the end of 2027, so many clients are migrating to S/4HANA. Clients running a migration want someone who has done one, not only someone who knows the old system.
Can I ask an SAP contractor whether they travel?
Yes. Describe the client's on-site pattern, such as Monday to Thursday on site every week, and ask whether the candidate can commit to it and how expenses need to work. Do not ask about family circumstances to judge it.