listing details

Site Reliability Engineer

Location: New York City

Site Reliability 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. 

Site Reliability Engineers will write code to monitor and ensure the uptime of real-time systems that process terabytes of data per day and play a mission-critical role for some of the world's largest publishers, media companies, and technology companies. Work hand-in-hand with a small sub-team of core backend developers. 

Role and Responsibilities

  • Manage availability, latency, scalability and efficiency of company services by engineering reliability into software and systems

  • Respond to and resolve emergent service problems; build automated tools to prevent problem recurrence

  • Review and influence new and evolving design, architecture, standards, and methods for operating services and systems

  • Participate in software and system performance analysis and tuning, service capacity planning and demand forecasting

  • Perform periodic on-call duties 


  • BA/BS degree in Computer Science or related field (in lieu of degree, 4 years of relevant work experience)

  • 3+ years of relevant work experience, including with UNIX/Linux systems requiring the use of languages like Python, C, C++, Java, Shell, or PHP

  • Technical troubleshooting and performance tuning experience



Warning: Unknown: open(/home/content/13/2422513/tmp/sess_g47h2pkjregjffs6lct2icm8b3, 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