ERP Solution Architect

Fynd ERP Deployment (Primary Responsibility)\n\nOwn end-to-end deployment of Fynd ERP for customers — discovery, solution design, configuration, data migration, integration, testing, go-live, and hypercare.\nTranslate customer business processes (commerce, supply chain, finance, inventory) into Fynd ERP configuration and, where needed, custom extensions.\nDefine the “system of record” boundary for each engagement — which processes and data live in Fynd ERP vs. the customer’s existing SAP/D365 estate.\nAct as the primary technical/architectural point of contact for customers during Fynd ERP rollouts.\nSAP & D365 Integration Depth\nArchitect and build integrations between Fynd ERP and SAP (ECC/S4HANA) or D365 (F&O/Business Central) — using APIs, IDocs/BAPIs/RFCs on the SAP side, Data Entities/AIF/DMF on the D365 side, and middleware/iPaaS tools as needed.\nDesign integration patterns for the specific modules most likely to be in scope: SAP FI/CO, MM, SD, WM/EWM; D365 Finance, Supply Chain Management, Business Central.\nEnsure master data consistency (SKUs, customers, vendors, pricing, inventory) flows correctly and reliably between Fynd ERP and the customer’s SAP/D365 environment.\nDesign for event-driven, real-time, or batch integration depending on the customer’s SAP/D365 landscape (on-prem ECC vs. S/4HANA Cloud, D365 on-prem vs. cloud).\nUnderstanding the Customer’s SAP/D365 Landscape\nPerform in-depth technical discovery of a customer’s existing SAP or D365 implementation — configuration, RICEFW customizations, integration points, data model, and known technical debt.\nSpeak fluently in SAP/D365 terminology and process language (e.g., SAP Activate methodology, Clean Core/BTP extensibility, S/4HANA migration paths; D365’s Data Management Framework, Power Platform extensibility) so that customer-side SAP/D365 architects treat you as a peer, not a vendor rep.\nIdentify risks, gaps, and dependencies in the customer’s current ERP setup that will affect the Fynd ERP deployment.\nCross-Cutting\nSet integration and architecture standards across engagements so patterns are reusable rather than reinvented per customer.\nWork closely with Fynd ERP product and engineering teams to feed back real-world SAP/D365 integration requirements into the product roadmap.\nUse prior hands-on experience with SAP and D365 to identify capability gaps in Fynd ERP and propose concrete enhancements — effectively acting as a product advisor grounded in what mature ERPs already do well.\nMentor implementation consultants and vet any external SIs/partners engaged on SAP or D365 workstreams.\nMust-Have Experience\n8–15+ years in ERP implementation, consulting, or architecture roles.\nProven, hands-on, end-to-end implementation experience on both SAP (ECC/S4HANA) and Microsoft Dynamics 365 (F&O/Business Central) — not exposure to one platform and theoretical familiarity with the other.\nA track record equivalent to an SAP Solution Architect and/or D365 Solution Architect: has led or architected multiple full-lifecycle implementations (requirements → solution design → build/configuration → data migration → testing → go-live → hypercare) on each platform.\nDeep, working fluency in SAP terminology and concepts — e.g., FI/CO, MM, SD, WM/EWM, RICEFW objects, IDocs, BAPIs/RFCs, SAP Activate methodology, S/4HANA migration (brownfield vs. greenfield), SAP BTP/Clean Core, SAP Integration Suite (CPI)/PI-PO.\nEqual fluency in D365 terminology and concepts — e.g., D365 Finance, Supply Chain Management, Business Central, Data Entities, Data Management Framework (DMF), Application Integration Framework (AIF), X++ extensibility, Power Platform (Power Automate/Power BI), Azure Integration Services.\nReal experience integrating a non-SAP/non-D365 system into an existing SAP or D365 landscape — this is the exact pattern we need for Fynd ERP.\nStrong understanding of commerce and supply chain processes (order management, inventory, procurement, fulfillment) and how they map to ERP modules.\nComfortable owning technical discovery directly with a customer’s IT/ERP team, including their SAP/D365 architects.\nHands-on and builder-minded — writes/reviews integration code, works directly in configuration and data, and doesn’t stop at architecture diagrams.\nAI-first working style — actively uses AI/LLM tools to accelerate ERP work (data mapping, migration scripting, documentation, test generation) rather than relying purely on manual, traditional ERP-consulting methods.\nDemonstrated comfort operating in both the ERP world and the open-source world — e.g., has used or contributed to open-source tools/frameworks alongside enterprise ERP platforms, and can bring that pragmatism into how we build and extend Fynd ERP.\nGood to Have\nSAP certifications (e.g., SAP Certified Application Associate/Architect – S/4HANA) and/or Microsoft Dynamics 365 certifications.\nPrior experience with a product company building its own ERP/commerce platform, rather than only working ERP implementations as a consultant/SI.\nExperience in retail, D2C, or unified-commerce environments specifically.\nFamiliarity with modern iPaaS/API management tooling (MuleSoft, Boomi, Azure API Management, or similar).\nExposure to cloud infrastructure (Azure, AWS, GCP) supporting ERP and integration workloads.\nWhat We’re NOT Looking For\nSomeone who has only worked on one ERP platform and has “read about” the other.\nPure functional consultants without integration/technical architecture depth.\nProject/program managers without hands-on solution design and implementation ownership.\nSomeone looking for a purely internal role — this position is customer-facing and will regularly sit across the table from a customer’s SAP or D365 architects.\nIdeal Candidate Profile Someone who can walk into a customer’s environment already running SAP or D365, quickly map out what their system actually does, tell us exactly where Fynd ERP should plug in and what needs to integrate versus what needs to be replaced — and then go build and deploy that solution themselves. They’ve done this more than once, on both platforms, and can hold their own in a room full of SAP/D365 architects because they’ve genuinely been one.\nThey’re also restless in a good way — they reach for AI tools to move faster, they’re as comfortable pulling from open-source communities as they are navigating enterprise ERP conventions, and they’re always asking why something has to be done the slow, traditional way when it doesn’t have to be.