listing details

Backend Infrastructure Engineer

Location: New York City

Backend Infrastructure Engineer

The company is a SaaS analytics company focused on transforming brand advertising online. The company's products include Ad Search, Pro and Analytics. Ad Search is a free display ad search engine. Pro is an industry wide real-time search solution providing insights across brands, publishers, and ad tech. Analytics is a proprietary solution for advertisers and publishers to measure ad effectiveness and content engagement that exposes a new lens of attention measures that move beyond traditional digital metrics. 

Backend Infrastructure Engineers build real-time analytics systems and an industry search engine that play a mission-critical role for some of the world's largest publishers, media companies, and technology companies. In this role you will shape the future of hand-built company systems that collect and process terabytes of data per day and play a game-changing role for publishers who want to solidify their digital businesses in a privacy-friendly way. 

Role and Responsibilities

  • Shape the Web traffic, data streaming, caching, and computational strategies that will allow the company to take on our next 10x increase in traffic

  • Conceptualize, architect, and implement strategies to enhance our reliability.

  • Architect backend systems to support brand new product offerings


  • Bachelors degree in Computer Science or other Engineering discipline

  • 2+ years of experience in and advanced coding skills using Python, C, C++, Shell and Unix

  • Deep understanding of network protocols, relational or analytic databases and AWS

  • Candidates with experience with differential equations, statistics, I/O event notification mechanisms, DNS strategies and colocation strategies preferred



Warning: Unknown: open(/home/content/13/2422513/tmp/sess_4a9ojtrnh1ff34f90kvhi3l424, O_RDWR) failed: No such file or directory (2) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct () in Unknown on line 0