InMobi Interview Experience | On-Campus 2021
Question Details
InMobi visited our campus and conducted their interviews in December. The recruitment procedure consisted of an online screening round followed by 2 technical rounds and 1...
Full Details
InMobi visited our campus and conducted their interviews in December. The recruitment procedure consisted of an online screening round followed by 2 technical rounds and 1 HR round
Round 1 The online assessment consisted of three questions and the duration was 2 hours. It was held on DoSelect platform. The following questions were asked:- https://cses.fi/problemset/task/1674 (Something similar to this) https://www.geeksforgeeks.org/dsa/connect-n-ropes-minimum-cost/ (The only catch was that input was given in comma separated form so had to parse those) https://leetcode.com/problems/cheapest-flights-within-k-stops/ After the online round 25 people were shortlisted and 25 people in extended list. Interview was scheduled on 1st December and was to be conducted on MS Teams.
Round 2 The interviewer was quite friendly and gave his introduction and asked for the same. After this he asked an open-ended design question. The task was to design an hospital appointment system with certain priorities for patients. The main discussion point was choosing best data structures for the design purpose and object-oriented paradigms which needed to be followed.
Round 3 The interviewer was quite serious and started with DSA question. The first question he posted was quite complex to understand at first but after looking carefully it boiled down to finding next smaller element concept and I told him the stack solution. He was impressed and asked for a more optimised approach which uses constant space. After few hints from his end, I came up with the code. After this he pasted another question which was this https://leetcode.com/problems/maximum-number-of-visible-points/ Though I have seen this question but never solved it, so I was stuck for a few minutes but then I tried to explain a mathematical approach but was not getting it right. After a few hints, I deduced that this can be done using sliding window and some general maths. I quickly coded it up and he was satisfied and asked if I have any questions.
Round 4 This was a chill HR Round and he just asked basic introduction, life in Covid times, about my projects and hobbies. This round was done within 10 minutes and after a few minutes, I got a confirmation from TnP cell that I am selected in InMobi.
About This Question
This is a reported interview question from a inmobi interview for a swe role during the oa round reported in 2025.
It covers the following topics: Two Pointers, Oop, Sliding Window, Stack Queue, Stack .
Difficulty rating: Easy
More Inmobi Interview Questions
About Inmobi Interview Reports
This question was reported by a candidate who interviewed at Inmobi. 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 Inmobi are the higher-signal extractions to take from this report.
For broader preparation context, the Inmobi 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 Inmobi reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Inmobi 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 Inmobi 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.