Interested in working with us? We are hiring!
See open positions
Better late than never, but we wanted to share a video from last fall’s AWS re:Invent conference where our own chief architect Valentino Volonghi shared the stage with Amazon CTO Werner Vogels for a fireside chat.
Here’s how we added JSCS, a JavaScript style checker, to our git workflow.
AdRoll is heading to Erlang Factory SF Bay Area..
In which a member of our Real-Time Bidding team discusses his experience with exometer, an Erlang library for building monitoring solutions.
Until recently, when our customers created a campaign, they could choose to target the whole world, the U.S. or create a list of specific countries and U.S. metros (e.g. the San Francisco Bay Area, the Atlanta metro, etc.). Last week, we added the ability to target or exclude countries, metros, regions (e.g. states in the U.S., provinces in Canada,…), cities and postal codes. That meant doing a significant refactor of our geolocation code, which lead me to (finally) use Deferred objects.
AdRoll is going gangbuster when it comes to hiring engineers. We’re adding headcount in a very competitive market on an ongoing basis, and we continue to differentiate ourselves with the depth and complexity of our engineering problems. We take a very collaborative approach to engineering but give individuals a high degree of project ownership. While we bounce ideas off one another and learn together, each engineer is tackling large problems directly tied to the company’s bottom line.
In rolling out our real time bidding infrastructure, we were faced with the task of syncing data for every user we could possibly target across four regions. We have on the order of hundreds of millions of users, and tens of thousands of writes per second. Not only do we have to deal with the daunting task of writing this data out in real time, the bidding system has a hard cap of 100ms for every bid request, so we need strong guarantees on read performance.
Anybody that has worked with AWS must deal with the arbitrary hostnames that AWS generates for each instance. These names are difficult to remember and not particularly useful to understand what tasks any particular node is assigned to.
As perfect as jQuery may seem, sometimes its default behaviors end up being very surprising to the uninitiated.
At AdRoll, we have a lot of data to deal with. As we keep accumulating all of this data, our scaling issues become more complicated, and even something as simple as counting becomes a bit of a chore. After using Bloom filters to count uniques, we eventually wanted to find something more space efficient.