InMobi SDE Intern and 6-Month Intern Guide: DSA, Python Debugging and Your Projects
Prepare for InMobi SDE intern interviews with reported assessment patterns, interview questions, and preparation advice.
On this page
Last reviewed November 16, 2026.
For students applying for InMobi's SDE internship or the 6-month internship with a full-time offer (including Glance).
Built by the Codinzhub team from InMobi intern experiences that students from IIT Roorkee and MNNIT Allahabad shared on Codinzhub in 2026, plus earlier intern reports. Each one is one student's memory, so use this as a map, not a promise.
The 30-second version. InMobi's intern process looks like the SDE 1 process, only shorter. After the OA, round 1 is DSA with a Python debugging question, and round 2 is a deep dive into your resume and projects with one more coding question. For the 6-month intern plus full-time (6M + FTE) track there is also an HR round. Weak project explanations were the reason given in two rejections.
Other InMobi roles: SDE 1 · SDE intern and 6-month intern · Machine learning engineer
Round-by-round breakdown
Stage 1: Online assessment
What to expect. The same three-question coding OA as SDE 1; see the SDE 1 guide for 2026 questions by campus.
Stage 2: Round 1, DSA and debugging
At a glance
- Length: 40 to 60 minutes
- Questions per round: 2 DSA, sometimes plus 1 Python debugging
- What was asked: graphs, linked lists, arrays, trees, DP
- Most common: well-known medium problems, with a dry run
What students were asked:
- IIT Roorkee (2026): a Python debugging question, course schedule (topological sort) and merge k sorted linked lists (heap). Read the experience
- MNNIT Allahabad (6M + FTE, Glance): the longest run of consecutive increasing values in an array (for example 1, 2, 3, 4 in [100, 1, 2, 3, 200, 4]), and tree height while returning the sums of the left and right subtrees. Explain, code and dry run each. Read the experience
- IIT Roorkee (2025): matrix chain multiplication, recursive and then iterative, then a priority queue question, then projects.
Stage 3: Round 2, resume and projects
At a glance
- Length: about an hour
- Questions per round: a project deep dive plus 1 coding question
- What was asked: your AI project, token limits, RAG, a graph question
- Most common: "how did you solve this, and what if it fails?"
What to expect. The MNNIT student was asked how they handled their AI project, what happens when the token limit is exceeded, and what RAG is, then a graph question: how many separate components appear when a given edge is removed. They were rejected after this round.
Stage 4: HR (6M + FTE)
What to expect. A fit conversation for those who clear round 2.
The Codinzhub Next-Round Playbook
- Practise Python debugging: indentation, list-of-lists creation (
[[0]*m for _ in range(n)], not[[0]*m]*n), off-by-one errors. - Be able to explain every project decision and its failure modes.
- Always dry run your code on the sample before saying you are done.
About this guide
This guide is researched and written by the Codinzhub team from questions and experiences students shared on Codinzhub and in public interview write-ups, rewritten in our own words. Practice links open the full question on Codinzhub. Interviewed for this role? Share your experience on Codinzhub and we will update the guide.
Keep track of what you’ve learned.