ThinkTankers Interview Experience
Interview Experience
It is the best interview I had ever faced. The interview procedure justifies the name of the company.The interview procedure consists of 3 rounds.Round I: This round is an...
Full Details
It is the best interview I had ever faced. The interview procedure justifies the name of the company. The interview procedure consists of 3 rounds. Round I: This round is an offline written test with 40 questions. 20 aptitude. 20 English comprehension. A total of around 160 students appeared for the test and only 24 made it to the
next round. Round II: This is the craziest round I had ever attempted. This round is called as ‘ The blank paper test’. As the name suggest, we were given a blank paper and asked to write the details on the top of the paper and asked us to do whatever we wish to do with that paper. The time allotted is 20 min. The candidates who did best got call Round III: This round is held at the Head Quarters of the company at Hyderabad. My interview took place for 1 hour. There are questions from my project and remaining of them are from C, Java, Python and regarding web technologies like HTML, CSS, JS. There are various coding questions asked to solve. 1+23+45+6….. (n terms) 1+23+456+789*10+…. (n terms) We have to write code implementing the series. There are various questions on Overloading, overriding, inheritance, String vs. String buffer vs. String builder classes. Thanks to GeeksforGeeks for providing with valuable information. I’m able to answer most of the questions. I recommend every interviewee to go through GeeksforGeeks before attempting any interview. Thank you Geeks!!
About This Question
This is a candidate experience report from a thinktankers interview for a swe role reported in 2016.
It covers the following topics: Strings .
Topics
About Thinktankers Interview Reports
This question was reported by a candidate who interviewed at Thinktankers. 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 Thinktankers are the higher-signal extractions to take from this report.
For broader preparation context, the Thinktankers 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 Thinktankers reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Thinktankers 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 Thinktankers 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.