InMobi Interview Experience, 2024 (On Campus)
Interview Experience
I was recently placed at InMobi as an SDE 1.InMobi is a global leader in mobile advertising, headquartered in India. Founded in 2007, it offers a platform connecting brand...
Full Details
I was recently placed at InMobi as an SDE 1. InMobi is a global leader in mobile advertising, headquartered in India. Founded in 2007, it offers a platform connecting brands, developers, and publishers. Its services include programmatic, native, video, and location-based advertising. InMobi provides robust analytics tools and has a global reach. It has been recognized as a leading player in the industry and has received numerous awards for its contributions. It was also India’s first Unicorn. Mode of application: On Campus 2. Recruitment Process Overview There was 1 online assessment and 3 in-person interviews: Online Assessment Technical Interview Tech/Managerial Interview HR Round 3. Rounds 3.1 Online Assessment There were 3 DSA Easy to Medium level questions: Simple ratio problem. I couldn't clear 1 hidden test case out of 15. Sliding window problem; all test cases
passed. DSA question on DP/Binary search; all test cases
passed. Out of 120 students, 18 were shortlisted for the interview rounds based on this online assessment. 3.2 Technical Round The interviewer was very nice and told me to relax. First, he went through my resume and asked about everything in it, from my internship to all the projects in detail. He grilled me a lot on some of the projects. Then he asked two DSA questions. The first question was similar to "Rotate String." Instead of characters, the string contained words separated by blank spaces. He was not looking for an optimal solution; he wanted to see all the possible solutions and how far I could go. The second question was "Roman to Integer." I took a little bit of time, but I could answer both questions. This round lasted about 1 hour. 3.4 Tech/Managerial Round Out of 18 students, around 10 were shortlisted for this round. This round started with an easy DSA question: Delete the Nth node from the end of the given linked list . Once I answered this question, the interviewer moved on to system design concepts like Load Balancing, Shared Procedures, Concurrency, and different architectures. I could answer almost all of them. Then she asked me about the coding languages I knew, and she asked basic questions on Python. Then she asked about a few of my hobbies, which I had mentioned in my resume. This round also lasted about 1 hour. 3.5 HR Round Out of 10 students, around 8 were shortlisted for this round. This was purely non-technical. The interviewer basically asked where I was from and other general HR questions. He also tested how I would react to different situations. This round lasted around 45 minutes.
Note: The final list was chosen based on performance in all the rounds. Finally, 5 students were selected out of 8 for the role. It was definitely a challenging experience, but the interviewers were very friendly and open to any doubts.
About This Question
This is a candidate experience report from a inmobi interview for a swe role (intern level) during the oa round reported in 2025.
It covers the following topics: Two Pointers, Linked List, Strings, Sliding Window, Dynamic Programming, Binary Search, Os, System Design .
Difficulty rating: Easy
Topics
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.