ERP Consultant Interview Questions 2026

Last updated: July 22, 2026

By Gregg Flecke, Senior Talent Acquisition Partner, KORE1

The ERP consultant interview questions that matter most test judgment that survives a platform change. Business-process mapping, fit-gap analysis, data migration, and integration architecture reveal more than product trivia on SAP, Oracle, Workday, Dynamics, or NetSuite.

I have spent close to thirty years placing IT and ERP talent, and here is the thing almost every ERP hiring panel gets backwards. They interview for the logo. They spend the whole loop confirming the candidate knows their platform, then wonder six months into an implementation why a five-times-certified consultant cannot reconcile a filthy item master or tell the CFO no.

The platform matters. It is not the thing that breaks projects.

What breaks projects is the stuff that looks the same on every ERP. Requirements nobody wrote down. A vendor master with fourteen years of duplicates. An integration that works in test and dies at go-live. A business process the consultant configured around instead of fixing. None of that is a SAP problem or a NetSuite problem. It is an ERP problem, and the interview has to test for it whether you run S/4HANA, Oracle Cloud ERP, Microsoft Dynamics 365, Workday, or a tier-two suite like Infor or Epicor. Same failure modes. The logo just changes.

Full disclosure, because you should know where I sit. KORE1 places ERP functional and technical consultants through our ERP consultant staffing practice, and we earn our fee when the hire is still there and still delivering a year later, not when the panel wraps. Our twelve-month retention on direct-hire placements runs 92% across more than thirty U.S. metros. ERP is one of the harder verticals to hit that number in, because a mis-scoped first hire tends to take the whole implementation budget down with it. So the loop below is the one I actually push clients to run. If you are the candidate reading this instead of the hiring manager, our ERP consultant career guide is written for you.

Before the First Question: Specialist or Cross-Platform Consultant?

Decide this before you write a single interview question, because it changes the whole loop. Are you hiring someone to go deep on the one ERP you already run, or someone who can carry business-process and implementation discipline across platforms because you are mid-migration, multi-ERP, or not sure yet what you are landing on?

Both are legitimate hires. They are not the same interview.

The specialist gets weighted toward platform depth. If you are two years into Oracle Cloud ERP and you need someone to own Financials configuration, you want scars specific to Fusion, not a generalist who has touched six suites at the surface. The cross-platform consultant gets weighted toward transferable judgment. If you are moving off a legacy on-prem system and you have not committed to the destination, or you run three ERPs across acquired business units, the person who has migrated data between platforms and lived through more than one cutover is worth more than the deepest single-product expert.

Comp tells part of the story too. Here is where the major platforms land in 2026 for a mid-to-senior consultant, base salary, before bonus or contract premium.

Treat those as directional. They come from Glassdoor, ZipRecruiter, Salary.com, and Levels.fyi ranges reconciled against our own placed base, and the variance between sources is wide enough that you should never anchor on one. The Bureau of Labor Statistics puts the median wage for computer systems analysts, the category most ERP consultants fall under, at $103,790 as of May 2024, with 9% projected growth through 2034. That is the floor of the market. ERP specialization pulls well above it. Tier-two suites like Infor CloudSuite, Epicor Kinetic, and Sage usually trail the majors on base, and the public data on them is thinner, which matters when you are trying to set a fair band with fewer comps to lean on. For a live pull on any specific role, our salary benchmark assistant runs current ranges by title and metro.

The Cross-Platform Core: Six Questions That Work on Any ERP

These are the questions I would keep no matter what is stamped on the box. Every one of them targets a competency that transfers, and every one has a weak answer that sounds fine until you ask the follow-up. That second layer is where you separate the consultant from the person who has watched consultants work.

Walk me through the last full implementation you owned, from discovery to hypercare. Where did it go sideways?

Open it and go quiet. Do not fill the silence. A real implementation owner names the client, the modules in scope, the timeline, the go-live date, and the one thing that nobody saw coming. The weak version is a resume bullet read aloud. “Led an ERP implementation for a manufacturer” tells you nothing. “Nine-month Dynamics 365 F&O rollout across two plants, went live on the second attempt because the first cutover failed on inventory valuation, and I owned the data cleanup that got us there” tells you everything. The tell is whether they volunteer the failure without being pushed. Every senior consultant has a project that hurt. The ones who claim every implementation went clean are either junior or lying, and both cost you the same at go-live.

How do you run a fit-gap? Give me a real gap you found and what you did with it.

More of the hires I have watched go wrong stumbled here than on any other competency. Fit-gap analysis is the discipline of comparing what the business does to what the software does out of the box, and deciding what to accept, configure, extend, or customize. It is universal now. SAP calls the modern version clean core. Oracle, Microsoft, and NetSuite all preach the same religion under different names: stay close to standard, extend on the side, keep the core upgrade-safe. The strong answer treats a gap as a decision with tradeoffs, not a ticket to write custom code. Watch for the candidate who defaults to customization for every gap. That instinct is a legacy on-prem habit, and in a cloud ERP it produces the technical debt that makes the next upgrade a nightmare. The best consultants push the business to change its process before they change the software. That conversation is uncomfortable. It is also the job.

Talk me through your approach to data migration. What is the part everyone underestimates?

If a candidate is relaxed about data migration, they have not done enough of it. This is where implementations actually die. Independent ERP research firm Panorama Consulting has found for years that organizations chronically underfund migration, and that budget overruns trace back to data and technical issues about a third of the time. The strong answer gets specific fast. Profiling the source data. Deduplication. The vendor master and item master that mean different things across two divisions. Mapping legacy fields to a new structure. The decision about how much history to bring, and the fight with the controller who wants ten years of it. A candidate who says “we extract, transform, and load the data” has described a tool, not a plan. The one who tells you about the weekend they discovered the source system had three active records for the same customer is the one who has been there.

How do you handle integrations? Walk me through a hard one.

Almost no ERP lives alone. It talks to a CRM, a warehouse system, a bank, a tax engine, a dozen bolt-ons. The strong answer covers the method, the timing, and the failure mode. Method is whether they use a native connector, an iPaaS layer like Boomi or Celigo or Oracle Integration Cloud, or a custom API build. Timing is real-time versus batch and why. The failure mode is the part that separates seniors from mids. What happens when the other system is down. How do they handle a record that syncs halfway. Which system owns the customer of record when both think they do. The candidate who only names the tool has integrated on paper. The one who tells you how they handled a nightly sync that silently dropped records for a week has integrated for real.

Describe a time the business wanted something the system should not do. How did you handle it?

Change management and stakeholder judgment, which is half the job and none of the certification. ERP work is political before it is technical. Always has been. Every implementation has a moment where a department head demands a customization that will break the upgrade path, or insists the new system replicate a broken manual process because that is how they have always done it. The consultant who reflexively says yes to the client is a liability. So is the one who reflexively says no. The right answer is a story about a trade. They pushed back, explained the cost, offered an alternative, and either won the business over or documented the decision and moved on. Listen for whether the candidate can disagree with a stakeholder and keep the relationship. That skill does not show up on a resume.

Cutover weekend. Something is wrong Monday morning. What was your plan and what is your first move?

Cutover is the compressed, high-stakes window where the old system goes off and the new one goes live, and it is where preparation either pays off or does not exist. Strong candidates describe the plan before the panic. A cutover runbook with hour-by-hour steps and named owners. A go/no-go checklist. A rollback position. A hypercare window with the right people on call. Then, calmly, the first move when it breaks: triage what is actually broken versus what is user confusion, check whether it is data, config, or integration, and communicate to the business before the business comes to them. The consultant who has never written a cutover plan will hand-wave this question. The one who has lived through a bad Monday will get quieter and more precise, because they remember exactly how it felt.

Probing Platform Depth Without Drowning in Product Trivia

Now you can go platform-specific. The mistake is starting here. Depth questions only mean something once you know the candidate can run a process and a project, because a person who can recite SuiteScript governance limits but cannot run a fit-gap is a developer you have mislabeled as a consultant.

When you do probe depth, do not quiz them on menu paths. Ask for the judgment call that only shows up with real hours on the platform. One question per platform, aimed at the seam where product knowledge meets architecture:

• SAP. Ask how they decide between a standard configuration, a key-user extension, and a developer extension on BTP, and when they would break clean core anyway. The consultant who has never made that call in anger will not have a real threshold. See our SAP consultant interview questions for the deeper module-by-module set.
• Oracle Cloud ERP. Have them walk through a quarterly update that changed behavior they depended on. Fusion updates on Oracle’s cadence, not yours. Anyone who has run it for real has a story about regression testing against a release.
• Microsoft Dynamics 365. Ask when they reach for the Power Platform versus X++ versus a plain configuration. The over-customizer reaches for X++ first, and that answer tells you they will fight the upgrade path. Our Dynamics 365 consultant interview questions break the loop down by app and track.
• Workday. Push on integrations and business-process framework, not just reporting. Studio, Core Connectors, and the security model are where Workday implementations actually strain. For the full loop, our Workday consultant interview questions go deeper.
• NetSuite. Governance limits, saved searches versus SuiteAnalytics, and multi-subsidiary close. A functional consultant should never freeze on OneWorld. Our NetSuite consultant interview questions cover the archetype split.

Running Infor, Epicor, IFS, or Sage? The same principle holds. Ask about the last upgrade or the last integration, and listen for whether they talk about the platform the way someone who has fought with it talks, or the way someone who studied for a cert talks. There is a difference, and you can hear it in about ninety seconds.

Scenario Questions Where the Scars Show

Questions get you answers. Scenarios get you thinking, out loud, in front of you. For a senior hire, spend a full round here. Pick the scenario that maps to the work you actually have on deck.

Scenario one: the dirty migration.

You are moving off a legacy on-prem ERP with fourteen years of history. The vendor master has thousands of duplicates, the item master uses part numbers that mean different things in two plants, and the go-live date is already set. What is your plan for the data?

This is the scenario that exposed a candidate I will not forget. Sharp resume, certified to the ceiling on the destination platform, and every one of those certifications came from greenfield builds where the data started clean. Put in front of a real brownfield mess, the candidate froze, because certs do not teach you how to reconcile a filthy item master under a fixed deadline. The strong answer is a sequence. Profile the data before promising anything. Define ownership and cleansing rules with the business, not for them. Decide what history actually has to come over versus what can live in an archive. Build a reconciliation step that the controller can sign off on. And protect the go-live date by scoping the migration down, not by pretending the mess is smaller than it is.

Scenario two: the customization the software should not be doing.

Halfway through the build, a powerful department head insists on a customization that will work now and break your next upgrade. The executive sponsor is leaning toward giving it to them to keep the peace. You disagree. Walk me through the next hour.

Now you are watching change management under real pressure. The weak candidate either caves or digs in. The strong one gets curious first. What is the underlying need behind the request, and can a configuration or a side-by-side extension meet it without touching the core? Then they quantify the cost in plain language the sponsor understands, which is upgrade risk and future dollars, not technical jargon. Then they offer a path. The consultant who can turn “no” into “here is a better way to get what you actually want” is the one worth the senior band.

Scenario three: the integration that lied.

Two weeks after go-live, finance notices the numbers between your ERP and the warehouse system do not tie out. The integration reports success every night. What do you do?

Diagnostic muscle. A strong candidate does not touch code first. They reproduce the discrepancy, isolate whether it is a mapping problem, a timing problem, or a silent-failure problem where the integration reports success while dropping records. They check the error handling that clearly is not catching something. And they communicate to finance early, because a two-week-old data problem gets worse in silence. The junior instinct is to blame the other system. The senior instinct is to assume the integration is lying until proven honest.

Red Flags That Show Up on Every Platform

Panels rarely miss the loud red flags. They miss the quiet ones, the candidate who sounds fluent on the surface and falls apart one follow-up deep. A few worth watching, across any ERP:

The certification collector. A wall of badges and no scar tissue. Certifications prove someone can pass a test on standard functionality. They prove nothing about whether the person can run a fit-gap, manage a controller, or clean a data set. Certs are a tiebreaker between two experienced candidates, never a substitute for experience. Not a shortcut. When the cert count is high and the failure stories are absent, slow the loop down.

The single-implementation consultant is another one. Somebody who has only ever worked inside one company, on one instance, is not a consultant. They are an admin with real but narrow skills. The configuration choices on a distribution rollout look nothing like the ones a professional-services firm needs, and a person who has only seen one pattern will apply it everywhere, sometimes wrongly.

The one who thinks the software fixes the process. Ask what they do when a client’s business process is a mess. If the answer is “the ERP enforces best practices, so it fixes itself,” walk away. Software does not fix a broken process. It automates it faster. A consultant who does not know that will pave your cow paths at enterprise scale.

Then there is the candidate who cannot name a project that went badly. I mentioned this up top and I will say it again because it is the most reliable tell I have. Real implementations go sideways. A consultant who narrates a career of clean go-lives has either not led the work or is managing you in the interview. Neither is what you want to buy.

Structuring the Loop for an ERP Hire

Three rounds for a mid-level functional consultant. Four for a senior or hybrid. The shape flexes, the discipline does not.

Round one is a short screen for archetype and comp. Are you interviewing for the specialist or the cross-platform hire, and does the band land? Thirty minutes. A good chunk of candidates self-select out here, which saves everyone the calendar.

Round two is the cross-platform core. The six questions above, or the six that matter most for your situation. This round tells you whether the person can run an ERP project on any platform, which is the thing that transfers.

Round three is the scenario round. Sixty to ninety minutes, whiteboard or shared doc, one scenario that maps to your real work. Watch the thinking more than the answer. The deliverable is less important than how they reason toward it under a little pressure.

Round four, for senior hires, is behavioral and stakeholder-facing, with the finance or operations leader who will actually depend on this person. ERP consultants live or die on stakeholder management, because every implementation is a series of decisions about whose process wins. A consultant who cannot manage that tension will struggle no matter how clean their configuration is. Skip the take-home unless you are testing one specific technical skill, and if you do assign one, keep it to ninety minutes and pay for their time.

Most ERP hires close on the scenario round, not the technical quiz. That is the round that shows you the human being who will be in the room when the cutover goes wrong, when finance is asking why the numbers do not tie, and when the answer has to come from judgment rather than a certification study guide.

Hiring-Manager Questions We Get About ERP Interviews

Should we hire a consultant who specializes in our platform, or a cross-platform generalist?

It comes down to your roadmap. If you are settled on one ERP and building depth, hire the specialist and weight the loop toward platform scars. If you are migrating, multi-ERP, or undecided, the generalist who has survived several cutovers is usually the safer bet.

The common mistake is hiring a deep single-platform specialist for a migration, then discovering they have only ever worked greenfield on that one product. Migration is its own skill. It transfers across platforms far better than product configuration does.

How much should a stack of ERP certifications move the needle?

Less than most panels think. A certification proves someone studied the standard product. It says nothing about whether they can run a fit-gap, clean a data set, or tell a stakeholder no. Treat certs as a tiebreaker between experienced candidates, never a substitute for the war stories.

Weigh what the certs sit next to. A senior consultant with two certs and five real implementations beats a junior with six certs and one. Every time.

How do we test ERP skills if we cannot give a candidate access to a live system?

You do not need a live system. Test judgment, not clicks. The scenarios in this post work entirely in conversation, because the signal you want is how the candidate reasons through a dirty migration or a bad integration, not whether they can find a menu path.

If you want a hands-on check, a scoped ninety-minute exercise on a single realistic problem beats a leetcode-style quiz. Pay for the candidate’s time, and keep it tied to work they would actually do.

Is an ERP consultant the same as a business analyst or a solution architect?

No, and the overlap causes real hiring mistakes. A business analyst gathers and documents requirements. An ERP consultant configures and implements against them. A solution architect owns the end-to-end system design across applications. The titles blur, so interview for the actual deliverable, not the label.

If what you really need is the architecture-level hire, our enterprise architect interview questions are the better fit. Match the questions to the work, not the job title on the req.

Contract or direct hire for an ERP implementation?

For a net-new implementation, contract or contract-to-hire is usually right. The work concentrates in the first six to twelve months, and the best implementer is not always the person you want owning steady-state support afterward.

If you are filling a permanent seat to own the platform long-term and you already have someone handling day-to-day, direct hire fits better. We run both models through our contract staffing and direct hire staffing desks, and the choice usually comes down to how much of the work is the build versus the run.

How long does it take to hire an experienced ERP consultant in 2026?

Plan on three to six weeks for a functional consultant on a common platform, and longer for scarce combinations like S/4HANA conversion leads or hybrid functional-technical hires. Our average IT time-to-hire runs about 17 days, but ERP specialization sits at the tighter end of the market.

If your timeline is genuinely short, scope the role down to the specialist skill you need most and bring in the rest on contract. Trying to hire one person who is deep on everything is the fastest way to a stalled search.

Hire the Consultant Who Fixes the Process, Not the Software

Strip away the logos and ERP hiring comes down to one question. Can this person walk into a business that does not fully understand its own processes, on a platform that will not do everything the business wants, and get to a working system without paving the mess? That is the job. It looks the same on SAP, Oracle, Workday, Dynamics, and NetSuite, and the interview that finds it looks the same too.

Weight the loop toward judgment first, platform second. Test the fit-gap, the migration, and the stakeholder conversation before you test the product depth. Watch how the candidate handles the failure they did not expect to be asked about. That is the signal.

If you want a second read on a loop you are about to run, or you would rather hand the search to a team that has placed ERP consultants across platforms for close to two decades, talk to our team. For the broader practice, see our ERP recruiters and IT staffing pages. ERP searches are not slow because the market is empty. They are slow when the interview tested for the wrong thing.