ERP Integration Expert

GeneralMind builds AI Systems of Action for complex enterprise workflows. We deploy AI employees that automate messy operational handovers across supply chains processing orders, validating invoices, coordinating suppliers, and handling exceptions directly on top of enterprise systems like SAP or Oracle. Our platform combines AI agents, operational context graphs, and real transaction data to achieve Autopilot-grade automation in real operational environments. We work closely with leading global companies across manufacturing, retail, and logistics to deploy AI into mission-critical workflows. Tasks Own the integration architecture for new customers end to end: assess their ERP landscape, choose the right interface pattern (OData, RFC/BAPI, IDoc/EDI, CPI/BTP, staging tables, file-based), and design something their IT will approve and operate. Lead technical discovery with customer IT, basis, and process teams, and surface the blocking constraint in week one, not week nine. Own the data and field mapping from the customer's order, item, partner, and pricing structures onto our internal model, including the custom fields that carry the real business logic. Design and build our ERP connectors in Python (S/4HANA and ECC, Oracle, Microsoft Dynamics, Salesforce) and turn per-customer work into reusable abstractions, so the tenth connector costs a fraction of the first. Build durable, long-running integration workflows with safe write-back into customer systems of record: idempotency, retries, replay semantics, and recovery paths from the start. Own integration observability: know when a sync is stuck, degraded, or silently writing the wrong thing before the customer notices. Define the authentication, network, and security posture per customer and get it through their review. Feed what you learn in customer landscapes back into the product. You will see the same five problems before anyone else does. Requirements ERP integration depth, non-negotiable: you have delivered productive ERP integrations and know the interface landscape first-hand (IDoc, BAPI/RFC, OData/Gateway, CPI/BTP Integration Suite), on both S/4HANA and ECC, and you know which one to reach for and why. Functional grounding: fluent in at least one of SD (order-to-cash) or MM (procure-to-pay), credible in the other, plus the FI touchpoints for AP/AR. You know what a schedule line, a condition record, and a three-way match actually are. Engineering, not just configuration: 5+ years building and operating backend systems with real Python depth, owning production services rather than just delivering features. Reliability instinct: idempotency, retries, and observability are part of how you design, not afterthoughts. A workflow engine like Temporal in production is a strong plus. Customer-facing credibility: you can stand in front of an enterprise IT department, absorb their constraints, push back where it matters, and leave them confident. End-to-end ownership: you identify what's broken or