Enterprise Solution Architect (human) at Neura Robotics (Metzingen, Germany / Riederich, Germany)Enterprise Solution Architect (human)

Neura Robotics is expanding its existing ERP team into a full Enterprise Application Team. With a growing system landscape: Business Central as the ERP core, CRM, Business Intelligence, AI integration, and MES and PLM in the future, we need someone to actively shape the architecture of that landscape: set standards, interlock integrations cleanly, and prevent fast "vibe coding" from turning into uncontrolled shadow IT. You define the guardrails without becoming an approval gate that slows the company down.

• Reference architectures & guidelines: You develop and maintain binding standards for how systems at Neura may be connected to each other: when a middleware layer makes sense and when a direct connector solution is sufficient.
• Technical sparring: You are the early point of contact for the team when new integrations or tools are being planned, as a sparring partner, not an approval authority.
• System landscape overview: You maintain a living overview of systems and data flows: ERP (Business Central), CRM, BI, AI applications, and eventually MES and PLM: who accesses what, and where redundancies or dependencies arise.
• Technology assessment: You evaluate new tools and technologies from an architectural perspective before they are introduced, to avoid uncontrolled connections into the core system.
• AI & digitalization strategy: You work closely with the ERP AI Engineer and the Digital Transformation role, bringing the architectural perspective into the company's AI strategy.

• Several years of experience building and evolving enterprise architectures in heterogeneous system landscapes
• Experience with multiple application types (e.g. ERP, CRM, BI, MES, PLM) is an advantage: in-depth Business Central knowledge is not required, as this is already covered within the team
• Solid understanding of integration patterns, middleware concepts, and API architectures
• Hands-on skills, e.g. implementing integrations independently, are a plus but not a must
• Strong pragmatism: you prefer a good, secure solution over a theoretically perfect architecture
• Strong communication and persuasion skills: you establish standards without relying on hierarchy
• A sense for when standardization is necessary and when it would only slow down day-to-day business