> Markdown version of [/jobs/ext/2728385-staff-backend-software-engineer](https://www.wearedevelopers.com/jobs/ext/2728385-staff-backend-software-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Staff Backend Software Engineer - **Company:** Vibe - **Location:** Paris, France - **Contract:** Permanent contract - **Skills:** Java (Programming Language), C++ (Programming Language), Software Debugging, Distributed Systems, PID Controllers, Redis, Backend, Apache Kafka, Machine Learning Operations, Data Pipelines - **Published:** September 5, 2026 - **Apply:** https://startup.jobs/staff-backend-software-engineer-performance-vibe-8128290 ## About the Role * Shipped backend systems in a strongly typed language C++, Rust, Go, Scala, Java, or equivalent at production scale * Debugged distributed systems under real traffic: latency issues, consistency failures, the works * Worked inside a DSP, SSP, or bidder: you understand auction mechanics from the inside * Built or tuned pacing algorithms or PID controllers theory and implementation, not just awareness * Solid grounding in probabilistic reasoning and statistical modelling you think in distributions, not just averages Nice to Haves * Experience in a scale-up environment you know what fast and resource-constrained actually feels like * ML systems in production: feature pipelines, model serving (not just training notebooks) * Real-time data pipelines and low-latency architectures at scale * Redis, Kafka, or equivalent under meaningful load ## Description You'll join the Performance team the engineers who own advertiser outcomes at Vibe. Bidding, pacing, and the prediction stack that drives both. You'll report to Clément Schiano, Engineering Manager for Performance. This role exists because our roadmap is clear and the bottleneck is execution. We have a knowledge concentration problem too: critical expertise sits with one person, which creates fragility. We need someone who can absorb, challenge, and extend that knowledge not just ship tickets. Three reasons someone great would want this job: 1. CTV performance advertising is still being invented. The auction dynamics, identity graph, and feedback loops are nothing like display or search. There's no playbook to copy you'd be writing it. 2. You own the full decision loop. From prediction to bid price to pacing, on a product real advertisers depend on today. Your judgment shapes the direction. You'll see the impact in the numbers within weeks. 3. The timing is right. Past "does this work?" and into "how fast can we scale this?" Early enough to shape the architecture. Late enough that you're not building on sand. What You'll Do Own the pacer and bidder * Go deep on the bidder and pacer stack map it end-to-end and identify at least one fragility worth owning on day one * Propose improvements to the bidder or pacer autonomously from problem definition through to design proposal * Ship measurable improvements to CPx, pacing accuracy, or win rate within your first three months Raise the team's ceiling * Distribute critical system knowledge: make the team faster and less dependent on any single person * Challenge existing designs, including inherited ones, and push for cleaner solutions * Deepen expertise in the theoretical foundations (probabilistic modelling, PID control theory) powering our approaches Move at Vibe pace * Use AI tooling as a genuine force multiplier (not a crutch, not a checkbox) * Iterate in production, not in your head, we - ship, measure and adjust ## Related Videos - [Reducing LLM Calls with Vector Search Patterns - Raphael De Lio (Redis)](https://www.wearedevelopers.com/videos/1714-reducing-llm-calls-with-vector-search-patterns-raphael-de-lio-redis) - [Developing the Backend with Stefan Lingler, CTO at Shpock](https://www.wearedevelopers.com/videos/100360-developing-the-backend-with-stefan-lingler-cto-at-shpock) - [How to Benchmark Your Apache Kafka](https://www.wearedevelopers.com/videos/76-how-to-benchmark-your-apache-kafka) - [Build and Deploy a Fullstack App with Open Source Tooling](https://www.wearedevelopers.com/videos/775-build-and-deploy-a-fullstack-app-with-open-source-tooling) - [Meet Your New BFF: Backend to Frontend without the Duct Tape](https://www.wearedevelopers.com/videos/682-meet-your-new-bff-backend-to-frontend-without-the-duct-tape) - [Accelerating Authentication Architecture: Taking Passwordless to the Next Level](https://www.wearedevelopers.com/videos/733-accelerating-authentication-architecture-taking-passwordless-to-the-next-level) ## Related Articles - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [The 7 Most Popular Backend Frameworks for Developers](https://www.wearedevelopers.com/magazine/403-the-7-most-popular-backend-frameworks-for-developers) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Lessons for Vibe Coders and Developers](https://www.wearedevelopers.com/magazine/614-lessons-for-vibe-coders-and-developers) - [What’s the Difference Between Frontend and Backend Development?](https://www.wearedevelopers.com/magazine/240-what-s-the-difference-between-frontend-and-backend-development)