Tripadvisor software engineer candidates report an HR or recruiter screen, easy-to-medium coding rounds, and a behavioral finish. Several also describe a system design or code-review stage, which one candidate said decided the outcome.
$146K
Avg. Base Comp
$210K
Avg. Total Comp
4-7 rounds
Typical Rounds
Not reported
Process Length
Candidates describe Tripadvisor's software engineer process as friendly but broader than a typical coding screen. Reports of the coding problems are fairly consistent: easy to medium LeetCode-style questions, with balanced brackets or Valid Parentheses appearing in several accounts. Individual reports add Min Stack, merge intervals, Ransom Note, a word-by-word string reversal and a tic-tac-toe depth-first search. Complexity analysis also came up, so practice explaining why a solution has its complexity, not just passing it.
The early screen can be more technical than its name suggests. Two candidates report that the HR call included about four quick data structure questions. One describes stack concepts such as FILO and LIFO alongside complexity questions.
System design and code review appear to be where some candidates lost ground. One candidate who reached a final round was turned down after a checkout-page performance problem, and another stumbled on diagnosing bottlenecks in a slow system. A third was asked to critique a code sample and later faced a high-availability, fault-tolerant design. Fundamentals beyond algorithms also came up, including Java and network knowledge.
Round counts run from four to seven, and timing varies. One candidate finished in about a week, while another described seven rounds over two to three weeks. One candidate reported an offer, while most others did not. Plan for the full loop, and prepare concrete project stories for the final manager conversation, which candidates describe as behavioral and conversational.
Synthesized from 14 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Tripadvisor process.
I had an HR screen and then a tech screen. They were on the easy side because they sent me an interview preparation guide and I had prepared accordingly. I feel confident and I think I passed both interviews.
Questions asked: The HR screen was relatively simple - some standard behavioural questions like why are you leaving your current company or why are you interested in Tripadvisor, and then 4 easy technical questions on space and time complexity of operations on data structures.
In the tech screen I solved an easy string LeetCode-style question and then was questioned on Java fundamentals (how does a HashMap work), SQL (inner join vs left join) and networking (HTTP verbs).
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Tripadvisor
Minimum Change
| Question | |
|---|---|
| Find the Missing Number | |
| Find the First Non-Repeating Character in a String | |
| Level Of Rain Water In 2D Terrain | |
| Google Maps Improvement | |
| Nearest Common Ancestor | |
| Type-ahead Search | |
| Reservoir Sampling Stream | |
| Hurdles In Data Projects | |
| Success Measurement | |
| Target Indices | |
| Same Characters | |
| Binary Tree Validation | |
| String Palindromes | |
| Impossibly Iterative Fibonacci | |
| LRU Cache 1 | |
| Tic-Tac-Toe Outcome | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Monthly Customer Report | |
| Top 3 Users | |
| Random SQL Sample | |
| Prime to N | |
| String Shift | |
| Rolling Bank Transactions | |
| Bagging vs Boosting |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a recruiter or HR call covering background and the role. Two say it also included about four quick data structure questions, and one mentions stack concepts such as FILO and LIFO plus complexity analysis. Expect to answer fundamentals briefly and cleanly.
Candidates typically describe an easy or easy-to-medium problem, often brackets matching or Valid Parentheses, a string question, or a stack problem. One candidate also reports data structure and networking questions, and another was asked about Java, so fundamentals may come up alongside coding.
Reports of the middle rounds vary in length and emphasis. Candidates mention LeetCode-style problems such as Min Stack, Ransom Note, merge intervals, or a tic-tac-toe depth-first search, and complexity analysis came up in more than one report. One candidate was also asked to review existing code.
Several candidates report a design component. Examples include diagnosing a slow checkout page, a high-availability and fault-tolerant design, and bottlenecks in an existing system. One candidate said this stage decided the outcome even though the role did not emphasize it, so prepare for caching, database and scaling trade-offs.
Candidates report a final conversation with a manager or culture-fit interviewer about role expectations and how they handled specific situations. Reports describe it as conversational rather than an interrogation. Prepare concrete project stories with outcomes.
