Last updated: November 21, 2026
By Robert Ardell, Co-Founder and Strategic Advisor, KORE1
The best Epicor consultant interview questions hand a candidate a failing situation in a named product and release, then listen for where they look first. Anybody can define a BPM. Far fewer can find the one slowing the shop floor.
A precision machining shop in Rancho Cucamonga hired an Epicor consultant last spring after a loop everybody called excellent. He walked the panel through Application Studio layers. He explained a method directive versus a data directive without notes. He named the Kinetic release he’d last upgraded. Nobody asked him to diagnose.
Week three, labor entry on the shop-floor terminals went from about one second per save to about fourteen. Twenty-two terminals. Operators started writing hours on paper again.
The cause was a directive he had built himself, which emailed the planner whenever logged hours passed an estimate. It sent that email from inside the save. When the mail relay got slow, every terminal waited on it. Eleven days to find, partly because the one person who knew where to look was the one who’d written it. The fix took an afternoon, and it was dull: set a flag in the save, send the email later from a scheduled process.
That’s the case for this page. The loop graded vocabulary. The job was diagnosis.

What follows is the list I’d hand a panel working with our Epicor consultant staffing desk, and the desk gets paid when a client hires through us, so discount my opinions to taste. Every question works without us. Scoping the search, the five different Epicor products, and the pay bands are all in our guide to hiring an Epicor consultant, so this page is only the interview. The platform-neutral screen sits in our ERP consultant interview questions, and the posting that draws these candidates is in the Epicor consultant job description template, or the ERP consultant job description template if the seat spans platforms.
What This Interview Is Really Testing
An Epicor consultant interview should establish three facts about a candidate: which Epicor product they actually ran, which release it was on, and whether they can find a fault in the customization layer without help. Tenure and tool vocabulary prove none of the three.
Part of the reason is that Epicor’s calendar keeps moving, and an answer that was current in 2023 can be a liability now. The vendor has published most of the dates, so use them.
| When | What Epicor Did | The Question It Earns |
|---|---|---|
| Release 2025.2 | Last Kinetic release to include the Smart Client (classic screens) | “What did you rebuild before it went away?” |
| Release 2026.1 | Browser forms replace the Smart Client; a Power Tools Client stays for DMT, Functions, Advanced Print Routing, and Service Designer | “Was your last go-live on browser forms or classic?” |
| May 2026 | Kinetic moves from semi-annual releases to a monthly CI/CD cadence; Epicor Functions arrive in the browser with release 2026.100 | “What have you done by Friday when an update lands Tuesday?” |
| January 2028 (tentative) | Final on-premises Kinetic release, 2028.1; Active Support through December 31, 2029, Sustaining Support from January 1, 2030 | “Have you moved a customer from on-premises to the cloud?” |
| May 2028 (tentative) | Final on-premises Prophet 21 release, 2028.1; Active Support through June 30, 2029 | “Which Prophet 21 rules would you check before that date?” |
Those come from Epicor’s Kinetic Browser UX page, its 2026.100 release announcement, and the January 2026 schedule of final on-premises releases. Epicor calls the 2028 dates tentative. Treat them that way.
KORE1 averages 17 days to fill IT roles, and 92% of our placements are still in the seat a year later. I can’t prove it from a dataset, but the Epicor hires who come apart in the first quarter, in the ones I’ve seen, tend to come out of loops that rewarded fluency.
The First Fifteen Minutes, Before Any Scenario
Boring facts first. Four questions, asked plainly.
- Which Epicor product, which release, and was it cloud, private cloud, or on-premises when you left?
- Who applied the updates, and who tested them? Two different people, ideally.
- What did you build that somebody else is still maintaining?
- Name one customization you would build differently today, and say what changed your mind.
The third one is quiet. It matters. People who have lived with their own work for two years answer it in detail, and people who built and left answer it in generalities.
Customization Layer Questions
Epicor lists Application Studio, Automation Studio, the SDK, BPMs, BAQs, and Epicor Functions as the toolset for tailoring Kinetic, and the loop should touch at least three of them. Skip the definitions. They’ve been rehearsed.
“Labor entry went from one second to fourteen after a directive shipped. Where do you look?”
Give it as a story, with the twenty-two terminals and the paper timesheets. Then wait.
Strong candidates ask which directive type it is before anything else. A directive that runs inside the save, the in-transaction kind, makes every save wait for whatever it does, so the second question is what the directive reaches outside the database to do. Email, a web service, a file share. They reproduce it in a test copy, trace the save, and find the call. Then they fix it by getting the slow thing out of the transaction, with a flag now and the work done later. The best ones volunteer that the person who wrote the directive is the worst person to review it.
Weak answers start with the server. More memory, a bigger box, a call to the host. Sometimes that’s right. Not here. It was a mail relay.
“When does logic belong in a Function instead of a directive?”
Short version. A directive fires because something happened, a save or a record changing, and it can be the thing that refuses the save. A Function runs because something called it, from a directive, from a REST call, or from a schedule. So logic that several places need, or that should run on a timer, wants to be a Function, and logic that has to be able to say no belongs in a directive.
Epicor added Functions to the browser in release 2026.100, so a candidate who left a plant before then may have met them only in the Power Tools Client. Fine. What you’re listening for is a reason. “Functions are the new BPM” is a slogan. So is “whatever the newest tool is.” Neither one is a reason.
“Somebody added a column to a BAQ on Friday. By Monday three things are wrong. How could you have known?”
Epicor’s own browser page advertises BAQ as a source for another BAQ, which is lovely until one query feeds five dashboards and another query. So a good answer is a dependency answer. Before anybody edits a shared query, find everything that reads it, other BAQs, dashboards, BAQ reports, and any outside tool calling it over REST. Copy it instead of editing it when the consumers are unknown.
“I’d have tested it” misses the point. Testing what you changed never finds what you didn’t know was attached.
- How do you find every consumer of a query you didn’t write?
- Who is allowed to change a BAQ in production at your last employer, and was that written down?
- Tell me about a customization you retired. How did you know it was safe?
Planning, Scheduling, and the Plant Floor
Release 2026.100 separated the SHOPLOAD data from the MRP scheduling run and added a Force Infinite Queue option at the part revision level. Epicor’s own explanation is that manufacturers don’t all adopt advanced scheduling the same way or on the same timeline. Good. It’s also a free interview topic.
“Finite or infinite scheduling: which do you turn on first?”
Neither, until you know which resource actually limits delivery. Constraint first. Strong candidates start there, a heat-treat oven or a five-axis machine or a single inspection cell, and apply finite scheduling there first, because a finite schedule is only as honest as the routing times underneath it and most shops have a few routings they trust and many they don’t. They’ll talk about moving in stages. Some will mention that infinite is the right answer for a work center that is never the bottleneck.
The weak answer is “finite is more accurate, so everywhere.” Accurate in theory. In practice a finite schedule built on routing times nobody has measured since 2019 is a fast way to produce a confident wrong date.
“MRP wants to buy a part you can see on the shelf. Why?”
There are about five honest causes, and the candidate should reach two or three without help. Stock sitting in a bin or warehouse flagged as non-nettable. A lead time that makes the shelf quantity arrive too late to matter. A firm job demanding it earlier than the schedule shows. Demand from a job nobody needs anymore. Or a quantity on hand that physically doesn’t match the system, which is the one that costs money.
A strong answer is a sequence of questions, in the order a person would check them. A weak answer is “I’d rerun MRP.” Rerunning is the last move. Checking comes first.
Costing has its own questions and they live in the hiring guide, along with the rebuild-triage exercise for classic customizations. Not repeated here.

Hosting and Release Questions That Didn’t Exist Two Years Ago
Starting with the May 2026 release, Epicor says cloud customers receive smaller, more frequent updates, which it frames as easier to review and absorb. Maybe so. It also means somebody has to review and absorb them every month.
“An update lands Tuesday. What have you done by Friday?”
A strong candidate describes a rhythm. Run the update against a test or preview environment first. Replay the regression set, which for an Epicor shop means the directives, the Functions, the BAQs that feed dashboards, and the customized screens. Read the release notes for anything touching the tables those use. Tell the floor what changes. Write down what was checked.
NetSuite shops have lived with scheduled releases for years, and the good ones preview and regression-test every time, which our post on NetSuite release testing walks through. A written change-control procedure from an ERP firm that serves regulated manufacturers goes further and treats every vendor release as a change to the operating environment, assessed against the preview before it reaches production. Nobody needs to quote that. They need to have thought about it.
Weak answers wait for production to complain. It does. Loudly.
“You moved one customer from on-premises to the cloud. What did you find in the customizations?”
Listen for specifics. Anything that reached around the application, such as direct database reads, a file share, or a scheduled script running on the server, tends to need a redesign when the hosting changes. Candidates who’ve done the move have a list, and the list is usually longer than the customer expected. Candidates who haven’t done it describe the migration tooling.
If your own system is staying on-premises past 2029, say so in the interview. Some candidates want that work and some don’t, and you’ll learn which from how they react. Upgrade planning and the staffing around it is its own subject, covered in our page on ERP upgrade staffing.
Distribution Seats: Prophet 21 and Its Neighbors
Prophet 21 is a different product with a different extension model. Epicor describes DynaChange as an extensibility suite that adds business logic to the interface without altering application code, and it’s where a lot of Prophet 21 customization lives. Ask a Prophet 21 candidate about that. Never routings.
“Reps keep overriding contract prices at order entry. Rule, report, or people problem?”
The answer I like starts with a number. How many overrides, by whom, at what margin cost, because a handful of overrides by two senior reps is a conversation and four hundred a month by everyone is a gap in the system. Then comes the choice. A rule can constrain overrides by user or product group or margin floor, a report can make them visible to the sales manager, and training fixes neither if the incentive is wrong.
The weak candidate builds the rule in the first minute. Rules are cheap. Hard feelings about them aren’t.
Eclipse, BisTrack, and CMS candidates each need their own list, and we write those with the client once we know which product is running. Don’t borrow this section for them.
When the Plant Is Regulated, and When a Tool Writes the Code
Skip this section if nothing you build has to be validated. If you make devices, food, pharmaceuticals, or aerospace parts, it’s most of the reason the pool is small.
“A device customer wants a validation assessment for every change to a validated screen. What does that do to your estimate?”
Bigger. The candidate should say by how much, or at least say that someone else should. On a NetSuite integration proposal we have benchmarks from, written for a mid-market pharma manufacturer, validation ran about 30% of the hours. The reason is that custom code inside a configured product, a BPM or a Function in this case, is still bespoke, and GAMP 5 assesses software by component rather than letting the whole product’s category cover everything inside it.
A candidate with regulated experience says that in their own words. A candidate without it says “we’d just document it.” That’s the sound of an audit finding.
“Prism Developer drafts rules and data views from a prompt. Who writes the tests?”
A person writes the tests. That’s the answer. The reason is independence, since a test generated by the same means as the code it checks can’t catch that code’s blind spots. Epicor describes Prism Developer for Application Studio as generating events, data views, rules, and interface components from natural-language prompts, with a preview and validation step before anything is merged. Good. A validated plant needs more than that. A named person accountable for every deliverable, generation against an approved design rather than a loose prompt, and review by somebody other than the author.
Don’t require Prism experience. It’s new, and anyone claiming years of it is telling you something other than what you asked.
How to Score the Answers
Write the strong and weak signals down before the first interview. The U.S. Office of Personnel Management’s guidance on structured interviews gets the principle right: every candidate gets the same predetermined questions in the same order, and every answer is rated on the same scale. This is the sheet we give clients.
| Question Area | Strong Signal | Weak Signal |
|---|---|---|
| Product and release | Names product, release, and hosting without prompting | “Epicor, a few versions” |
| Directives and Functions | Asks what the logic reaches outside the database to do | Blames the server first |
| Shared queries | Finds every consumer before editing | “I’d test my change” |
| Scheduling | Starts at the real constraint, adopts in stages | “Finite everywhere” |
| MRP troubleshooting | Checks nettable stock, lead time, and firm demand in order | “Rerun it” |
| Release handling | Previews, regression-tests, documents, tells the floor | Waits for production to complain |
| AI-assisted builds | A person writes the tests; someone else reviews | “The tool handles it” |
Two scorers, separate sheets, one to four per row, compared only after both finish. A three-point gap on a row means the interviewers heard different answers, and sorting that out is where the useful ten minutes of the debrief go.
Answers That Cost a Candidate the Offer
Four, and they’re consistent. The first is a story in which the vendor’s support line fixed everything, because the person you’re hiring is the one who gets called before support does. Next is a candidate who built something large and can’t say who maintains it now. Third, any account of testing in production, told as though it were a skill. And the last is quieter. Ask what they’d do in week one, and if the answer is a rebuild plan before they’ve looked at a single directive, they’ve decided what your system needs without seeing it.
If You’re the Candidate
Bring one fault you found yourself and one you caused. Hiring managers have heard the polished version of every go-live, and the fault you caused is the most believable thing you can say. Know your release number cold. Know your going rate too, and the Epicor consultant salary guide shows where this seat lands in 2026, with the ERP consultant salary guide as the cross-platform view. If a panel only asks about definitions, ask them what is actually broken. That tells you whether you want the job.
Before You Schedule the Loop
How long should the technical round run?
Seventy-five minutes covers four scenarios with real follow-ups, which beats eight rushed ones, because the useful information comes from the second and third question on a single failing directive, not from breadth.
Cut a scenario before a follow-up. Always.
Should they build something live in Application Studio?
Not unless the candidate gets a prepared sandbox, since watching a stranger click through an unfamiliar tenant tests nerves rather than judgment.
Hand them a directive definition, a trace excerpt, or a BAQ and ask what they notice. Ten minutes of reading aloud tells you more than forty of clicking. Plenty of strong people click slowly.
A NetSuite or SAP consultant applies. Can they pass this loop?
Sometimes for functional seats, since order-to-cash, procurement, and close logic transfer well between platforms, but they will miss the customization-layer questions until they have spent a quarter inside Epicor’s own tools.
Run the platform-neutral screen first. Our SAP S/4HANA consultant interview questions and Dynamics 365 consultant interview questions show how the same ideas look elsewhere.
What does an Epicor consultant cost in 2026?
Contract rates run $85 to $165 an hour and direct-hire base runs roughly $110,000 to $165,000 for an experienced functional consultant, according to our placement data, with product and customization depth moving the number most.
Pull a band for your own metro with the salary benchmark assistant before the req goes out.
We run Kinetic in one plant and Prophet 21 in the distribution arm. One loop or two?
Two, because a Kinetic costing lead and a Prophet 21 pricing specialist share a vendor and very little else, and one panel asking both the same questions will mark both down.
Share the screening block. Split everything after it.
Bring Your Own Failure to the Interview
The directive story works because it’s specific to a real system. Yours should be too. Pull the last incident your floor still talks about, the slow screen or the wrong report or the update nobody tested, strip the names, and put it in front of the candidate. Ten minutes. They sort themselves.
We’ve placed technical talent across 30+ U.S. metros since 2005, our recruiters average 15+ years in the business, and the Epicor work tends to land with manufacturers and distributors who have a small IT team and a system everyone leans on. Many of those seats start on contract staffing terms and convert later. If you’d like a second read on your question set, or a slate of consultants who’ve already handled questions like these, talk to a recruiter on our ERP desk. Planning an Epicor build-out for a plant floor? Our look at manufacturing ERP staffing covers the wider crew.

