Solution Architect - Actuarial Platform

Solution Architect - Actuarial Platform

We Are Waiting for You

Hi there!

I am Laura, the recruiter for this position. Nice to meet you!

First, a little bit about what I like the most about working at Zurich Technology Delivery Center: The environment here is incredibly collaborative and innovative. Our tech-driven mindset fosters continuous learning and growth, creating an atmosphere where everyone can thrive. Now, I can't wait to share this exciting journey with you at Zurich!

First off all, THANK YOU for considering our company. We understand that finding the right opportunity can be tough, but I’ll try to make it easier.

Who Are We?

Let me introduce us. You’re reading about Zurich Insurance Group, a global leader in insurance, but this role specifically pertains to our Technology Delivery Center (TDC). Established in Barcelona in 2006, the TDC operates as an integral part of Zurich Insurance Group, providing cutting-edge technological solutions and support to Zurich's local and global business units.

In essence, Zurich TDC is where technology meets the vast reach of a multinational company. We specialize in areas such as software development, data analytics, cybersecurity, and IT infrastructure. Our primary mission is to support Zurich's strategic goals and enhance operational efficiency through innovative technology solutions.

If you're considering a role with us, know that you'll be joining a hub of technological excellence dedicated to driving Zurich's success on a global scale.

What Can You Expect?

The Solution Architect is the technical authority for feature evolution and platform design across ACE (Actuarial Calculation Engine). The role owns architectural decisions across the data, ETL, integration, and application layers — ensuring new capabilities are built with consistency, scalability, and full alignment to cloud migration objectives.

ACE is not a simple reporting application. It is a multi-layer calculation and data platform built on Databricks (Delta Lake, DBT, PySpark), Azure Data Factory, and a .Net GUI/orchestration layer. The calculation engine manages seven distinct data classes, applies a formula-driven calculation chain with complex interdependencies across a multi-dimensional calculation grain, and produces a result set consumed by reporting, data sharing, and downstream analytical systems including the ZAAi agentic reporting layer.

The platform is migrating from Azure to AWS with a target go-live of Q1 2027. The Solution Architect will own target-state architecture design and ensure all new features delivered before the migration are AWS-portable from day one..

And you might be thinking: This is great, what will my day-to-day be like, at TDC? I’m glad you asked.

As a Solution Architect – Actuarial Platform (ACE) you will have the opportunity to:

Solution Architecture for Feature Delivery

• Own end-to-end technical design for new features and enhancements across the ACE platform and associated actuarial systems.
• Translate actuarial business requirements (BRDs) into detailed technical specifications — defining data flows, calculation chain impacts, formula applicability changes, API interactions, and integration patterns.
• Maintain and evolve the ACE solution architecture reference, ensuring it reflects both current state and target AWS architecture at all times.
• Assess and challenge technical approaches proposed by the delivery team; enforce architectural principles and prevent short-cuts that compromise auditability, idempotency, or data quality.
• Define non-functional requirements (NFRs) for each feature: performance, scalability, data retention, disaster recovery, and auditability.

Actuarial ETL & Data Architecture

The ACE data model has seven data classes, each with different volatility, lifecycle, and governance rules:

• Static (ISO codes, enumerations) — lowest volatility, versioned by default, ad hoc update lifecycle
• Master (Forex rates, BDP rates, Counterparty, Reporting Hierarchy, GroupRe Treaty) — time-series, sourced from SAP and Group systems
• Local Reference (UoA, SUoA, RS, RF, AY, RP, RT) — BU-specific, medium volatility
• Transaction (cashflows, actuals, opening balances, reconciliation actuals) — highest volatility, quarterly supply
• Group Reference Data (GRD) — group-wide scaling constants applied uniformly across BUs
• Report Configuration (formula files in Git repo) — PO-managed, IT-governed, pulled at runtime
• Result Set — generated by the calculation engine, written to Delta Lake Gold layer
• Design and govern ETL pipelines for all seven data classes with appropriate partitioning, versioning, and data quality controls per class.
• Own the Delta Lake partitioning strategy — calculation grain alignment across Company Code, Cycle, Reporting Period, Run ID, Valuation Date, Unit of Account, Sub-UoA, Accident Year, and LIC Type dimensions.
• Design and review the pivot/execute/unpivot ETL pattern used by the calculation engine — ensuring it is performant, correctly scoped, and free of cyclic formula dependencies.
• Define the multi-currency FX conversion chain — transactional, functional, and Group currency dimensions — and ensure correctness of FX-impacted inherited variables across all calculation grains.
• Design the formula applicability validation layer, ensuring all combinations of Valuation approach (BBA01/02/03), GOR (Gross/Reinsurance), Reinsurance type, and LIC Type (LRC/LIC) are correctly covered.
• Enforce data model standards for ACE result sets: 2NF structure, partition key consistency, and result set dimension completeness across all new reports.
• Define data lineage, auditability, and Reverse Traceability Matrix (RTM) standards — every calculation output must be traceable to its input data, formula version, and execution context.
• Design self-healing pipeline patterns: retry logic, reprocess queues, custom null/NaN exception handling, and fully qualified error logging at calculation grain level.
• Own the Unity Catalog data sharing architecture — views, access control, and query cluster isolation between the calculation engine and external consumers.

Config-as-Code & Deployment Architecture

• Design and own the Git-based formula deployment pipeline: repository structure, branch strategy, PO-managed formula files, IT release approval gates, and Databricks runtime pickup.
• Define the Databricks workflow and DBT deployment pipeline via Azure DevOps, including environment promotion policies (Dev → SIT → UAT → Prod) and full deployment auditability.
• Ensure all new features are designed AWS-portable from day one — no Azure-only dependencies introduced pre-migration.

AWS Migration – Target Architecture (Go-Live Q1 2027)

• Lead architectural planning for the ACE migration from Azure to AWS — mapping current components (ADF, Azure Databricks, Azure Storage, .Net orchestration layer) to AWS equivalents.
• Produce migration artefacts: as-is/to-be architecture diagrams, migration runbooks, risk registers, and decommission plans.
• Work with the Azure Principal Architect and platform engineers to resolve cross-dependency blockers and de-risk the migration timeline.
• Validate that the AWS target architecture preserves all ACE design principles: idempotency, ACID compliance, self-healing, auditability, and parallel processing capability.

Governance, Standards & Team Engagement

• Establish and maintain Architectural Decision Records (ADRs) for all significant platform technical choices.
• Ensure all feature designs comply with Zurich IT governance, Cloud Centre of Excellence (CCoE) standards, and information security requirements.
• Provide architectural review and technical oversight on deliveries from the Databricks engineering team — enforcing implementation standards: cyclomatic complexity, null handling, logging, and partition discipline.
• Act as the technical bridge between actuarial business users, Product Owners, and the Spain/India delivery team; communicate trade-offs and risks clearly to each audience.
• Support the BA team in translating BRD requirements into deliverable technical scope, identifying assumptions and open items early.
• Operate effectively in a geo-dispersed model: structured as