Treebo Interview experience
Question Details
WRITTEN ROUND – It happened on HackerEarth1) Negative Signs : In this problem given a number N, we have to return Yes/No such that if it is possible to get sum as zero by ...
Full Details
WRITTEN ROUND – It happened on HackerEarth 1) Negative Signs : In this problem given a number N, we have to return Yes/No such that if it is possible to get sum as zero by making half the numbers as negative(for odd number take floor of half). For example, if N=3 answer will be yes for {1,2,-3} 2) OZ graph : Graph related ques, don't remember the exact problem statement. Solved it partially using BFS. ROUND 1--Started with Discussion based on my resume. 1) I have a stream of number, I need to find the median of data at a given point of time. I already knew the solution to problem so interviewer varied the question to 2) I have a stream of number, I need to find the random number from list with equal distribution. I solved the problem, then interviewer asked for mathematical proof, I had given that too. 3) For a given tree, print inOrder traversal. In the tree, leaf nodes' left pointer and right pointer are pointing to the respective leafs. I was told to write the code for it
ROUND 2 Design based round. It was more of a discussion round than a Q/A round I was told to Give a DB design for task scheduler. I was unable to provide good design, so was
rejected after this round.
About This Question
This is a reported interview question from a treebo interview for a swe role during the phone screen round reported in 2017.
It covers the following topics: Trees, Binary Tree, Graph, Probability Stats, Graphs .
Topics
About Treebo Interview Reports
This question was reported by a candidate who interviewed at Treebo. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Treebo are the higher-signal extractions to take from this report.
For broader preparation context, the Treebo interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Treebo reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Treebo Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Treebo reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.