trivago logo

trivago Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 46 interview experiences · FREE TO READ

2.8 Rounds average
Average Typical difficulty
60.9% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at trivago.

Showing 3 of 46
trivago logo
trivago

Software Engineer

Engineering · more than a year ago

Entry Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Group
Interview formats
Behavioral Technical Coding

The interview process was pretty straightforward. It had three parts: 1. A screening, 2. A technical assessment, and 3. A cultural fit check. Sadly, I didn't pass the technical assessment. Personally, this technical part was different from other companies' interviews where you get a Leetcode question to solve. This one was like a Leetcode question, easy difficulty, but the description was unclear. There were no examples showing what the result should be for a given input. Instead, you were supposed to ask questions to understand the problem, kind of like pair programming. I found this out after the interview when I asked for feedback. I think they should have mentioned this at the start, that we'd be assessed on figuring out the scenario. As a result, I spent too much time trying to understand the question rather than solving it.

Confirmed questions5 questions
  • Can you tell me about yourself and why you're interested in this role?
  • There was a technical assessment involving merging two lists, though it was more about filtering.
  • Could you clarify the prompt about merging the two lists?
trivago logo
trivago

Software Engineer

Engineering

Mid Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Technical Coding Behavioral

I applied for Software Engineer - Data Plumber to Master Our Hotel Data in Oct 2016 and heard back in 9 days. The interview was scheduled for two weeks later. They were super responsive to my questions about the interview. The interview had two parts: first, a general chat on personal and technical stuff, then a 30-minute programming task where I could use Google (they watched closely!) and they responded in two days. They then suggested my next interview, two weeks out, which followed the same two-part structure: a discussion and a 30-min coding task on a known problem with a tricky edge case. This was with an Engineering lead. I got confirmation the next day for an interview a week later, which lasted 2 hours. No coding this time, just deep dives into technical and non-technical skills, especially databases and their behavior since it's a data role. It was tough but friendly and supportive. Since I had another offer, I asked for a quick confirmation. I got an unofficial one via Skype, enough to decline the other offer for trivago's international environment. There were some HR/management miscommunications about the recruitment being frozen, but it turned out to be a misunderstanding. I got the contract offer a few days later, and they were helpful throughout.

Confirmed questions4 questions
  • What are indexes on Databases and how efficient are they?
  • How can a DB be optimized when there are millions of records constantly updating?
  • What are S.O.L.I.D Principles?
trivago logo
trivago

Software Engineer

Engineering

Entry Average Positive experience Accept offer 3 rounds
Interview process
Take home Recruiter call Technical screen Onsite
Interview formats
Technical Behavioral Coding

The whole thing took about two months. I applied on the Trivago careers site for the Software Engineer role in Leipzig. Five days later, they sent me a project to do, which I had to finish in 7 days. I sent it back two days after that and then waited a whole month for feedback. The recruiter eventually told me the IT team liked my project and set up a Skype call. This call had two parts: first, a chat with HR, and second, a talk with a Team Lead. A week later, the recruiter set up another interview with the Head of the IT Team. Each of these interviews lasted about an hour.

Confirmed questions3 questions
  • What do you know about Trivago and what are your motivations, including responsibilities in your current role?
  • We discussed your current job, design patterns, software testing, system performance optimization, and databases.
  • The IT Head of the office asked similar questions to the previous technical interview and some behavioral questions as well.

trivago Software Engineer Interview Questions

Quoted word for word from trivago interview reports.

Can you write code that takes a list of integers and returns a list of its unique values?

Read reports

Can you pull data from the file system and return it as a JSON using Spring Boot?

Read reports

Given a code snippet with two synchronized blocks, when could this lead to a bug, and how would you resolve it?

Read report

How can a DB be optimized when there are millions of records constantly updating?

Read report

If you visit our site and see '[]' displayed, how would you troubleshoot that?

Read report

Regarding a page with numerous images, what strategies would you employ to enhance its loading performance?

Read report

Imagine a microservice that keeps crashing. How would you go about debugging it, and what tools would you use?

Read report

Formats, difficulty and experience

Across all 46 trivago interview reports.

Interview formats

Technical 34.7%
Behavioral 29.8%
Coding 25.6%
Case 5.8%
System Design 2.5%

Interview difficulty

Easy 15.2%
Average 71.7%
Difficult 13%

Candidate experience

Negative 37%
Positive 60.9%
Neutral 2.2%