Grand Rapids, MI
ERP Project Manager recruiting based on accountable delivery experience. Crosscheck recruits ERP & Enterprise Applications candidates for contract, contract-to-hire, and permanent roles tied to Grand Rapids.
What We Place
Representative roles
Platforms and technologies
Our Approach
This editorial hiring guide starts with sourced Grand Rapids business context. Grand Rapids' 2024 Community Master Plan describes a local base in manufacturing, biopharmaceuticals, medical devices, life sciences, food processing, and production technology. The official plan gives technical searches concrete laboratory, factory, and product settings. An ERP Project Manager search should identify the platform, modules, business units, implementation partner, current system, delivery phase, budget, timeline, and governance. The role may lead a full implementation or one constrained workstream, and the brief should say which.
Define the systems, delivery stage, operating boundary, and ownership expected from the ERP Project Manager
Screen candidates for evidence of cross-functional ERP scope, workstreams, partners, budget, risk, testing, data, cutover, readiness, and governance
Separate direct delivery experience from adjacent product, project, or consulting exposure
Support contract, contract-to-hire, and permanent searches across the US and Canada
Start the search
Include the business context, systems, delivery phase, work model, compensation, and interview timeline. A Crosscheck search lead will use that context to calibrate the role before sourcing begins.
Local Market Brief
Define ownership across process design, configuration, development, integrations, data migration, security, testing, cutover, training, change, and support transition. Record decision rights among business owners, technology teams, vendors, and executives. The three sourced Grand Rapids contexts below turn that scope into intake and screening decisions. They do not measure current vacancies, candidate supply, or Crosscheck client activity.
Editorial market scenario
Give candidates the integration, approval, audit, and change-management boundaries during the interview. Ask for comparable decisions from prior work. This is planning guidance, not measured local demand.
Editorial industry scenario
An industrial brief should show how software, data, and infrastructure connect to plants, equipment, schedules, quality, and frontline users. Confirm that this context applies to the employer before using it in the search.
Screening focus
We match experience to the actual phase of work, including discovery, configuration, migration, integration, rollout, and post-launch support.
Published labor benchmark
BLS does not publish an occupation matching ERP Project Manager. Crosscheck uses Computer Systems Analysts (15-1211) as the closest published broad benchmark; it is not a count or pay estimate for this exact specialty.
BLS OEWS May 2025, published May 15, 2026
Published metro employment
1,140
BLS publishes a narrower metro employment estimate for the proxy occupation. Screen for adjacent experience that transfers without lowering the production bar. The estimate equals 1.899 jobs per one thousand across the metro workforce.
Employment concentration
0.57 location quotient
Grand Rapids-Wyoming-Kentwood, MI reports a below-national employment concentration for this proxy occupation. Decide which requirements justify a wider regional or remote search.
Annual wage reference
$63,550 to $144,150
The metro median is 8% below the national Computer Systems Analysts median. Do not use the gap to discount niche platform or domain experience. BLS reports a $97,210 median for the proxy occupation in Grand Rapids-Wyoming-Kentwood, MI.
Hiring brief scenarios
These scenarios connect location context to role responsibilities. Use them as prompts to verify with the employer, not as measures of Grand Rapids demand, clients, or candidate supply.
Sourced advanced manufacturing context
The Grand Rapids Community Master Plan identifies local concentrations in metals, plastics, production technology, automotive manufacturing, and office-furniture production. Translate the operating context into workstreams, process owners, milestones, acceptance evidence, and constraints on outages or business calendars. Ask how unresolved decisions are surfaced and closed. Advanced factories can join product configurations, materials, suppliers, machinery, production orders, robotics, inspections, serial or lot history, inventory, maintenance, and cost.
Evidence to request: Review an ERP plan or RAID log with workstreams, dependencies, owners, dates, decision gates, and measurable acceptance criteria. Trace the product from released engineering and sourced material through equipment, production, inspection, serial or lot evidence, inventory, maintenance event, shipment, and variance owner.
Sourced medical devices and life sciences context
The plan describes biopharmaceutical, medical-device, and life-sciences concentrations tied to the Medical Mile. Set dependencies among the ERP, source systems, interfaces, reports, identity, data loads, testing cycles, sites, and vendors. Require a comparable example where the critical path changed. Medical and life-sciences work may connect research samples, clinical data, instruments, device configurations, product quality, validation, manufacturing transfer, complaints, and regulated records.
Evidence to request: Use a conversion, integration, or testing failure and score triage, ownership, options, schedule effect, and closure evidence. Name the research or device outcome, sample or patient data, approved configuration, instrument interface, validation test, quality gate, production transfer, complaint path, and approver.
Sourced food processing and production technology context
Grand Rapids' plan also names food processing and production technology among the city's and region's industry concentrations. Define budget, schedule, risk, quality, readiness, and stabilization controls. Candidates should explain forecasting, escalation, test exit, go-live approval, rollback, and support handoff. Food-production systems can connect recipes, ingredients, suppliers, equipment, batches, quality results, allergens, inventory, recalls, shipments, and financial records.
Evidence to request: Ask for a cutover or deployment the manager led, including prerequisites, command structure, validation, business communication, and stabilization. Trace the food product from approved recipe and ingredient source through equipment, batch, quality and allergen checks, inventory, shipment, recall evidence, settlement, and release owner.
Interview scorecard
Ask each candidate the same core questions. Score the evidence, ownership, and judgment in the answer instead of relying on job-title or keyword matches.
1. ERP Project Manager: SAP
Choose an SAP decision from your work as ERP Project Manager. Which constraint changed the design, and what evidence supported the result?
Use the answer to assess plant processes, inventory, planning, integrations, cutovers, and support for operating teams. The manufacturing and operational systems context is an editorial scenario, not a measured claim about Grand Rapids.
2. ERP Program Manager: Oracle
Describe project work you completed as ERP Program Manager involving Oracle that did not follow the original plan. What did you own, and how did you correct it?
Use the answer to assess plant processes, inventory, planning, integrations, cutovers, and support for operating teams. The manufacturing and operational systems context is an editorial scenario, not a measured claim about Grand Rapids.
3. ERP Deployment Lead: Workday
For a Workday system you supported, explain the handoff, operating limits, and measures used after launch. Where did your responsibility begin and end?
Use the answer to assess plant processes, inventory, planning, integrations, cutovers, and support for operating teams. The manufacturing and operational systems context is an editorial scenario, not a measured claim about Grand Rapids.
Need the full ERP Project Manager evaluation guide?
The role guide covers technical scope, interview questions, and evidence checks once, without repeating the same material on every city page.
FAQ
For qualified exclusive searches in our core disciplines, Crosscheck targets a first candidate slate within 48 hours after a completed intake. Contract placements include a 40-billable-hour replacement guarantee, and permanent placements include a 90-day replacement guarantee, subject to the signed agreement.
Continue your research