We are looking for a hands-on E2E IT Architect to design and build the composable technology landscape of Keenfinity Group - Audio. The business goal is clear: we want to grow fast, and the digital customer journey of our brands (Electro-Voice, Dynacord and others) is the engine for that. You will shape the architecture that connects commerce, CRM, PIM, CMS and ERP into one coherent, API-first platform that serves our brand websites, the new Customer Portal, our Academy and future digital products. The target picture is not finished yet. You will help define it, and then make it real together with a small, young team in Ovar and a handful of specialised implementation partners. Architecture Design & Build: Own the end-to-end architecture of our composable stack: Norce (commerce), Salesforce (Sales, Revenue and Service Cloud), Stibo STEP (PIM), Storyblok (headless CMS), Bynder (DAM), Workato (iPaaS) and the SAP ERP backbone. Design the integration layer and the BFF/API layer that feed our headless frontends, and make pragmatic decisions about where the stack is API-first, where it is event-driven, and where a simple SaaS-to-SaaS connection is good enough. Standards that Enable, not Slow Down: Define lightweight, practical standards for API design, data contracts, event handling, identity (OAuth 2.0, OIDC) and observability. Document them where people actually read them, and evolve them with the team rather than enforcing them from the outside. Delivery Partnership: Work day to day with our Product Owners (Frontend, CRM, MDM), the brand marketing leads and our implementation partners. Review their designs, unblock them, and take technical decisions quickly when they are needed. You are the person who keeps the whole picture in mind while everybody else is heads-down in their part of it. Technology Evaluation: Keep an eye on what is emerging in composable commerce, integration and AI-assisted engineering. Propose where a new platform or pattern would make us faster or simpler, and be equally willing to say no when it would not. We prefer fewer, well-integrated components over a long list of tools.