ERP Solution Architect – Fynd ERP

Location: Mumbai, India

Department: Engineering

Experience: 8-15+ yrs

1. Architect and build integrations between Fynd ERP and SAP/D365 (or specific modules within them) wherever a customer needs their existing ERP to coexist with Fynd ERP rather than be replaced outright.
2. Understand a customer’s existing SAP or D365 implementation in depth — their configuration, customizations, master data, and process flows — so we can correctly scope what Fynd ERP will own, what stays on the legacy ERP, and how the two will talk to each other.
3. Bring that SAP/D365 experience back into Fynd ERP itself — using firsthand knowledge of how SAP and D365 solve a given problem to identify gaps, propose enhancements, and help shape Fynd ERP’s own roadmap so it holds up against the platforms our customers are used to.

• Hands-on, not just advisory: Someone who will get into the configuration, the code, the API payloads, and the data — not just draw architecture diagrams and hand them off.
• AI-first: Someone who instinctively reaches for AI/LLM-based approaches to speed up ERP work — data mapping, code generation, documentation, testing, migration scripting — rather than doing everything the traditional, manual ERP consulting way.
• Genuinely enthusiastic about pushing boundaries: Someone who gets energized by “how do we do this better/faster/differently” rather than defaulting to how SAP or D365 implementations have always been done.
• Equally comfortable in the ERP world and the open-source world: Traditional ERP work (SAP/D365, proprietary tooling, enterprise integration patterns) tends to live in a different universe from open-source engineering culture (GitHubnative workflows, open APIs, community tooling, modern dev stacks). We need someone who can move fluidly between both — bringing open-source speed and pragmatism into ERP work, and enterprise rigor into how we build Fynd ERP.

• Own end-to-end deployment of Fynd ERP for customers — discovery, solution design, configuration, data migration, integration, testing, go-live, and hypercare.
• Translate customer business processes (commerce, supply chain, finance, inventory) into Fynd ERP configuration and, where needed, custom extensions.
• Define the “system of record” boundary for each engagement — which processes and data live in Fynd ERP vs. the customer’s existing SAP/D365 estate.
• Act as the primary technical/architectural point of contact for customers during Fynd ERP rollouts.

• Architect 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.
• Design 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.
• Ensure master data consistency (SKUs, customers, vendors, pricing, inventory) flows correctly and reliably between Fynd ERP and the customer’s SAP/D365 environment.
• Design 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).

• Perform in-depth technical discovery of a customer’s existing SAP or D365 implementation — configuration, RICEFW customizations, integration points, data model, and known technical debt.
• Speak 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.
• Identify risks, gaps, and dependencies in the customer’s current ERP setup that will affect the Fynd ERP deployment.
• Advise customers on brownfield vs. greenfield approaches where Fynd ERP is being introduced alongside or in place of parts of SAP/D365.

• Set integration and architecture standards across engagements so patterns are reusable rather than reinvented per customer.
• Work closely with Fynd ERP product and engineering teams to feed back real-world SAP/D365 integration requirements into the product roadmap.
• Use 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.
• Mentor implementation consultants and vet any external SIs/partners engaged on SAP or D365 workstreams.

• 8–15+ years in ERP implementation, consulting, or architecture roles.
• Proven, 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.
• A 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.
• Deep, 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.
• Equal 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.
• Real 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.
• Strong understanding of commerce and supply chain processes (order management, inventory, procurement, fulfillment) and how they map to ERP modules.
• Comfortable owning technical discovery directly with a customer’s IT/ERP team, including their SAP/D365 architects.
• Hands-on and builder-minded — writes/reviews integration code, works directly in configuration and data, and doesn’t stop at architecture diagrams.
• AI-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.
• Demonstrated 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.

• SAP certifications (e.g., SAP Certified Application Associate/Architect – S/4HANA) and/or Microsoft Dynamics 365 certifications.
• Prior experience with a product company building its own ERP/commerce platform, rather than only working ERP implementations as a consultant/SI.
• Experience in retail, D2C, or unified-commerce environments specifically.
• Familiarity with modern iPaaS/API management tooling (MuleSoft, Boomi, Azure API Management, or similar).
• Exposure to cloud infrastructure (Azure, AWS, GCP) supporting ERP and integration workloads.

• Someone who has only worked on one ERP platform and has “read about” the other.
• Pure functional consultants without integration/technical architecture depth.
• Project/program managers without hands-on solution design and implementation ownership.
• Someone 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.