ERP Systems Administrator
Overview
Moonshot builds the power infrastructure that enables AI. Our electrical distribution equipment goes into the largest AI data center deployments in the country; our customers include the companies building the next generation of AI compute. We are in hypergrowth, moving into a purpose-built manufacturing campus near Dallas.
This role is one of two ERP Systems Administrator seats on the team. Each administrator owns a defined set of modules and functional areas, and both are expected to understand the full platform well enough to cover for one another. This seat is focused on the production and operations side of ECI M1: inventory, purchasing, jobs, scheduling, timecards, shop floor, and quality. This is a hands-on, execution-focused role responsible for keeping these modules configured correctly, running cleanly, and aligned with how the business operates on the floor. As Moonshot scales rapidly and moves into a new manufacturing campus, this role ensures the production layer of our ERP foundation stays disciplined, accurate, and ready to grow.
Key Responsibilities
• Production Module Ownership and Configuration: Own the configuration, maintenance, and continuous improvement of ECI M1 modules covering inventory, purchasing, jobs, scheduling, timecards, shop floor execution, and quality. Ensure module settings, workflows, and system controls reflect current business processes and production realities. Coordinate with your peer ERP Systems Administrator, who owns the finance and order management side of the platform, to maintain consistency and clean handoffs across the full system.
• MRP and Manufacturing Process Support: Apply working knowledge of MRP concepts, including demand planning, master scheduling, capacity management, work orders, and bill of materials, to translate production requirements into structured ERP configurations. Partner with Supply Chain, Manufacturing, and Engineering to make sure M1 reflects how work actually flows through the floor, not just how it was set up at go-live.
• Data Governance and Inventory Integrity: Define and enforce data standards for production-side master data, bin and location controls, inventory accuracy, and non-conformance tracking. Identify and close gaps in system usage that lead to reporting discrepancies, reconciliation work, or lost visibility into production status. Establish accountability for consistent, disciplined system usage across the departments this role supports.
• Reporting and Operational Visibility: Develop and maintain production and inventory reporting using SQL and Crystal Reports. Write and maintain queries against the M1 database to surface accurate, actionable information for operations leadership and the shop floor. Define what data belongs in ERP versus external systems and hold that line.
• Cross-Functional Adoption and Training: Work directly with production, warehouse, purchasing, and quality teams to drive disciplined, consistent ERP usage. Document workflows, train users on correct system behavior, and follow through on incomplete adoption rather than treating configuration as the finish line.
• Integrations and Systems Coordination: Support integrations between ERP and third-party or internal systems that touch the production and operations modules this role owns. Coordinate with your peer administrator, internal developers, and external partners to ensure integrations are stable, accurate, and documented.
• ERP Roadmap Contribution: Provide the ERP Manager with visibility into production-side gaps, improvement opportunities, and scalability constraints. Contribute to build-versus-buy and enhancement-priority conversations from a grounded understanding of how the manufacturing modules are actually performing.
Qualifications
Experience:
• 5 to 7 years of ERP administration, implementation, or optimization experience in a manufacturing or production-driven environment.
• Demonstrated hands-on ownership of production-side ERP modules: inventory, purchasing, jobs, scheduling, shop floor, or quality.
• Experience working inside a team-based ERP function alongside peers or specialists covering adjacent modules is strongly preferred.
• Background in high-growth or operationally complex manufacturing environments preferred.
Skills:
• Strong SQL skills for production and inventory data querying, with the ability to write and maintain reports against a live ERP database.
• Working knowledge of MRP concepts, including demand planning, master scheduling, capacity management, work orders, and BOM, and the ability to apply those concepts within an ERP system.
• Experience with Crystal Reports or equivalent SQL-based reporting tools.
• Ability to configure and optimize ERP workflows, security roles, and module settings without relying on vendor professional services for every change.
• Clear communication with both technical and non-technical stakeholders; able to translate between shop-floor reality and system configuration.
• Strong documentation discipline and follow-through on adoption, not just configuration delivery.
• Experience with ECI M1 preferred.
Education:
• Bachelor's degree in Information Systems, Business, Engineering, Supply Chain, or related field, or equivalent ERP experience.
Why Moonshot?
• Operational Impact: The modules you own are the ones the floor runs on every day. Your configuration decisions show up immediately in production visibility, inventory accuracy, and shop-floor execution, not buried in a backlog.
• High-Growth Opportunity: Moonshot is expanding rapidly, moving into a purpose-built manufacturing campus, and increasing operational complexity across every function. You are joining at the moment these systems need to be right, not after someone else has already shaped them.
• Ownership with a Team: You own a defined, meaningful piece of the ERP platform with a peer alongside you covering adjacent ground. You are not alone in the system, and you are not sharing ownership in a way that blurs accountability.
• Culture of Execution: Moonshot is a disciplined, accountable organization where follow-through is valued over polish. If you take satisfaction in closing the loop, not just opening the ticket, this is the right environment.
