DOMAIN ARCHITECT

As part of its continued growth and platform evolution, Gaming1 is looking for a Domain Architect to shape and evolve the Engagement Area, covering the capabilities that support customer acquisition, interaction, engagement, communication and retention. This role sits at the intersection of business, architecture, product and engineering.

The Domain Architect translates business capabilities and strategic objectives into clear architectural direction, while ensuring that solutions are scalable, maintainable and aligned with the long-term platform strategy. The role combines strategic architectural ownership with pragmatic, hands‑on involvement, working closely with engineering and business teams to turn architectural vision into actionable roadmaps and delivered outcomes.

YOUR ROLE

As a Domain Architect for the Engagement Area, you will own and evolve the architecture of the area, translating business strategy and capabilities into clear architectural direction, actionable roadmaps and scalable technical solutions.

This is a highly autonomous and hands‑on architectural leadership role. You are expected to challenge assumptions, refine the architectural vision and actively drive it forward through close collaboration with business, product and engineering teams.

• Define and evolve the domain architecture, including capabilities, domain boundaries, services and integration patterns
• Translate business objectives into coherent architectural roadmaps and pragmatic technical solutions
• Design and guide scalable, resilient and maintainable distributed systems where relevant
• Define architectural principles, standards, patterns and guardrails that enable autonomous delivery
• Work closely with engineering teams in collaboration with Engineering Managers and Heads of Engineering to ensure pragmatic and high‑quality delivery
• Ensure the domain integrates coherently with the wider platform, including data, infrastructure, analytics and developer experience

YOUR PROFILE

Engagement Domain Expertise

• Strong understanding of customer acquisition, communication, engagement and retention capabilities
• Good understanding of customer journeys, engagement funnels and behavioural analytics
• Knowledge of tracking, attribution, conversion optimisation and experimentation
• Understanding of customer journey orchestration and personalization
• Broad understanding of digital experiences, including content, information modelling, design systems, metrics, UI/UX flows and user behaviour
• Able to translate engagement objectives into coherent business capabilities, domain boundaries and architectural roadmaps

Technical Expertise

• Strong background in software and backend system design
• Deep experience with microservices and distributed architectures
• Solid understanding of:
  • Event-driven systems (e.g. Kafka, messaging systems)
  • API design and integration patterns
  • Scalability, resilience, and performance optimisation
• Experience working in complex, high-throughput environments

Architecture & Design

• Strong grasp of domain-driven design principles, with the ability to define clear domain boundaries, capabilities and service ownership
• Strong analytical skills and ability to perform due diligence and deep analysis of complex domains
• Able to translate business capabilities and architectural intent into coherent, scalable solution designs
• Experienced in designing architectures that balance short‑term delivery needs with long‑term scalability, maintainability and sustainability
• Comfortable making pragmatic trade‑offs between complexity, performance, maintainability and delivery speed
• Skilled in documenting architectures, processes, capabilities and relationships using appropriate architecture tooling
• Comfortable performing hands‑on assessments, data deep‑dives and prototype validations to support architectural decisions
• Able to evaluate proposed solutions rigorously, identify architectural risks and challenge unnecessary complexity or misalignment

Leadership

• Operates independently and proactively, driving initiatives forward without requiring constant alignment or oversight
• Acts as an architectural authority for engineers, business stakeholders and leadership
• Challenges strategies, assumptions and technical decisions constructively, proposing stronger alternatives where needed
• Sets clear architectural context that enables teams to deliver autonomously
• Navigates complex stakeholder environments with diplomacy, authority and a strong sense of ownership
• Communicates architectural decisions clearly across technical