Short answer: the plants replacing a 15-year-old ERP system rarely need more IT headcount. They need a handful of people who can stand between the shop floor and the software and speak both languages. That usually means an ERP functional analyst who knows manufacturing modules, an integration engineer who can move data between the ERP and the machines, and a manufacturing or industrial engineer with enough system literacy to define what “correct” looks like in a routing.
Hiring managers keep posting for the wrong seat. They write a generic “ERP Analyst” req, get 300 applicants who configured financial modules at an insurance carrier, and none of them can read a bill of materials. Here’s what the roles actually require, what the market pays, and when to hire them.
Why ERP Modernization Turned Into a Hiring Problem
The spending decision came first, and the staffing decision is still catching up. In a 2025 Deloitte survey of 600 manufacturing executives, 80% said they planned to put 20% or more of their improvement budgets into smart manufacturing initiatives, with the money concentrated in foundational things: sensors, data analytics, automation hardware, cloud infrastructure. An ERP replacement is usually the spine that work hangs off. You can buy machine-level sensors all day, but if the production data lands in a system that can’t schedule against it, nothing on the floor changes.
That creates demand for a skill profile most manufacturers didn’t staff for. The old ERP administrator ran a stable, on-premise system: user accounts, month-end closes, an occasional report request, a vendor ticket when something broke. The person needed for a modern rollout does something closer to systems design. They map how a work order actually moves through the plant, decide which of those steps the software should enforce, clean up 20 years of accumulated item-master garbage, and then get a maintenance planner who has used the same green screen since 2009 to trust a tablet.
Picture the way this shows up in a real plant. A 400-person contract manufacturer decides to replace an on-premise system that’s been patched since 2011. The controls lead already has a full plate keeping two robotic cells running. The quality manager owns the CAPA process and has never seen a database schema. The IT manager supports 60 laptops, a domain controller, and a phone system. None of them is wrong for their job, and none of them can define how a routing should be structured so that labor reporting and costing both come out right. So the decision defaults to the integrator’s template, and 14 months later the plant is running a configuration nobody internally can explain or change.
The talent math is not friendly. Deloitte and The Manufacturing Institute projected that U.S. manufacturing could need as many as 3.8 million new workers between 2024 and 2033, with roughly 1.9 million of those jobs going unfilled if the skills and applicant gaps hold. The shortage isn’t spread evenly. Roles that combine production knowledge with digital fluency are the tightest part of the market, and they’re exactly the roles an ERP project depends on.
What a Modern ERP System Actually Looks Like on a Plant Floor
Before you can write a job description, you have to be specific about what the new system does that the old one didn’t. Otherwise the req describes a maintenance job for software that no longer behaves that way.
The practical differences that drive hiring:
- It’s integrated, not isolated. The ERP exchanges data with MES, SCADA/historian systems, warehouse scanners, quality systems, and often a customer portal. Those connections run over APIs and middleware rather than overnight file drops.
- It’s configured, not custom-coded. Modern platforms expect you to set up workflows, approval rules, and costing methods through configuration screens. Heavy custom code is now a liability, because it breaks on the vendor’s quarterly update cycle.
- It’s continuous. Cloud deployments update on the vendor’s schedule. Somebody has to regression-test the pieces that matter before each release, permanently, not once at go-live.
- It’s real-time and mobile. Inventory transactions happen at the point of the move, scanned on the line. That only works if the master data underneath is right, which is a people problem more than a software one.
- It reports on itself. Embedded analytics, OEE dashboards, and scheduling engines mean somebody has to own data definitions, or three departments will calculate scrap rate three different ways.
Vendor comparisons of the top ERP systems for manufacturers tend to sort platforms by exactly these dimensions: depth of production planning, how the MES integration is handled, whether shop-floor data collection is native or bolted on. Read that landscape as a staffing spec, because it is one. A platform with strong native MRP and weak integration tooling means you need a stronger integration engineer. A platform that leans on partner-built extensions means you need someone who can manage a vendor relationship as well as a codebase.
The Technical Skills Worth Hiring For
Five capability areas cover most manufacturing ERP programs. Very few candidates carry all five, and a company that insists on finding one who does will spend nine months not filling the seat.
ERP functional configuration, at the module level. This is the core hire, and the resume screen is narrower than most recruiters realize. “Experience with NetSuite” is not a qualification. Experience configuring work orders, routings, backflush rules, and standard cost rollups in a discrete or process environment is. Ask a candidate how they’d handle a phantom BOM, or what happens to WIP valuation when a routing changes mid-order. The answer separates the functional analysts from the people who ran user provisioning.
Integration and interface work. REST and SOAP APIs, middleware platforms, EDI for customer and supplier transactions, and increasingly OPC UA for machine-level data. In plants with older equipment, this person also has to be comfortable with the unglamorous parts: a PLC that only speaks Modbus, a labeling system with a flat-file interface, a legacy scale nobody has updated since the plant opened.
Data engineering and migration. The single most underestimated line item on any ERP project. Somebody has to reconcile duplicate part numbers, resolve units of measure that don’t convert, decide which of 40,000 inactive items to bring over, and build the validation that proves the loaded data matches the source. SQL fluency is table stakes. Judgment about what to leave behind matters more.
Shop-floor systems literacy. Not necessarily a controls engineer, but someone who understands what a work center is, how a scheduler treats setup time, why the operator at the press brake will not scan a label if the terminal is 30 feet from the machine. This is where manufacturing and industrial engineers earn their place on the project team. The Bureau of Labor Statistics puts the median annual wage for industrial engineers at $101,140 as of May 2024, with employment projected to grow 11% from 2024 to 2034 and about 25,200 openings a year. That’s a faster-than-average growth rate in an occupation manufacturers were already competing for.
Reporting, analytics, and OT security. Somebody owns the semantic layer: what counts as on-time delivery, how yield is computed, which transaction date drives the KPI. And once the ERP talks to the plant network, the attack surface changes. A controls network that used to be air-gapped is now integrated, and somebody needs to have thought about segmentation before the auditor does.
For the analyst-shaped seats, the market comparison point is the computer systems analyst classification, which BLS reported at a median wage of $103,790 in May 2024 with 9% projected growth through 2034. Manufacturing employers competing for those candidates are bidding against software, insurance, and healthcare IT for the same people, usually without the same remote-work flexibility.
The Non-Technical Skills That Decide Whether the Project Lands
Technical screening gets you a candidate who can configure the system. It doesn’t tell you whether the plant will use it.
The trait hiring managers describe most often is floor credibility. The candidates who succeed can stand at a work center during second shift, watch how a transaction actually gets recorded, and notice that the operator writes quantities on a sticky note and enters them all at break. That observation is worth more than any requirements workshop, and you won’t get it from someone who won’t leave the conference room. It’s also a reason to weigh a maintenance planner or a production supervisor who taught themselves SQL above a polished consultant with no plant time. The first one can learn the software. The second one has to earn trust from people who have watched two failed rollouts already.
Change communication is the second one. A modern ERP rollout takes work away from some people (no more manual spreadsheets for the planner) and adds work for others (the operator now scans every move). Whoever leads the functional side has to explain that trade honestly, not sell it. Plants can smell a pitch.
Third: the ability to say no. Every department arrives with a wish list, and a functional owner who approves all of it produces a customized system that can’t take a vendor update. The skill being screened for here is negotiation under pressure from people senior to you, which is hard to test in an interview and easy to check in a reference call. Ask a former colleague which requests the candidate turned down and how that conversation went.
The demand curve for hybrid skills shows up in the job posting data. Reviewing five years of manufacturing postings, Deloitte and The Manufacturing Institute found a 75% jump in demand for simulation and simulation-software skills, concentrated in technology-enabled production and testing roles. That’s one narrow example of a broader pattern: the technical baseline for a “manufacturing” job keeps moving, and the postings show it before the job titles catch up.
How to Sequence the Hires
Timing decides cost. Bring people in too late and you pay a systems integrator to make decisions your own staff should have made, then pay again to unwind them.
- Before software selection: hire or designate the functional owner. This person should be in the room for demos, because they’re the one who has to live with the answer. Hiring them after the contract is signed means inheriting somebody else’s assumptions.
- During design and build: integration engineer and data migration lead. These are the most contract-friendly roles on the project, because the workload is genuinely front-loaded. A 9-to-14-month contract or contract-to-hire fits the shape of the work.
- Sixty days before go-live: super-users from the floor, backfilled. This is the step companies skip. If your best scheduler is training 40 people, someone has to do the scheduling, and it isn’t going to be them at 11 p.m.
- After go-live: the permanent seat. Continuous release cycles, integration monitoring, and report ownership are ongoing work, not a project phase.
Two staffing realities worth planning around. First, the post-go-live retention risk is real: a functional analyst who just completed a successful implementation on a major platform has a resume the market wants, and recruiters know the go-live date. Decide before launch whether you’re retaining that person and price it accordingly. Second, contract talent works well for migration and integration, poorly for the functional owner role, because that seat depends on institutional knowledge that walks out when the contract ends.
Short Answers
Do we need to hire before we pick a platform?
Hire or assign the functional owner first. The integration and data roles can wait until the platform is chosen, since the required toolset depends on it.
Can our existing ERP administrator grow into the new role?
Sometimes, and it’s usually worth testing. The gap is rarely intelligence. It’s exposure to integration architecture and data modeling. A candid skills assessment plus a training budget costs less than a six-month external search.
Should the ERP lead report to IT or to operations?
Operations, in most plants, with a dotted line to IT. The failure mode of an IT-owned rollout is a technically clean system that nobody on the floor uses.
How do we screen for real manufacturing ERP experience?
Ask process questions, not tool questions. How do they handle a BOM change on an open work order? What’s their approach to cycle counting during cutover? Which data did they decide not to migrate, and why? Candidates who only configured finance modules answer these vaguely.
Contract or direct hire?
Contract for migration, integration, testing, and temporary backfill of floor super-users. Direct for the functional owner and the post-go-live systems role.
How long does it take to fill these roles?
Longer than the project plan assumes. Functional analysts with recent manufacturing implementation experience typically take 60 to 120 days to source, interview, and start, and that’s before any notice period. Build the search timeline backward from the design phase, not from go-live.
Do we need someone with experience on our exact platform?
It helps, and it isn’t a hard requirement for the functional owner. Someone who ran a full lifecycle on a comparable manufacturing platform transfers well, because the underlying concepts (MRP logic, costing, routings, cutover mechanics) are consistent. Platform-exact experience matters more for the integration and technical configuration seats.
What does the market actually pay?
Use the BLS medians above as a floor, then add for platform-specific experience and location. Candidates with recent hands-on manufacturing implementations on a major platform command a premium because the supply is small and the projects are visible.
Where to Start
Write the requisition for the specific work in front of you, not for a job title. If your bottleneck is 40,000 dirty part records, hire the data person first and worry about the configuration expert later. If your plant runs 12 machines that need to report cycle counts automatically, the integration engineer is the constraint.
Three things to decide this quarter: who owns the functional side and whether they’re already on payroll, which parts of the project are genuinely temporary and belong on contract, and what you’ll do to keep your implementation lead in the 90 days after go-live. The plants that get ERP modernization right tend to be the ones that staffed it as an operations program with technical people in it, not as an IT project with operations consulted.
