About Traffic Label

Traffic Label is a fast-growing, data-driven technology company operating in the iGaming and affiliate marketing space, building scalable products focused on performance, analytics, and automation across global markets.

What we’re building

We’re building a Customer Data Platform: one unified player profile across our group of brands. The platform should help the business:

• Improve acquisition. Understand who actually converts, and why others don’

• Increase conversion. Replace generic flows with journeys built for the specific player in front of us.

• Segment players properly. Who’s a high-value player? Who’s at risk of leaving? Who’s a VIP?

• Reactivate before churn. Spot players who are about to leave and bring them back with offers that match what they actually want.

Tech stack:

• Snowflake (with Snowpipe and Cortex Analyst LLM agent).

• dbt, Python.

• Airflow (Astronomer), AWS (S3, Lambda), Terraform, GitHub Actions.

• Omni BI on top. Reverse ETL into marketing platforms.

• Medallion architecture: bronze, silver, gold.

We’re early in the build, and the person we hire helps shape the foundation.

Role Overview

You sit between the business (Product Owner, stakeholders) and the engineering team.
About 30% of your time is practical data work: validating that CDP capabilities behave as specified, exploring data before specs are written, testing hypotheses for new capabilities, building shared gold layer models that consumer teams use, and helping those teams understand what data is available. It is not business reporting or analytics built for individual brands.

The other 70% is Systems Analysis: turning what you find into specs engineers can build from, owning data quality from symptom to root cause, raising what isn’t right before it ships, and shaping the semantic layer so other business lines can find and trust the data.

Four things define the systems analysis side:

1. Turn business intent into specs that engineers can build from. Talk to stakeholders, figure out what they actually need, and write it down. Each spec covers source schema, target model, transformation logic, business glossary, schedule, data quality checks, consumer, and use case. Stay reachable through development. Engineers will have questions.

2. Find and fix data quality problems at the root, alongside the engineering function. Trace lineage, identify the cause, work with the data source owner on the fix, check downstream impact, and close the loop.

3. Confirm what’s delivered does what we said it would. Validate against the spec you wrote. When the data isn’t right, you raise it before it ships.

4. Make data usable beyond the team that asked for it. Contribute to the semantic layer, data descriptions, and shared definitions so other business lines can find what they need, understand what it means, and trust it without going through you each time.

You work on the Data Platform layer:

CDP build, identity resolution, data quality, semantic definitions, and governance. Business analytics on top of the platform, such as dashboards and performance reports for specific brands, is produced by analyst teams aligned to those brands. Your job is to make sure those teams can do theirs: trustworthy data, clear definitions, fast issue resolution.

The team

You sit within the Data Platform alongside:

• A Product Owner who sets the roadmap and business priorities.

• The Data Engineering function. Your manager (Data Engineering Lead) and the engineers building the platform.

• Embedded QA function. Owns automated validation.

• Shared DevOps across the wider organisation.

Where you’ll start

Identity resolution. Deterministic matching is already running in our MDM across five data sources. You extend coverage to the remaining sources and validate match quality at scale. The harder cases are future scope: hashed identifiers without keys, duplicates across sources, device and behaviour signals. They start when we add dedicated ML engineering capacity, with no committed timeline yet. You’ll own the spec and acceptance for that work when it begins.

Skills & Experience

• SQL. Expert level. Window functions, complex joins, and root cause investigation on large datasets.

• dbt. Practical experience. You can write models, write tests, and debug them.

• Python. Comfortable for ad hoc analysis, scripting, and data manipulation.

• Confident across the modern data stack. You investigate problems yourself instead of waiting for DE, and you can explain the root cause to the business in plain language.

• Medallion or layered data architectures.

• You’ve written specifications that engineers built from.

• You’ve owned a data quality problem from “something looks off” to “fixed at source”.

• You can talk to business stakeholders and a backend engineer in the same hour without losing either of them.

• Background in iGaming, affiliate marketing, SaaS, or other high-volume digital businesses.

• Experience unifying customer or user profiles across sources, sometimes called Customer 360 or Single Customer View. Angles: identity matching, semantic modelling, etc.

What We Offer

• Opportunity to work on scalable, high-impact products in a growing iGaming business

• Collaborative and fast-paced engineering environment

• Exposure to modern technologies and architecture

• Competitive salary and performance-based incentives

• Flexible working environment and supportive team culture