InMobi logo
InMobiSoftware Engineer
Updated Jan 9, 2026

InMobi Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at InMobi, newest first and distilled into what to expect across the loop.

Get your personalized InMobi Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Build my free plan
Hot & recentNewest first
8 months ago
Average Positive Lucknow

It started with an on-campus style process where a coding round came first. The problems felt moderately challenging, and I was able to qualify from there. After the coding round, I went through multiple technical interviews with three interviewers, and the whole thing ended with an HR round.

The technical portion leaned into data structures and algorithms. I remember getting asked about tries specifically, and the vibe felt fairly straightforward but still competitive. By the time I reached HR, I felt like I’d done my best to communicate clearly, but I ultimately didn’t get an offer. Looking back, the process felt like solid DSA screening end-to-end, and my performance in the later technical discussion just wasn’t enough for the final decision.
9 months ago
Difficult Positive Bengaluru

My process for the Software Engineer role felt like a strict sequence of elimination-style rounds: four rounds total, all of them competitive. I went through two DSA-focused technical rounds, then a project or resume discussion, and finally an HR round.

What stood out was how heavily the company leaned on problem-solving through DSA. The questions ranged widely—from simpler tree-related problems up through more complex trie work, with dynamic programming level problems also showing up in the mix. Overall, the difficulty felt genuinely high for me, and it matched the way the interviewers framed the process.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.

What to expect

Distilled from the reports

Technical Rounds Focus

The interview process heavily emphasizes data structures and algorithms (DSA), with multiple rounds dedicated to problem-solving in this area, often escalating in difficulty from easy to hard questions. Candidates should prepare for a wide range of topics including trees, graphs, and dynamic programming.

DSAProblem-solvingAlgorithms

Online Assessment

Candidates typically start with an online coding assessment that includes several challenging DSA questions, which serves as an initial filter before moving on to technical interviews. Success in this round is crucial for advancing in the process.

Online assessmentCodingScreening

Behavioral & HR Rounds

The final stages of the interview process include HR rounds that focus on cultural fit and communication skills, where candidates are assessed on their work-related experiences and ethical considerations. Clear communication is emphasized throughout.

HR roundBehavioralCultural fit

Interview Dynamics

Candidates report varying dynamics during interviews, with some experiencing supportive environments while others faced aggressive questioning or disorganization, impacting their overall impression of the process. It's important to remain calm and adaptable regardless of the interview style.

Interview dynamicsCommunicationAdaptability

Difficulty & Outcome

The overall difficulty of the interview process is perceived as high, with many candidates not receiving offers despite strong technical skills. Candidates should be prepared for rigorous evaluations and understand that performance in DSA rounds is critical to success.

DifficultyEvaluationOutcome

Preparation for Technical Depth

Candidates should focus on deepening their understanding of key technical concepts and problem-solving strategies, as interviewers often expect detailed reasoning and clarity in explanations, particularly in system design discussions.

Technical depthSystem designReasoning