Company Background:
Who is Nexxen?
Flexible advertising, unified by data. Nexxen empowers advertisers, agencies, publishers and broadcasters around the world to utilize data and advanced TV in the ways that are most meaningful to them. Our flexible and unified technology stack comprises a demand-side platform (“DSP”) and supply-side platform (“SSP”), with the Nexxen Data Platform at its core.
Why join the Nexxen team?
With a global footprint, you can be part of a team that is transforming advertising through our creative, flexible and unified solutions. Employees hustle, commit and dedicate themselves to pillars that make up the Nexxen Way – the 3Cs - Customer Centric, Curious Mindset, Collaborative with No Ego.
Project Description:
Team Serve — Who We Are
Serve owns the real-time serving edge of the DSP: the services that receive bid requests, render and deliver ads, and record what happened.
Service footprint- kRTBPS, PS, S2S, APS, third-party integrations, ad preview, and contextual targeting.
We sit in the hot path between ad exchanges and the bidder — processing 1.2 million requests per second in US-East alone — enhancing bid requests with the signals bidding needs, integrating with third-party APIs, and writing the measurement events that power reporting and billing.
Latency, availability, and data correctness at scale are our main focus.
What We Work On
- Product roadmap (quarterly): New features for third-party integrations and measurement collection — expanding what the platform can track, measure, and bill.
- Tech roadmap: Modernizing our systems. Current focus: splitting the monolith into a microservices codebase and building one-click deployments.
-Scaling for 2x: Doubling our request throughput over the next year — capacity planning, performance tuning, and architectural changes across the serving stack.
- Batch → stream processing: An active initiative to serialize/deserialize legacy Java log records into Kafka, moving our measurement pipelines from batch to real-time streaming.
Who we work with
- Cross-team work: We partner with the Runtime Apps team (we consume their campaign data) and the Sunflower Data team (we produce the logs that feed offline/online model training and reporting).
- Operations: Occasional P2/P3 delivery investigations (typically 1–2 every couple of months, following major system changes). PagerDuty rotation once per quarter — 24/7 for one week.
How We Work
- Two-week sprints
- Daily standup at 9:30 AM PST