Technology / Systems Enterprise Architect

The Technology Enterprise Architect (EA) will design, integrate, and maintain a unified architecture across multiple interconnected systems. The environment includes hybrid -hosted platforms, offline/remote system constraints, complex data flows, and multiple integration touchpoints.

This role serves as the “glue” between technology teams, system vendors, and business system owners—ensuring that platforms are secure, scalable, compliant, and interoperable.

Key elements of the environment include:

• Hybrid on -premise and cloud systems
  

• Offline/poor -connectivity environments requiring store -and -forward solutions
  

• Master -data complexity across multiple systems
  

• Integration across devices, sensors, applications, and cloud infrastructure
  

• Strong need for API management, data warehousing, and data pipeline development
  

The EA must be able to design architecture frameworks, write integration code, develop data pipelines, configure interfaces, and ensure systems align to broader business requirements.

Requirements

2. KEY RESPONSIBILITIES & RESULT AREAS

Architecture & Systems Design

• Define, implement, and manage enterprise architecture processes and standards.
  

• Develop logical, physical, virtual, and integration architecture diagrams.
  

• Ensure system owners understand system behaviour, integrations, and operating models.
  

Systems Integration & Data Management

• Oversee API and integration specifications with internal teams and vendors.
  

• Manage master -data processes and support data custodians in ensuring data integrity.
  

• Implement error -management and monitoring controls for all production systems.
  

• Define disaster recovery and business continuity requirements and ensure testing.
  

Vendor & Stakeholder Management

• Collaborate with system vendors to ensure contractual and technical obligations are met.
  

• Advise business owners on architectural constraints and data governance.
  

• Ensure procedural alignment between business rules and technical capabilities.
  

3. KEY RELATIONSHIPS

Primary Stakeholders

• Technology vendors and partners
  

• Technology leadership
  

• Business system owners
  

• Super users
  

• Regional and onsite technology teams
  

Indirect Stakeholders

• End users
  

• Operational management
  

• External IT suppliers
  

• Regional support staff
  

• Audit and risk teams
  

4. JOB SPECIFICATION

The Enterprise Architect will:

• Engage with business units, technology teams, and vendors to define system architecture and hosting requirements.
  

• Address security, data segregation, and store -and -forward mechanisms for offline systems.
  

• Design and support device, network, and systems accessibility management.
  

• Provide guidance on business processes and master -data -related rules.
  

• Write or configure code for systems integration (APIs, Python, database queries, etc.).
  

• Work with cloud technologies (Azure or similar) for data warehousing and transfer processes.
  

5. KEY PERFORMANCE AREAS

Aligned to four architecture pillars (TOGAF -aligned):

1. Business Architecture
   

2. Data Architecture
   

3. Applications Architecture
   

4. Technical Architecture
   

Deliverables Include:

• Enterprise architecture diagrams
  

• API/middleware/store -and -forward definitions
  

• Error -management processes and reporting
  

• Vendor roles and responsibility frameworks
  

• Data integrity protocols and review cycles
  

• Data warehouse architecture and data -flow mapping
  

• Network standards (WAN, WWAN, VPN, LAN) and SOPs
  

• Network monitoring dashboards, alerts, and escalation processes
  

Performance will be monitored through KPIs and a balanced scorecard measured monthly.