One of the many responsibilities of a Site Reliability Engineer (SRE), is to ensure uptime, availability and in some cases, consistency of the product. In this context, the product refers to the website, APIs, microservices, and servers. This responsibility of keeping the product up and running becomes particularly interesting if the product is used around the world 24 hours every day like trivago. And just like in the medical profession, someone has to be on call to react on failures and outages outside of the office hours.
Engineering Culture at trivago
Insights, experiences and learnings from trivago's tech teams.
At trivago, we run webservices with complex backends in different regions around the globe 24/7. Our system is being iterated and developed on a daily basis. Naturally, mistakes will be made and something will break eventually. Engineers being on-call are the first responders to issues with negative impact on our users and the business.
trivago is the home to 500+ tech specialists from all corners of the globe – each with their own unique background and story of how they ended up here. Our trivago Tech Check-in series focuses on individual engineers' experience during their time at trivago. In this edition, you'll meet Mohammad Abed – a frontend software engineer who has been with trivago for 11 months now and is working on our Express Booking product.
In the middle of summer 2021, we hosted one of our favourite annual events of the year - trivago Tech Week! This year’s tech week had a new, hybrid format, featuring a wide variety of talks and exchange forums, hosted both by internal talents and external speakers. To make things even more engaging, the week included virtual opportunities for talents to gather and converse across departments, a gaming tournament and a highly anticipated live-music concert to tie everything together!
While engineering, we fix bugs, create new systems, build workflows and establish processes. Our job is to change things. Changing things can involve mistakes that ultimately lead to the failure of a particular system. To learn from these failures, a retrospective is helpful to get to the root of this problem. In the tech industry, a Blameless PostMortem is the right tool for this job.
Five years ago trivago started to build guilds – small communities dedicated to certain topics or technologies – as a need arose to organize the collaboration of more than a hundred developers on a wide range of topics. You can read more about how we started in the previous blog posts Part I and Part II.
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:
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.