Our team
Interview
Although relatively new to the programmatic ecosystem, Antonio Nicolás Dianez has quickly immersed himself in the complexities of SSP technology, bringing a strong backend foundation and a passion for continuous learning. As an SSP Backend Developer, he works on high-performance systems where speed, scalability, and reliability are critical—an environment that perfectly matches his technical curiosity and problem-solving mindset. In this interview, Antonio shares what it’s like to ramp up quickly in such a demanding space, the skills needed to thrive behind the scenes of programmatic advertising, and how understanding both the technology and the business is key to building impactful solutions.
Answer: Well, to be honest, I practically started when I joined Tappx. Although I had done some minor work before at a company in the field and touched on certain parts of their projects, I think my true start has been these last three months, where I’ve had to do some rapid learning about programmatic advertising.
A: For me, the best part is working on a system that has a real impact and requires very fine-tuned performance and reliability. In an SSP, everything happens very fast, there are many connected pieces, and any technical improvement has a massive effect. I also enjoy being in an environment where I’m learning so much. I was quite “green” regarding this topic, so this is helping me understand how this whole world works.
A: I’d say the first thing is having a solid backend foundation: data structures and databases—though ClickHouse is a bit tricky since it’s not widely used. You need knowledge of concurrency and optimization. In an SSP environment, it’s vital to understand performance and scalability because of the high volume and demanding latency requirements. Beyond the technical side, you need curiosity to understand the business—knowing why we do what we do helps in debugging complex problems and communicating with other teams.
A: I organize by priorities. First, I check for anything critical like incidents or technical blockers. Then, I try to reserve quiet blocks of time for coding or reviewing architecture.
A: Not many at all; sometimes none. Most of my communication happens through Slack or Linear tickets. I only use email for formal documentation.
A: Since I work from home, I don’t “arrive,” but I try to disconnect mentally. When I finish, I take my dog for a walk to leave the office space. This helps my brain understand the workday is over, which is better for my mental health than staying at the computer.
A: First, I’d seek financial peace of mind and help my family. Then, I’d invest wisely, maybe start my own project, and travel—which is a passion of mine. I’d probably keep programming but in a much “lighter” way, without the pressure of deadlines or losing sleep over it.
Audio interview