Marketplaces. Social commerce. Quick commerce. Each retail media network has its own data model, its own vocabulary, and its own way of describing a campaign. A bid is not always a bid. A budget cap is not always the same field. An ad object on one platform may not have a direct equivalent on another.

We built a Unified Campaign model to solve this — a single, normalized structure that abstracts away platform differences so that automation, analytics, and product features can be built once and work everywhere.

As a Backend Engineer on the Data Unification team, you will own the pipelines and transformation logic that make this possible. You'll work with raw performance media data, map it into clean, consistent structures, and ensure the unified model stays accurate and current, even as platforms evolve and edge cases multiply.

This is a role for engineers who love the craft of data modeling and pipeline engineering, who take pride in making messy real-world data behave, and who want their work to be the foundation everything else is built on.

Every Performance Media Network exposes data differently.

Campaign hierarchies differ: some platforms have ad groups between campaigns and ad objects; others don't. Attribute names and semantics vary: daily budget, bidding strategy, status codes: none are standardized across platforms. Data freshness varies: some platforms push events; others require polling. Some fields update in real time; others lag by hours.

Platform automations change state without notifying you — and your pipeline needs to detect and reconcile that.

The Unified Campaign model is the layer that hides all of this complexity from the rest of the system. Your job is to keep that layer correct, complete, and current.