Technical screening questions
Ask for one example per question and listen for specifics.
- Which module and release have you worked on most recently? A good answer: A specific module and ECC or S/4HANA version with the project phase.
- Walk me through an end-to-end process in your module. A good answer: For example procure-to-pay in MM with configuration points.
- How do you handle a change request? A good answer: Impact analysis, transport management and testing.
- What was your role at go-live? A good answer: Cutover tasks, hypercare and issue resolution.
- How have you worked with ABAP developers? A good answer: Writing functional specifications and reviewing results.
Quick screening questions
Use these when you have only a few minutes.
- Which module and how many full-cycle implementations?
- ECC to S/4HANA: what was your role?
- Describe a complex configuration you owned.
What separates the levels
Match the level to the requirement before you submit.
- Junior: supports and tests in one module.
- Mid: configures and owns workstreams.
- Senior: leads design and cross-module integration.
Red flags
Any of these is a reason to probe further.
- Cannot name a module or release.
- Only end-user experience.
- Claims several unrelated modules at depth.
Tools you should hear mentioned
An SAP consultant with real experience usually names several of these without prompting.
- SAP ECC or S/4HANA
- SAP GUI and Fiori
- Solution Manager
- ABAP specifications
- SAP Activate or ASAP
- Test tools
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should an SAP consultant screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.