Enterprise Information Systems Engineer

About the Role 

Charm is hiring an EIS (Enterprise Integration Systems) Engineer to own the technical infrastructure connecting our core operating systems: Manufacturo (MFO), NetSuite, and Mangrove, among others.. This role operates within the IT organization and is responsible for the plumbing — integrations, automation scripts, system administration, and cross-system data anomaly resolution.

Charm operates a federated ownership model. Engineering, Operations, MRV, and Finance own their respective data and processes. The EIS Engineer owns the infrastructure underneath them. You are the person those teams rely on when data needs to flow between systems reliably, when a new process needs to be wired up technically, or when something breaks across a system boundary. You are not the owner of every problem — but you are the owner of the infrastructure that causes them.

Digital Tool Assessment & Implementation

• When a new digital tool is needed, assess what's available in the existing ecosystem and make the final selection call in coordination with Engineering

• Configure new tools at the system level — modules, licensing, permissions, and integrations — so domain teams can build on top of them

• Own the technical infrastructure underneath what engineers build; if the plumbing is broken, you get the call

Integration & Automation Infrastructure

• Maintain and develop all integrations between systems including but not limited to Manufacturo (MFO), NetSuite, and Mangrove

• Own automation scripts running in Manufacturo's Integrator module (C#)

• Ensure NetSuite ↔ MFO integration flows are error-free and assembly builds are triggering correctly

• Manage the data pipeline from MES to MRV reporting tools (SQL queries, Google Sheets connection)

• Build new integrations as the business introduces new processes or systems

• Own UAT test plans for new integrations; coordinate domain owners to test their respective pieces

• Ensure data is protected and security best practices are followed

• Create diagrams, wikis and system records to clearly document your designs.

Cross-System Anomaly Resolution

• Intake, triage, and prioritize data anomaly tickets that cross system boundaries

• Investigate root cause, coordinate with the relevant domain owner, and own the fix at the integration or infrastructure layer

• Document root causes and resolutions to reduce repeat issues

Data & Reporting Infrastructure

• Write and maintain SQL queries that feed MRV and operational reporting

• Update queries and scripts when processes change

• Fulfill data requests from internal stakeholders — dashboards, CSVs, live data connections — in coordination with the relevant domain team

System Administration

• Administer Manufacturo, NetSuite, and Mangrove at the configuration level: items, products, user roles, licenses

• Maintain hardware peripherals connected to these systems — label printers, scanners, tablets, and the Bartender integration

• Own the master documentation library; ensure domain teams are documenting their own processes

NPI / Process Change Support

• When Engineering introduces a new process, configure the technical infrastructure to support it: data collection fields, automation scripts, and integration outputs

• Consult with Engineering and Ops Process Specialists during process builds to ensure the system can support what they're designing

• Support integration testing and go-live; Responsible Engineer owns approval

What You Won't Own

To set expectations clearly: this role does not own process design, work order construction, or data collection field definitions (Engineering Process Specialist); shop floor execution quality or operator training (Operations Process Specialist); MRV data requirements or Mangrove data quality (MRV team); or NetSuite financial data quality (Finance/Controller). Those teams own their domains. You are their systems infrastructure partner, not their data steward. When a process plan is wrong, they get the call. When the plumbing is broken, you do.

• 2+ years in a systems integration, MES/ERP administration, or manufacturing IT role

• Hands-on experience with an ERP system — NetSuite strongly preferred

• SQL proficiency: writing, maintaining, and quality-checking queries against relational data models

• Familiarity with API integrations and middleware concepts

• Basic scripting ability in C# or a comparable language; comfort using AI tools to accelerate development and debugging

• Strong communication skills — you'll be coordinating across Engineering, Operations, MRV, and Finance regularly

• Strong Understanding of Information Security best practices.

Other Preferred 

• Experience with Manufacturo or a comparable MES platform

• Experience with Mangrove or similar environmental data / MRV platforms

• Familiarity with Ignition SCADA or industrial data systems

• Experience managing third-party integration vendors or consultants

• Background in manufacturing, biorefining, chemical processing, or a similarly data-intensive industrial environment

• Networking fundamentals helpful for hardware troubleshooting

Characteristics that matter

• You take ownership of the infrastructure, not just the tickets. When the plumbing is broken, you find it before someone else does.

• You're comfortable operating across team boundaries without formal authority — this role succeeds through relationships and trust, not control.

• You document as you go. Institutional knowledge that lives only in your head is a liability, and you know it.

• You understand that your job is to make domain owners successful, not to be the smartest person in the room on every topic.

• Love what you do, and be self driven to be great at it.

• Experience using Claude AI Coding Assistant

• Security certifications like Security+, ISC2

• Experience working with Google Cloud Platform Infrastructure

• Experience with GitHub and development pipeline practices