Solutions Architect MMH

Role Purpose

The Solution Architect is responsible for designing end-to-end solutions for specific domains or work streams within the insurance modernisation programme.

The role translates business requirements and target architecture principles into coherent solution designs spanning process, application, integration, and data layers. The Solution Architect ensures alignment with enterprise standards while enabling delivery teams to execute effectively.

This role operates within defined architectural guardrails set by the Enterprise Architect and Lead Solution Architect.

There is already a clear, sensible strategic direction in place, with meaningful progress made. The expectation for the role is to build on that foundation, not to discard or restart it. Their role is to strengthen, accelerate, and ope rationalise what’s already been defined — ensuring continuity, stability, and incremental evolution. Any improvements should be evidence-based and respectful of the current architecture and organisational context.

The Modernisation Programme Operates Within a Predominantly

• Java-based application ecosystem
• AWS cloud environment
• API-first and event-driven integration model
• BPM and decision management platforms
• Containerised deployment (e.g., Kubernetes)

Candidates should demonstrate experience designing solutions in comparable enterprise technology environments.

• 7–10 years in solution design or architecture roles.
• Experience delivering enterprise applications in financial services (insurance preferred).
• Strong understanding of:
  • API-based integration
  • Process orchestration platforms
  • Data modelling principles
  • Cloud-native environments
• Experience working in transformation programmes

Experience Modernising Legacy Platforms In Brownfield Enterprise Environments Is Highly Desirable, Including Use Of Incremental Migration Strategies And Architectural Decomposition Approaches Including

• Modular decomposition in brownfield environments.
• Strangler patterns.
• Anti-corruption layers.
• Transitional architectures.
• Incremental migration strategies.

• Own solution architecture for assigned domain (e.g., claims, policy, digital engagement, integration).
• Produce high-level design artefacts covering:
  • Process flows
  • Application interactions
  • API contracts
  • Data flows
  • Integration patterns
• Ensure traceability from business requirements to solution components.

• Partner with business stakeholders to shape solution options.
• Translate operating model changes into system implications.
• Identify simplification opportunities (avoid automating broken processes).
• Provide architecture input into business case and impact assessments.

• Ensure domain solutions align with:
  • API standards
  • Event architecture
  • Security patterns
• Avoid duplication of capabilities across work streams.
• Collaborate with peer architects to prevent siloed designs.

• Define service boundaries.
• Ensure clean decoupling from legacy systems.
• Validate integration approach (sync vs async).
• Drive reuse of shared services where appropriate.

• Design workflow at solution level.
• Ensure decision logic is externalised.
• Prevent overloading BPM with domain logic.
• Design for straight-through processing where viable.

• Participate in design reviews.
• Review vendor and squad solution outputs.
• Ensure alignment to architecture runway.
• Identify risks and elevate appropriately.