Enterprise Applications Architect - AI & Governance in Paris

Pierre & Vacances–Center Parcs Group (PVCP), the European leader in holiday accommodation, brings together some of the tourism industry's most iconic brands—Pierre & Vacances, Center Parcs, maeva and Adagio—with operations across France and internationally, including Germany, the Netherlands, Spain and Denmark.

What you will do

Application architecture andcross-domain coherence. Curate application-levelstandards and reference patterns. Be the trusted expert teams consult oncross-domain design. Make integration patterns coherent and maintainable acrossthe systems portfolio.

Application landscape stocktake andrisk prioritisation. Conduct an honest inventory ofthe existing application portfolio across the IT departments. Identify andprioritise architectural risks (technical debt, end-of-life systems,integration brittleness, security and compliance exposure, AI-readiness gaps).Maintain the resulting risk register as a living artefact, and feed it into themulti-year roadmap and budget cycles co-authored with the Group CTO. This isthe foundational body of work for the first year and the basis on which much ofthe technology investment plan will be built.

AI architecture. Provide architectural advice on AI integration into applications:feature design, agentic tooling patterns, the security baseline for AIartefacts, and the architectural implications of LLM-based components. Thechoice and integration of agentic harnesses, including the runtime patternsthat turn LLMs into productive agents inside our application landscape, is anarea this role will shape in close partnership with the Group CTO. Not datascience or ML platform work; this is the application side of AI.

Architecture governance. Run the advice process at scale: convene the Architecture AdviceForum where significant proposals are presented, prepare and lead architecturereviews on delegation from the Group CTO, surface cross-team patterns from thebody of decisions. Arbitrate at group scope only when consensus cannot bereached. Build the case law of architecture decisions teams reference and learnfrom.

Technical advisory. Pair with teams on hard design problems. Raise architecturalmaturity through reviews, pairing, and communities of practice. This ishands-on, not a memo factory.

What success looks like

Six months in. First-cut application landscape stocktake delivered, with aprioritised architectural risk register the Group CTO can take into budgetconversations. ADR practice (structured, colocated with applicationrepositories) live across the IT departments. AAF cadence established with aregular rhythm of significant proposals reviewed. A textual C4 modellingbaseline prototyped on at least one flagship system.

Twelve months in. Top-priority risks from the stocktake reflected in the multi-yearroadmap and in the next budget cycle. A growing body of architecture decisionsaccumulating as case law across all five IT departments. Fitness functionsrunning in CI on at least two flagship services, covering structural integrity,external API conformance, and partner integration contracts. AI integrationpatterns documented and adopted by multiple product teams.

Eighteen months in. Recognised internally as the trusted technical adviser onarchitecture across the Group. Risk register live and refreshed as a workingartefact, with measurable reduction on the highest-priority items. Architecturematurity visibly improved at the team level (ADRs are written withoutprompting, fitness functions catch real regressions, the AAF runs on its ownmomentum).

Authority and governance

The role operates within the GroupCTO’s three-tier governance model (team scope, domain scope, group scope,differentiated by blast radius). Within that:

·Prepares and leads architecturereviews at domain and group scope, on delegation from the Group CTO.

·Has visibility on technicalreviews and design discussions across IT departments and is expected to engagewhere cross-domain implications arise.

·Captures architecturaldecisions made through the advice process, so they accumulate as precedent.

·Arbitrates at group scope onlywhen consensus cannot be reached, and never as a default.

·Works alongside PlatformEngineering at the application/infrastructure boundary.