One of my favorite events throughout the year is the trivago tech get together. It’s the one time where we all get together to celebrate tech. Here are some impressions from 2019: See all those happy people mingling in person? Guess it’s obvious why we had to change this up for 2020. Why internal conferences are still important We managed to get a lot done this year, but communication across teams was getting harder through virtual meetings.
Metrics are one of the main building blocks in the topic of observability and we use them heavily. This story is about an incident where we tried to find and resolve a problem that we saw in these metrics. We went down a rabbit hole of potential fixes, only to discover that the metrics were correct all along.
At trivago we are working heavily on the web platform and, based on the scale that we need to serve our users, our applications need to cater for many different kinds of environments and conditions. As one of our use cases demanded we look into how a background (and possibly terminating) state is defined in the modern web, we investigated the options and discovered a few interesting points, specifically about thePage Visibility API.
What does Data Science at trivago look like in practice? Which major challenges have we encountered as a travel-tech company since the COVID-19 outbreak? What’s it like to work in Data Science at trivago? In this Q&A with James Neaves (Business Intelligence Lead), Andrea Fernandez (Data Science Team Lead), and Sheetij Jain (Product Manager in User Profiling) we’ll answer all these questions and more. Too Long; Didn’t Read? Jump directly to the questions!
This is part two of our series about trivago engineer’s side projects. The first part is here. As always, take a look and feel free to reach out to any of them if you’d like to exchange on any of their topics! Hello Rust Our backend engineer Matthias Endler is running a YouTube channel about the Rust project as a side-project. In there he explains the ins and outs of the language, but his goal is not only to present information; rather, he’s striving to inspire fellow developers to try the language and stay curious.
Fanatic learning is one of trivago’s core values that forms a fundamental part of our engineering culture. It’s very valuable to have curious minds around you that connect the dots to come up with new ideas and love to exchange knowledge on various topics. Since many of our engineers are involved in their own initiatives and projects outside work, we decided to introduce you to some of these side projects. The goal is to recognize their achievements and share their knowledge with our broader tech community.
Over the past few months, I was given the opportunity to try out the life of a Product Owner (PO), alongside retaining my responsibilities as an engineer. The life of a PO has always intrigued me since I joined trivago 2 years ago, and I always found myself unofficially taking on roles that were traditionally done by them. Things like reaching out to stakeholders for collaboration, thinking about KPIs and impact, and general “aligning”.
Tackling hard problems is like going on an adventure. Solving a technical challenge feels like finding a hidden treasure. Want to go treasure hunting with us?View all current job openings
In our new series, trivago Tech Check-in, we’re introducing you to some of our tech talents from across the globe who help keep our metasearch engine running smoothly everyday. In this first edition, you’ll meet Fabian Fritzsche, an engineering intern that works on the Microservice-System that feeds our GraphQL API with up-to-date hotel data.
At trivago we operate a hybrid infrastructure of both on-premise machines and clusters on Google Cloud. Over time, we came up with a set of deployment guidelines for running our workloads as more and more of them are migrating to Google Cloud. These are not strict rules, but rather suggestions to best serve each team’s needs. Teams are meant to have full control over their workloads, but most of the time they “just want to run things” and do not have the time or resources to care much about managing the underlying infrastructure.