TinyOwl Technologies Interview Experience | Set 1 (On-Campus)
Question Details
Here is a brief description of my Interview Experience of TinyOwl TechnologiesROUND 1: ONLINE TEST (Hackerrank Platform)1 coding question to be done in 1 hour. Difficulty:...
Full Details
Here is a brief description of my Interview Experience of TinyOwl Technologies
ROUND 1 ONLINE TEST (Hackerrank Platform) 1 coding question to be done in 1 hour. Difficulty: Easy 1) Given a set of strings, we have to determine whether the strings represent valid IPv4 addresses/IPv6 addresses or neither of the two. (Basically, it was a String manipulation question).
ROUND 2 TECHNICAL INTERVIEW 1 (20 min) Difficulty: Easy 1) Given an array with integer data items, we need to find the minimum number of jumps needed to reach the end of the array where the number of cells we can jump at each step is equal to or less than the integer data item at that array index. 2) To find the lowest common ancestor of two nodes in a binary search tree. 3) Basic questions on Databases, Tables and SQL queries. Questions based on resume.
ROUND 3 TECHNICAL INTERVIEW 2 (1.5 hrs) Difficulty: Average 1) Implement a queue using stacks. 2) Breadth-first search in a Binary Tree. 3) Search an item in a matrix where all the elements are in ascending order both row and column-wise. Implement it using the best time complexity(worst-case). 4) Basic implementation of a priority queue. 5) Ranking of search results based on input keyword. 6) Questions related to web error status codes, server applications. 7) How to monitor CPU/Memory usage of various processes in Linux. Questions based on resume.
About This Question
This is a reported interview question from a tinyowl interview for a swe role during the oa round reported in 2015.
It covers the following topics: Heap, Trees, Strings, Binary Tree, Binary Search, Sql, Graph, Stack Queue, Queue, Arrays, Matrix .
Difficulty rating: Easy
About Tinyowl Interview Reports
This question was reported by a candidate who interviewed at Tinyowl. 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 Tinyowl are the higher-signal extractions to take from this report.
For broader preparation context, the Tinyowl 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 Tinyowl reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Tinyowl 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 Tinyowl 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.