Real, anonymous reports from people who interviewed for Software Engineer at Tripadvisor, newest first and distilled into what to expect across the loop.
I went through a pretty structured, multi-stage loop. It started with an HR conversation where we covered broad background and role fit, and it also included a few quick, basic technical check-ins. After that, I had a tech screen that felt more like problem-solving than memorization: I worked through an easy LeetCode-style question, talked through OOP and data structures, and then ended with an open-ended technical problem.
I had a relatively easy, straightforward path. I received an email for a meeting well before the day of the interview, so I had time to prepare. The overall process felt good in terms of how clearly they communicated what was happening.
The interview process typically starts with an HR conversation followed by multiple technical rounds, often including coding challenges and system design discussions. Candidates noted that the timeline felt fast once initiated, but some experienced a lack of follow-up communication afterward.
Candidates faced a mix of LeetCode-style coding questions and system design discussions, with varying emphasis on problem-solving versus rote memorization. The technical evaluations often included discussions on algorithms, data structures, and OOP principles.
Interviews included behavioral questions aimed at assessing cultural fit, with a focus on past experiences and project discussions. The tone of these interviews was generally supportive, allowing candidates to express their thought processes.
The overall difficulty of the interviews was perceived as average, but candidates reported feeling pressure during coding tasks and system design discussions. Some candidates expressed surprise at receiving negative feedback that seemed misaligned with their performance.
While initial communication from recruiters was often clear and supportive, many candidates experienced a lack of follow-up after the interview process, leading to feelings of uncertainty and disappointment.
Candidates encountered different formats, including pair programming, whiteboard challenges, and coding on CoderPad, which influenced their comfort levels and performance. The collaborative nature of some interviews was noted as both a challenge and a positive aspect.