Technical Architect Procurement

Job Location: hybrid in Bucharest

Recruitment process:

• HR screening
• 2 X Technical Discussion

Role purpose

The Technical Domain Architect defines and maintains the target architecture and drives the transformation from the current state toward the target architecture for Procurement & Assortment business domain.

The role connects business priorities with technology decisions and ensures that applications, data flows and integrations within the domain evolve coherently. 

Business stakeholders retain ownership of business decisions and priorities. The Technical Domain Architect ensures that proposed solutions are technically feasible, aligned with the target architecture and defined internal guardrails.

Reporting relationships

Reports to: Director Tech

The Technical Domain Architect is part of the Architecture Team and owns the architecture for one ormore assigned business domains.

Key responsibilities

Domain architecture

• Develop and maintain the target architecture for the assigned business domain. 
• Document the domain architecture across applications and business capabilities, data flows, and integrations and interfaces. 
• Translate business priorities into a realistic architecture roadmap. 
• Identify dependencies between the domain and SAP, data, integration and other application domains. 
• Maintain transparency of the current application landscape, planned changes and architectural gaps. 
• Ensure reliable and resilient communication between systems within the assigned domain, including the selection and appropriate use of middleware, synchronous APIs and asynchronous integration patterns. 
• Ensure that solution architectures support effective testing, particularly end-to-end system and integration testing, through clear interfaces and testable components

Application landscape management

• Assess existing applications regarding strategic fit, functionality, lifecycle, cost, risk and technicalquality. 
• Determine the most appropriate solutions for implementing new requirements, considering existing capabilities, target architecture and reuse opportunities. 
• Where a new system is required, prepare the architectural assessment and recommendation for review by the Architecture Board. 
• Recommend whether applications should be retained, improved, consolidated, replaced or retired. 
• Prevent unnecessary duplication of applications and capabilities. 

Project and delivery support

• Provide architecture guidance to projects, product teams and delivery teams from initial planningthrough implementation. 
• Review solution options and evaluate their impact on the wider application landscape. 
• Define architectural guardrails and identify approved technology patterns. 
• Support teams in resolving cross-application and cross-domain design decisions. 
• Review significant architecture decisions and document agreed exceptions. 
• Escalate decisions with material cross-domain or strategic impact to the Enterprise Architect Lead or Architecture Board.

Architecture governance

• Prepare architecture decisions for review and approval by the Architecture Board.
• Document decisions, assumptions, risks, dependencies and exceptions. 
• Monitor whether approved architecture decisions are reflected in solution designs and implementation. 
• Contribute to reusable architecture standards, templates and patterns.

Collaboration

• Work closely with the relevant business and IT stakeholders for the assigned domain. 
• Collaborate with Process Architects to ensure end-to-end integration of business processes. 
• Coordinate with the SAP Architect on SAP capabilities, clean-core principles and extensions. 
• Coordinate with the Data Architect on data ownership, models, flows and platform usage. 
• Coordinate with the Integration Architect on APIs, events, interfaces and integration patterns. 
• Work with Security, Infrastructure, Engineering and other specialists where their expertise is required. 
• Contribute actively to the Architecture Team's shared backlog and weekly architecture meetings.

Decision authority

The Technical Domain Architect is authorised to:

• Define the proposed target architecture and roadmap for the assigned domain. 
• Provide architectural approval or recommendations within the agreed governance framework. 
• Identify when a decision requires Architecture Board approval. 
• Request changes to solution designs that conflict with approved architecture principles or create unacceptable dependencies or risks.

Business priorities, budgets and final business decisions remain with the appropriate business and technology governance bodies.

Expected deliverables

• Current-state and target-state domain architecture.
• Domain application portfolio and business-capability mapping.
• Data-flow and integration diagrams.
• Domain architecture roadmap.
• Application lifecycle and rationalisation recommendations.
• Architecture decision records and project architecture assessments.
• Documented risks, dependencies and exceptions.
• Reusable domain-specific standards and patterns.

Required experience and capabilities

• Several years of experience in enterprise, domain, solution or application architecture.
• Strong understanding of complex enterprise application landscapes.
• Experience designing solutions across applications, data and integration.
• Ability to translate business requirements into clear technology decisions.
• Experience with architecture governance, roadmaps and application portfolio management.
• Understanding of cloud platforms, APIs, event-based integration and modern application architectures.
• Ability to assess architectural options, dependencies, risks and trade-offs.
• Strong stakeholder-management and communication skills.
• Ability to work effectively with business stakeholders and technical delivery teams.
• Fluent English; German is an advantage.

Preferred experience

• Experience in retail, supply chain, finance, e-commerce or another relevant Müller business domain.
• Experience with SAP S/4HANA Cloud and side-by-side applications.
• Familiarity with data platforms and enterprise integration platforms.
• Experience working with architecture frameworks and modelling tools.
• Experience supporting major transformation programmes while maintaining responsibility for the permanent application landscape.

Success measures

• A clearly documented and agreed target architecture exists for the assigned domain.
• Architecture decisions are timely and based on transparent options and trade-offs.
• Application duplication and unnecessary complexity decrease over time.
• Delivery teams reuse approved platforms, services and integration patterns.
• Architecture-related issues are identified earlier in the delivery lifecycle.
• Application lifecycle risks and modernisation priorities remain transparent.
• Business stakeholders, architects and delivery teams remain aligned.
• Delivery teams receive timely and actionable architecture guidance.