Mobile System Design Interview - The framework

From my experience, most of Engineers working with Mobile-based products think on design only from the code structure perspective, which is fine and desirable, but eventually not enough when facing a solid Mobile System Design Interview.

On such interviews, there are way more things to explore. For instance, let's consider the use case of providing offline features to our users. A couple of questions one may ask :

How should we handle offline information when needed? How do we efficiently sync with our Backed services according to our use case? Which storage should we use? How do we handle a good offline user experience without jeopardizing the user's phone storage?

As as second example, lets consider how do we drive the integration with our Backend systems. Some questions one may ask :

As a Mobile Engineer, can you design the contract of of the API you need to integrate with? How do you handle connectivity failures? What can you propose for idempontency requirements? What can we do minimize data exchange with our Backend systems? How do we minimize battery usage when providing excellent online experiences? How can we be resilient under poor quality networks without jeopardizing our Backend systems?

Those are some of the questions that one faces in a real world Mobile System Design interview, the same interview present as mandatory step when applying to a Big Tech company, Neo Big Techs like AirBnb, Spotify, etc, and many more.

In this session, I'll help you to prepare for this interview by presenting a custom framework I created. It was designed to crack this interview in a predictable fashion.

I'll present the framework and walk you through a real Mobile System Design Interview I created and applied to candidates in the past, clarifying questions along the way.

This session will allow you to understand how the framework fits in the interview and also provide you tools to identify whether or not you are sharing the right signals with your interviewer.