Games Backend Engineering

Alessia Meier

Games Backend Engineering Lead

Position and full job description

Design, implement and document the approved Card Universe server backend, including identity and authorisation, game and package registry, APIs, authoritative multiplayer sessions, matchmaking and persistence. Validate game-state transitions, concurrency, idempotency, reconnect and recovery. Maintain automated unit, integration and adversarial tests; measure capacity and latency against agreed targets. Implement security controls, observability, backup and restore, and rollback procedures within authorised scope. Preserve requirements traceability, versioned code and reproducible technical evidence; escalate missing specifications or access promptly. Work with Games product leadership, Daniel on technical assessment and infrastructure, and Adrian on integration. The formal reporting line is pending confirmation. Independent reviewers assess quality and security. The role has no self-authorised production deployment, destructive migration or live-user data access.

Technical remit

• Identity, authentication and authorisation; game and package registry; versioned APIs.
• Authoritative multiplayer sessions, matchmaking, persistence, game-state transitions and reconnect recovery.
• Concurrency, idempotency, automated unit and integration tests, adversarial tests, capacity and latency measurement.
• Security controls, observability, backup and restore, and rollback within authorised scope.

Working relationships and controls

Games product leadership defines the approved product scope. Daniel coordinates technical assessment and infrastructure; Adrian coordinates integration. The formal reporting line remains unconfirmed. Independent quality and security reviewers assess the evidence. Alessia cannot self-authorise production deployment, destructive migration or live-user data access.

Proposed first 90 days

Subject to confirmed scope and access: days 1–30, requirements, threat model and a tested vertical slice; days 31–60, one agreed game’s session, matchmaking, persistence and reconnect path; days 61–90, a staging pilot, independent test results and operational handover. These are planning milestones, not accepted deadlines or a promise to complete the catalogue.

Current assessment

Daniel’s current authorised exercise is an isolated synthetic Node.js SessionRegistry. It does not confer Card Universe access or demonstrate production readiness.