Technical Architect MMH

Role Purpose

The Technical Architect will be responsible for translating approved solution architectures into robust, scalable, and secure technical designs across the insurance modernisation programme. Working closely with the Lead Solution Architect, engineering teams, and vendors, the Technical Architect ensures implementation fidelity, enforces engineering standards, and embeds non‑functional requirements into delivered platforms. This is a hands‑on architectural role focused on technical depth, delivery quality, and platform integrity across BPM, APIs, cloud infrastructure, integration, and data services.

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.

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

• 8–12 years in software engineering and technical architecture.
• Strong hands‑on experience with:
  • API and microservices design
  • BPM/workflow platforms
  • Cloud‑native deployment
  • Integration patterns
  • Event‑driven architectures
• Experience in complex enterprise environments (insurance preferred).
• Strong understanding of non‑functional design principles.

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.

• Translate solution blueprints into detailed technical architecture artefacts.
• Define component‑level design (services, APIs, workflows, integrations).
• Ensure correct separation of concerns (orchestration vs domain logic vs rules).
• Validate vendor technical designs before build.

• Define and enforce:
  • API standards
  • Naming conventions
  • Error handling patterns
  • Logging & observability standards
  • Security patterns
• Ensure consistent patterns across work streams.
• Prevent localised “quick fixes” that create systemic debt.

• Oversee workflow model implementation quality.
• Ensure business/domain rules are externalised (not embedded in process flows).
• Validate integration patterns (synchronous vs async).Ensure API contracts are clean and versioned correctly.

• Performance targets
• Scalability thresholds
• Resilience patterns (retry, circuit breaker, failover)
• Security controls
• Audit logging
• SLA monitoring hooks

• Work with platform teams on:
  • CI/CD pipelines
  • Containerisation standards
  • Infrastructure‑as‑code alignment
  • Environment consistency
• Ensure environments reflect architectural intent.
• Enable repeatable, automated deployments.

• Identify early technical risks.
• Maintain a technical debt register.
• Propose refactoring paths before debt compounds.
• Escalate architectural deviations proactively.

• Provide hands‑on guidance to engineering teams.
• Participate in sprint‑level design discussions.
• Conduct code and configuration design reviews.
• Support production readiness assessments.