As part of its Architecture team, Gaming1 is looking for an Enterprise Architect with a broad, cross-functional scope, operating across multiple business domains and capabilities rather than being dedicated to a single domain. Within an assigned transversal scope, the EA has clear architectural decision rights and is accountable for turning enterprise strategy into coherent capability evolution, target architecture, and transformation roadmaps .
Reporting to the Head of Enterprise Architecture, the EA bridges business strategy, capability planning, and technology execution. The EA works closely with the VP of Architecture and, depending on the transversal scope, other relevant VPs. This is a business-facing architecture role with substantial technical depth: the EA is not expected to be the deepest implementation expert, but must be able to reason confidently about distributed solution designs, challenge architectural choices, and understand how local decisions shape the evolution of the enterprise landscape.
The EA has no direct reports and leads through clarity, influence, technical credibility, and decision quality. On enterprise-wide initiatives, the EA actively spars with Product Managers, Heads of Product, Heads of Engineering, architects, engineering teams, and senior business leaders to turn strategic ambiguity into coherent, executable choices.
1. Enterprise Capability & Target Architecture
- Own and continuously evolve Gaming1's Enterprise Capability Map as a shared business-technology model, reflecting strategic initiatives, capability maturity, ownership, and relevant dependencies in close alignment with business and technology stakeholders
- Own the Target Architecture for the assigned transversal scope: assess the AS-IS and TO-BE landscape, identify capability and technology gaps, and shape a coherent direction aligned with business strategy, regulatory constraints, cultural targets, and the intended evolution of Gaming1's distributed platform landscape
- Define architecture principles, guardrails, and decision criteria that allow Domain Architects and teams to move autonomously while remaining coherent with the enterprise-wide target architecture
- Shape the evolution of Gaming1's distributed architecture: reason deliberately about domain and service boundaries, interaction models, event-driven and request-response communication, commands versus events, orchestration versus choreography, consistency boundaries, ownership, resilience, and failure propagation. Identify and reduce semantic, temporal, deployment, data, and operational coupling so that distributed solutions remain independently evolvable rather than becoming a distributed monolith.
2. Transformation Roadmaps & Execution
- Build and steer incremental transformation roadmaps that bridge the Current and Target Architecture, making business outcomes, sequencing, dependencies, and trade-offs explicit
- Act as a senior architecture decision-maker in Design Authority discussions, weighing risk, benefit, reversibility, and enterprise coherence for solution designs that span multiple domains
- Shape initiatives early with Product Managers, Heads of Product, and Heads of Engineering, especially during ideation and discovery, so intended outcomes, capability impact, architectural constraints, solution options, and cross-domain dependencies are understood before implementation commitments harden
- When an enterprise-wide initiative needs unblocking, convene the right people and drive the decision to closure; use workshops, proofs of concept, or reference patterns where useful, typically together with Principal Architects and engineering teams
3. Cross-Domain & Business Alignment
- Act as a primary architecture sparring partner for Product Managers, Heads of Product, Heads of Engineering, C-level leaders, and relevant VPs on assigned transversal topics; challenge assumptions constructively and make the architectural consequences of strategic and product choices visible early
- Translate business and product ambition into capability and technology choices, and explain the Current and Target Architecture, decision rationale, trade-offs, and landscape consequences so that leaders and teams can make informed choices rather than discovering architectural constraints late in delivery
- Represent the transformation roadmap externally where relevant, using benchmarking and discussions with vendors and technology partners to challenge assumptions and improve direction
4. Architectural Practice & Enablement
- Maintain and improve the Architecture Repository, framework, and methodology, keeping governance proportionate and focused on accelerating good decisions and execution rather than producing artifacts for their own sake
- Make architecture knowledge reusable and accessible through clear documentation, training, reusable patterns, and automation where valuable
- Identify and sponsor opportunities where AI can accelerate the product engineering flow from idea through production and optimization, as well as the architecture practice itself, in coordination with the dedicated AI governance function
- Surface architecture-related information security, privacy, and compliance risks early and engage the relevant SMSI, security, and compliance functions in line with Gaming1 governance; ownership of those control functions remains with them
YOUR PROFILE
- Proven experience as an Enterprise or Solution Architect in a complex, multi-domain organization, with evidence of shaping direction beyond a single product or technology domain
- Strong business acumen and technical judgement: able to translate strategy, product intent, and capability needs into architecture while credibly challenging technical assumptions and trade-offs
- Strong knowledge of distributed-system design and integration architecture, including domain and service boundaries, synchronous and asynchronous interaction models, event-driven architecture, commands versus events, orchestration and choreography, consistency models, transaction boundaries, idempotency, ordering, concurrency, resilience, failure propagation, data ownership, and contract evolution. Able to identify semantic, temporal, deployment, data, and operational coupling, recognise distributed-monolith failure modes, and select technologies only after the architectural intent and trade-offs are clear.
- Able to turn ambiguous strategic problems into decision-ready options, target states, principles, guardrails, and executable transformation roadmaps
- Skilled in capability mapping, target architecture definition, landscape analysis, and transformation roadmapping
- Comfortable operating without formal authority and making difficult cross-domain decisions through influence, credibility, transparency, and clear direction
- Strong stakeholder management and sparring skills across Product Managers, Heads of Product, Heads of Engineering, C-level leaders and relevant VPs, Domain Architects, Enterprise Architects, Principal Architects, engineers, and vendors
- Experience contributing to Design Authority-type governance and communicating complex architecture choices simply, including the risks, benefits, dependencies, and consequences of a decision
#J-18808-Ljbffr
