Enterprise Architect 

Location: Brussels

Languages: English, Dutch, French

Role Mission

The Senior Interim Enterprise Architect will be responsible for structuring, cohering, and directing the future of the application landscape. The core mission includes:

• Creating a deep architectural understanding of the current application estate.
• Defining a target application architecture based on decoupling principles and integration via a central integration layer.
• Establishing clear architectural principles to prevent a return to point-to-point “spaghetti” integrations.
• Enabling realistic, phased modernization rather than disruptive “big-bang” change.

This role is strategic by nature but grounded in pragmatic feasibility, considering the client’s current capacity and constraints.

Collaboration Model

The Enterprise Architect will work closely with:

• The CIO, as the primary sponsor and architectural decision authority.
• Business stakeholders to understand functional needs and constraints.
• The Senior Data Architect to ensure alignment between application architecture, data flows, and integrations.
• A potential Program Manager, should the client decide to formalize program governance.

The Enterprise Architect acts as the overall guardian of application architecture coherence, coordinating closely with data and integration perspectives.

Key Responsibilities

1. Detailed Application Landscape Documentation:
   • Refine the existing high-level application landscape into a detailed, actionable architecture view.
   • Document core functionality, business ownership, technology stack, lifecycle status, interfaces, dependencies, criticality, and architectural risk for each application.
   • Identify redundant or overlapping applications, tight couplings, and fragile or undocumented integrations.
   • Produce clear “as-is application architecture” documentation for both technical and executive audiences.
2. Integration Architecture Analysis:
   • Analyze all existing integrations, including point-to-point interfaces, batch and file-based exchanges, and API-based integrations.
   • Identify structural weaknesses and quantify architectural consequences such as change impact propagation, maintenance complexity, and risk concentration.
3. Target Applications Integration Architecture Definition:
   • Define a future-state application architecture centered around a central integration layer.
   • Establish clear separation between core systems, supporting applications, and external consumers.
   • Define integration principles, interface standards, and allowed/disallowed integration patterns.
4. Architectural Principles & Guardrails:
   • Define a concise set of enterprise architecture principles, including decoupling, reusability, composability, and clear ownership boundaries.
   • Translate principles into practical guardrails for project teams, external vendors, and future sourcing decisions.
5. Roadmap & Transition Strategy:
   • Develop a phased and realistic roadmap, including immediate stabilization actions, mid-term architectural restructuring, and long-term modernization initiatives.
   • Align the roadmap with business priorities and data architecture and governance initiatives.
6. Enabling Governance & Decision-Making:
   • Support the CIO in architectural decision-making and investment prioritization.
   • Help lay the groundwork for ongoing architecture governance and a future architecture board or review process.

Required Experience & Profile

• Experience: 8–10+ years as an Enterprise Architect or Lead Solution Architect.
• Proven experience in complex, heterogeneous application landscapes and organizations with significant legacy components.
• Strong background in integration architecture and decoupling strategies.
• Experience in interim or advisory roles is a strong asset.

Technical & Functional Expertise

• Deep understanding of enterprise application architecture and integration patterns.
• Familiarity with cloud-based integration concepts and Microsoft Azure ecosystems is a strong asset.
• Ability to remain technology-neutral while providing clear guidance.

Ways of Working

• Strong analytical and structuring skills.

• Comfortable working with ambiguity and incomplete documentation.
• Able to communicate architectural concepts in clear, non-technical language.
• Natural authority without formal power.

Language & Communication

• Fluent in English for architecture artifacts and documentation.
• Ability to speak and understand Dutch and French, essential for stakeholder interaction.