Data Analyst

Data analysts in games work with telemetry, player behaviour and campaign numbers, and turn them into decisions the game and marketing teams can act on.

A data analyst in a games company sits between the raw event stream and the people who decide what to build next. The work starts with the pipeline and the query: pulling player events out of a warehouse with SQL, cleaning them, and checking that what looks like a drop in retention is not a tracking bug. Python and dashboarding tools carry the analysis from there, and a large part of the job is designing and reading A/B tests so that a result holds up.

The questions come from two directions. Game teams ask about progression, difficulty, retention and the economy; marketing and user acquisition ask about campaign spend, cohorts and lifetime value. Both expect an answer that is short enough to act on.

Compared with a data engineer, who builds and operates the pipelines, the analyst owns the interpretation. Compared with a game analyst, the scope is wider than one title and reaches into commercial reporting.

Where these positions are: Barcelona (4 positions), Paris (3 positions), Berlin (2 positions), Cambridge (1 position), Cologne (1 position), Katowice (1 position), Leuven (1 position), Limassol (1 position), Lyon (1 position)