InMobi | SDE 2 | Cleared & Offered
Anonymous User
1661
  • Status: Cleared all rounds (Offered)
  • Experience: 4.2 years
  • Role: SDE 2
  • Location: Bangalore (In-person + Virtual)

Compensation

  • Base Salary: ₹38L
  • Signing Bonus: ₹5L (Split over 2 years)
  • Performance Bonus: Not specified
  • Stock/RSUs: 250 Units (Vested over 4 years)
  • Total CTC (First Year): ₹44L - ₹46L

Round 1: Technical (DSA)

Verdict: Cleared

The focus was on efficient algorithms and graph theory.

  • Problem 1: A variation of the "Koko Eating Bananas" problem (LC 875). Required identifying the search space for the rate of consumption and applying Binary Search on Answer.
  • Problem 2: Evaluated a set of equations with variables and values. This was a direct application of LC 399 (Evaluate Division). Solved it using a Graph (DFS/BFS) approach to find paths between variables.

Round 3: High-Level Design (Bar Raiser)

Verdict: Cleared

This round was taken by a very senior engineer and focused on system resilience.

  • Problem: Design a Distributed Job Scheduler.
  • Key Requirements: High Availability, Durability, and exactly-once processing (or at least retry mechanisms).
  • Discussion Points: * How to manage job statuses (Queued, Running, Failed, Completed).
    • Database choice for persistence (SQL vs. NoSQL).
    • Handling retries and dead-letter queues (DLQ).

Round 4: Technical (DSA & Logic)

Verdict: Cleared

  • Problem 1: Given an array, find the minimum and maximum elements using the optimal number of comparisons (fewer than ). Used the tournament method/pairing approach.
  • Problem 2: A Graph problem involving a country with multiple disconnected cities. The task was to find the Minimum edges required to connect all components.
    • Approach: Found the number of "Connected Components" using Union Find (DSU). If there are components, we need edges.

Round 5: Low-Level Design (LLD)

Verdict: Cleared

Problem: Design a Railway Reservation System (similar to IRCTC).

  • Requirements: * Define core Entities: User, Train, Station, Route, Seat, Booking.
    • Class Diagram and Relationships (One-to-Many, Many-to-Many).
    • Handling concurrency during seat booking (Pessimistic vs. Optimistic locking).
    • Implementation of the core booking logic.

Round 6: Hiring Manager & Leadership

Verdict: Cleared

Two separate rounds focused on "Techno-Managerial" aspects.

  • Topics: Deep dive into my current architecture, technical ownership, and how I handle cross-team dependencies.
  • Scenarios: "Tell me about a time you disagreed with a technical decision," and "How do you handle high-pressure deadlines?"

Final Thoughts & Tips

The process was a mix of in-person and virtual rounds. They value candidates who can go deep into System Design and High Availability. For LLD, ensure you can write clean, modular code on a whiteboard/paper.

Comments (3)