Technical interview questions you should be asking ERP candidates

You're about to interview an SAP consultant. You don't understand half the acronyms on their CV. But you need to figure out if they're the real deal or bluffing their way through.

Here are 10 questions to ask, what good answers sound like, and what red flags to watch for.

Question 1: Walk me through your most recent project from start to finish.

Good answer: Structured narrative. Names the client, the industry, the duration, the team size. Explains the phases (blueprint, realize, test, deploy, hypercare). Mentions specific deliverables. Uses module names naturally.

Red flag: Can't describe the project beyond one sentence. Talks about "the team" but not their specific contribution. No numbers anywhere.

Question 2: What modules have you worked on and which one is your strongest?

Good answer: Lists specific modules (FI/CO, MM, SD, PP). Names one as their primary. Can explain why. "I've spent 8 years deep in FI/CO. I know the new asset accounting in S/4HANA inside out. I've also done MM configuration but I wouldn't call myself an expert."

Red flag: Lists 10+ modules as "expert." No one is expert in 10 modules. Either they're exaggerating or they're a generalist with no depth.

Question 3: What's the difference between SAP ECC and S/4HANA?

Good answer: Mentions the simplified data model (MATDOC, ACDOCA tables), Fiori UX layer, universal journal in finance, embedded analytics, ABAP for HANA. Can explain practically why it matters for their module.

Red flag: "S/4HANA is the new version of SAP." That's technically true but shows no depth. Like saying "a Tesla is a new kind of car."

Question 4: Tell me about a time something went wrong on a project.

Good answer: Names a specific problem. Data migration failure, scope creep, stakeholder conflict, performance issue. Explains what they did about it. Gives the outcome. Shows they've been in the trenches.

Red flag: "Everything went smoothly on my projects." Nobody has only smooth projects. They're either lying or they weren't close enough to the action to know what went wrong.

Question 5: How do you handle a client who keeps changing requirements?

Good answer: Describes a change management process. Impact assessment, stakeholder communication, scope vs timeline tradeoff discussion, documentation. Gives a real example.

Red flag: "I just do whatever the client wants." That's not client management. That's scope creep.

Question 6: How many full life cycle implementations have you done?

Good answer: A specific number. Can name each one. "Three full life cycle. Etihad Airways (ECC), EDGE Group (S/4HANA brownfield), and TII (S/4HANA greenfield)."

Red flag: "Numerous implementations." Can't count them or name them.

Question 7: What's your experience with testing?

Good answer: Describes their role in unit testing, integration testing, UAT. Mentions test scripts, defect management, regression testing. Knows the difference between testing their own work and coordinating UAT.

Red flag: "The testing team handles that." If they've never been involved in testing, they've never done a full implementation.

Question 8: How do you approach knowledge transfer?

Good answer: Documentation during the project (not just at the end). Train-the-trainer approach. Shadowing. Go-live support transition. Hypercare planning.

Red flag: "I hand over the documentation." That's not knowledge transfer. That's document dumping.

Question 9: What certifications do you have?

Good answer: Names specific SAP certifications, when they got them, whether they're still valid. SAP has different certification tracks. S/4HANA certifications are worth more than ECC-era ones.

Red flag: "I have SAP certification." Which one? When? For which module? Vague certification claims are often exaggerated.

Question 10: Why are you looking to move?

Good answer: Contract ending, looking for specific technology/industry/geography, career growth. Clear and professional.

Red flag: Bad-mouthing the current client or employer. Unrealistic expectations. "I want to be a director but I've never managed a team."

The bottom line for recruiters

You don't need to understand ABAP, BAPI, or RFC. You need to listen for specifics vs generalities. Real consultants give names, numbers, and details. Padded CVs give vague summaries.

If you want to go deeper, ERPCV generates technical interview questions from the candidate's actual CV. Upload their resume. Get 15 tailored questions with expected answers. You'll know what good sounds like before you pick up the phone.

Upload a CV. Get module depth, project verification, and interview questions.