InMobi.

The rounds, as candidates describe them

1. Problem solving (third-party)A 60-minute DSA round run by BarRaiser, an external interviewing platform, with Java questions.source ↗
2. Problem solving (InMobi engineer)A second DSA round after a discussion of your current project.source ↗
3. System design (senior roles)For a Staff Engineer, a system design round, then HM, a working-code round (an in-memory pub-sub), Director and HR.source ↗
4. Hiring managerTeam and culture fit, past work, and sometimes a design discussion.source ↗

• Design a Stock Exchange / Trading PlatformSystem design
  SQ-13 · Zerodha Kite Trading Platform →W05 · DAY 05 · Leader Election and Coordination →reported in:LeetCode Discuss · InMobi Staff Engineer, Bengaluru (2022) ↗
• Build an In-Memory Pub-Sub like Kafka (Machine Coding)Low-level design
  LLD-08 · Design a Logging Framework (Pub-Sub) →IP-18 · Design a Distributed Message Queue →reported in:LeetCode Discuss · InMobi Staff Engineer, Bengaluru (2022) ↗
• Design TwitterSystem design
  SQ-10 · Twitter/X →IP-07 · Design a News Feed →reported in:LeetCode Discuss · InMobi SDE-2 Backend (2024) ↗LeetCode Discuss · InMobi SDE-2 Backend, Bangalore, Rejected (2024) ↗
• Design a Web CrawlerSystem design
  IP-05 · Design a Web Crawler →reported in:LeetCode Discuss · Glance (InMobi) SDE 4, Bangalore (2021) ↗
• How does a hash table work internally, and how do you make it thread-safe?Concept
  W00 · PART 5 · Operating System Concepts for System Design →reported in:LeetCode Discuss · InMobi, Microsoft, Flipkart, Intuit, Soroco SDE2 (2021) ↗
• Design a Hospital Appointment System with Patient Priorities (LLD)Low-level design
  no lesson for this one yetreported in:GeeksforGeeks · InMobi Interview Experience, On-Campus 2021 ↗
• How do you deprecate a feature while rolling out its replacement to clients?Concept
  W10 · DAY 03 · Deployment Strategies →reported in:LeetCode Discuss · InMobi SDE2, Bangalore Remote (2022) ↗
• What goes wrong in a master-slave setup, and how do you debug it?Concept
  W01 · DAY 02 · Replication Trade-offs →W05 · DAY 05 · Leader Election and Coordination →reported in:LeetCode Discuss · InMobi SDE2, Bangalore Remote (2022) ↗

• Design an Ad Click Aggregation SystemSystem design
  IP-16 · Design an Ad Click Aggregation System →W08 · DAY 04 · Late-Arriving Data and Correctness →
• Design a Real-Time Bidding Ad ServerSystem design
  W02 · DAY 01 · Timeout Hell →W04 · DAY 05 · Multi-Tier Caching →W01 · DAY 04 · Hot Keys and Skew →
• Design Ad Frequency Capping and Budget PacingSystem design
  W01 · DAY 03 · Rate Limiting at Scale →IP-16 · Design an Ad Click Aggregation System →
• Design a Personalised Lock-Screen Content FeedSystem design
  IP-07 · Design a News Feed →W04 · DAY 04 · Feed Caching →SQ-21 · Instagram Feed and Stories →

Study path

Every lesson the questions above point to, once, in order.

1. 01SQ-13Zerodha Kite Trading Platform
2. 02W05 · DAY 05Leader Election and Coordination
3. 03LLD-08Design a Logging Framework (Pub-Sub)
4. 04IP-18Design a Distributed Message Queue
5. 05SQ-10Twitter/X
6. 06IP-07Design a News Feed
7. 07IP-05Design a Web Crawler
8. 08W00 · PART 5Operating System Concepts for System Design
9. 09W10 · DAY 03Deployment Strategies
10. 10W01 · DAY 02Replication Trade-offs
11. 11IP-16Design an Ad Click Aggregation System
12. 12W08 · DAY 04Late-Arriving Data and Correctness
13. 13W02 · DAY 01Timeout Hell
14. 14W04 · DAY 05Multi-Tier Caching
15. 15W01 · DAY 04Hot Keys and Skew
16. 16W01 · DAY 03Rate Limiting at Scale
17. 17W04 · DAY 04Feed Caching
18. 18SQ-21Instagram Feed and Stories