SQL

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.