Yassir

Backend Engineer - Ad Serving & Integrations

Yassir·LinkedIn·Algiers, Algeria·Hybrid·Full-time·1 day ago
Kawarizmi

About the role

title: "Backend Engineer - Ad Serving & Integrations"

subtitle: "Rust

  • Distributed Systems
  • Ad-tech"
  • Backend Engineer - Ad Serving & Integrations

-Context & Vision

In 2026, writing code is no longer the primary bottleneck; managing its complexity and ensuring its reliability is. We are building a highly resilient advertising platform with a very lean, senior internal team, and we intend to keep it that way.

To achieve scale without the overhead of a large engineering department, we rely on an AI-first development paradigm and a philosophy borrowed from the best large-scale open-source projects. Our code is not public, but our governance is theirs: asynchronous communication, exhaustive written documentation, explicit rules, and uncompromising quality gates. It is the only way a small team of humans and AI agents ships serious systems without accumulating technical debt.

This role owns the part of that platform where money and latency meet: the serving path and the integrations to external ad systems.

-The Role

You will own, end to end, the connectors and serving logic that turn an ad request into a served, billed impression. This is hands-on, systems-level backend work with a direct revenue impact and a low tolerance for error.

  • Ad Serving & Integrations. Build and own the integrations to external ad servers and demand partners, the serving gateway, and the augmentation and bidding logic that sits between them. You are the person who understands, precisely, how these systems talk to each other and why.
  • Correctness on the Hot Path. The serving path is real-time and handles money. You will hold the line on latency, on monetary correctness, on idempotency, and on the reconciliation between what was decided, what was cleared, and what was billed. A silent error here is a production incident.
  • AI-First Delivery.We expect AI to write the majority of the code; you are the editor, not the typist. You will specify work as explicit, self-sufficient issues, direct agentic tooling (e.g. Claude…
View all