SQL

SQL appears wherever a game produces data: accounts and inventories, progression and economy, telemetry, and the reports a team steers by.

Backend work uses it against the live schema behind progression, matchmaking and purchases, where indexing, migrations under load and query cost are the daily concerns. A migration that locks a table is an outage in a live title.

Analytical work uses it against a warehouse to answer why retention dropped in the second session or which offer paid for itself. The queries are larger, the stakes per statement smaller, and the output is a dashboard rather than a service.

The requirement list says which of the two a position means: a server language, containers and cloud services point to the first, statistics and reporting tools to the second. Both are called SQL, and operating a schema that thousands of concurrent players write to is a different craft from explaining their behaviour afterwards.

Where these positions are: Barcelona (6 positions), Paris (5 positions), London (4 positions), Belgrade (2 positions), Berlin (2 positions), Dublin (2 positions), Hamburg (2 positions), Lyon (2 positions), Cambridge (1 position), Cologne (1 position), Katowice (1 position), Leuven (1 position), Limassol (1 position), Lleida (1 position), Nicosia (1 position), Regensburg (1 position), St. Julian’s (1 position), Stockholm (1 position), Wrocław (1 position)