Technical screening questions
Ask for one example per question and listen for specifics.
- What is the difference between a user exit and a BAdI? A good answer: Older versus object-oriented enhancement.
- How do you tune a slow report? A good answer: Selects, internal tables and runtime analysis.
- What changed in ABAP for HANA? A good answer: Code pushdown and CDS.
- How do you integrate with external systems? A good answer: IDocs, RFC and OData.
- How do you manage transports? A good answer: Order types and release flow.
Quick screening questions
Use these when you have only a few minutes.
- What types of enhancements have you built (user exits, BAdIs)?
- How do you debug a performance problem in an ABAP report?
- Which S/4HANA changes affected your ABAP work?
What separates the levels
Match the level to the requirement before you submit.
- Junior: fixes defects and small reports.
- Mid: develops enhancements.
- Senior: leads technical design.
Red flags
Any of these is a reason to probe further.
- Only functional SAP knowledge.
- Cannot debug.
- No HANA exposure for an S/4 role.
Tools you should hear mentioned
An SAP ABAP developer with real experience usually names several of these without prompting.
- ABAP
- SAP GUI and ADT
- CDS views
- OData
- IDocs and BAPIs
- Transport management
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 ABAP developer 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.