Shadowing Practice: System Design Mock Interview: Design WhatsApp - Learn English Speaking with Video

בחר מצב תרגול

כל מצב פותח חדר תרגול במסך מלא.

264 משפטים

אם המשפטים קצרים או ארוכים מדי, לחץ על ערוך כדי להתאים אותם.

can you tell me how you would design WhatsApp?

Hey everyone, welcome back to another Exponent System Design mock interview.

My name is Kevin Wei and on today's show we have Roshan.

Before we get started, Roshan, do you mind telling the audience just a little bit about yourself and then we'll get into the mock interview?

Of course, Kevin.

Thank you.

Thank you so much for inviting me to this interview.

My name is like roshan i work as a sd2 at amazon

and yeah i spend most of my time building highly scalable systems

and you know uh creating impact in the lives of billions of people excellent thank you roshan

so let's do this question today can you tell me how you would design whatsapp yeah of course

so maybe like usually whenever we start the system designs first we start with collecting all the requirements

so Kevin what I'm gonna do is first you know try to get all the requirements

that the WhatsApp application could have because today like you know everybody's aware of WhatsApp

and it has like a bunch of features

but in the interest of time maybe we will be developing only some you know essential features is that fine Kevin?

Yeah that sounds good maybe you can tell me what these essential features what the priorities might be sure

so yeah maybe i'll start writing it down

so first thing like maybe we can start with very basic

so today whatsapp is used uh you know to send

and receive messages uh you know um between um two peers

so yeah this is one of the most basic feature where

two person like one person one person can you know send

and receive message to another person

so this is like a you know the minimum feature

that any typical chat application should have the second uh one could be you know a group messaging where a member

would create a group they will add some x number of people in the group

and whenever the person sends the message all the other parties in the group will receive it

and everybody will know that who has sent that message

so that's the second feature that we may have

and we can also have like once the message has been

sent you know um the other person would be really interested

to know whether it has been delivered second one would be

like rather it should there should be three things three receipts basically the sent receipt the delivered receipt

and the read receipt so maybe in case

if we want we can add that as well sent delivered and read receipt

so yeah this could be another feature um so kevin anything uh

so far like on these three features do you want to add something yeah this makes sense sending

and receiving messages this seems like p0

group messaging is interesting and sending delivering read receipts just to let the user know

that the app is working and that everything that they're doing is working as planned

i think we can stick with this for now and then

if we want to add more features we can

if we have time okay so now maybe i'll just ask some more clarifying questions on this uh the first feature

so when we say messages

so are we talking only about the text messages are uh

you know the the person can send documents images videos um is that feature available in the first version

yeah great question let's assume that most of the messages are going to be text or images okay okay

okay got it so i think uh yeah so maybe i let me add some uh title in here

whatsapp system requirements okay

so now uh maybe i'll proceed with the you know the

design of like what what is going through my mind so um let me let me draw some icons in here

nice i love it some visuals for us yeah so let's say like this is the user a

and we also have another user in here B.

Okay.

So now we need some kind of a protocol where A can communicate to B

but in a more secured way so that we don't get, you know, like some third party should not be able to, you know, decode the message and,

you know, read it because that would be a pretty awful experience for the user B.

like to the to both the users for that matter.

So we need some kind of a protocol where we can you know establish

that communication and I think we have something called web sockets.

So web sockets was specially designed for peer-to-peer communication.

So maybe I can quickly write that down one second.

um web sockets however uh just using web sockets won't work uh how would like how would my system know

that you know this uh this user b is present in

some network like b should b would be connected to some network right

so we need some kind of a you know database where we know

to which box is a connected to and

which box is b connected to

so let me just change this a bit let me put this here

and let me remove this line over here and yeah

so let's say maybe i can here okay so now let me see

okay so we need api gateway

okay

so basically what would happen is this you know this phone

this this user a is connected to api gateway one

and there's another user b which is connected to ap api gateway two Now, maybe we can have a microservice.

Let me put that here.

And we can call it as a session service.

One second.

Session microservice.

Basically, the responsibility of session microservice is to connect with a DB.

And it will tell us which user is connected to which box or which API gateway.

So, maybe I think, yeah.

So say suppose when the message

when A wants to send a message to B it would first go to API Gateway

and then connect to this microservice

and this microservice will fetch you know the box number of the user B

and then the session microservice will connect back to API Gateway number 2

and from there it will go to API Gateway to be

and the protocol that we will be using here is web sockets maybe i can write that down real quick

so this is how i think i would be able to you know send

and receive messages and i think this solution is also pretty scalable how are we going to ensure

that is maybe the type of database that we will maintain here is maybe NoSQL database.

We can use that for scalability purposes as well.

Yeah, NoSQL like maybe DynamoDB.

So why would you use NoSQL here rather than a relational or SQL database?

As in when the number of users grows, we want the systems to scale, right?

And NoSQL are one of the most of the time why we use no sequels

100

because it helps us during scaling and

101

we don't have to stick to one schema the schema could be pretty dynamic

102

so yeah okay for scalability yeah it makes sense yeah

103

and maybe i think i can quickly write that format as well

104

so for now i'm just thinking of a key value pair so it could have something like um the key

105

and yeah so the key could be the you know um user

106

and the value could be the the box uh or the gateway

107

so by that by that way we'll be able to identify

108

which user is in which box so yeah so

109

that would only this this problem this particular design will solve the first requirement

110

but we still have not addressed the images thing

111

so usually for static content we have s3

112

that is the most preferred feature like you know most preferred option

113

so maybe i i think i would stick to that

114

so maybe i think when

115

when user wants to send a image right the only difference between text

116

and image here is um by the way we are not planning to store this uh text anyway right

117

because as soon as uh as soon as this um text

118

reaches the session microservice we are only going to get the user name

119

and their box number

120

and then send the text message as it is we don't

121

need to store this text anyway however in case of images i'm thinking would it make sense to store it um

122

we we can say that we don't want to store it just

123

because we don't store text

124

so we also don't want to store images for privacy yeah privacy purposes okay

125

so yeah in

126

that case then i think we are good with first requirement

127

maybe before we go to second requirement let's complete the third one So send, delivered and released.

128

Now, as soon as, you know, this user A has sent a message,

129

like as soon as a message is received by the session microservice, what we can also do is immediately send a response back,

130

like an acknowledgement to user a

131

that your message has been received by us this session microservice can do

132

that so maybe what we can also do is like let me put

133

that real quick okay and the text here would be a read um message um send acknowledgement

134

okay and maybe let me put some numbers as well

135

so basically the the number one here indicates uh the first part of it

136

because the message has been sent now once the session microservice has got the box number of the user b

137

and once it has sent that message to b

138

what we can do is it can send back an acknowledgement to session microservice

139

so maybe let me put it this way um api gateway

140

and from here to session microservice and let me add some numbers here

141

so this is more of a message received acknowledgement and

142

And what I can also do here is I can add another text in here.

143

It says message delivered acknowledgement.

144

Okay.

145

So just to summarize, user A has sent a message to APA Gateway.

146

APA Gateway would have communicated to session microservice.

147

And as soon as the session microservice has got a message from A, it will send a message sent acknowledgement.

148

That is point number one.

149

and session microservice would interact with DB.

150

It would get the box number and it knows exactly where user B is.

151

So it would go to API gateway 2 and API like you know this message will get redirected to B.

152

Now as soon as the message is you know received by B, B can again send a acknowledgement.

153

So that is point number 2 and as soon as session microservice gets that acknowledgement

154

it will send a message delivered acknowledgement to A.

155

So, you know, sent has been covered, delivered has been covered.

156

Now read receipt.

157

So the thing is, as soon as the user B opens the message, we can do exactly similar thing what we did for, you know, point number two.

158

So maybe I think I can draw another box in here.

159

So what happens here when user B reads the message?

160

yeah message read acknowledgement yeah

161

so now once the message has been read we need to you know somehow indicate

162

that to user a right

163

so what we can do is again we can use the

164

typical feature of what whatsapp is already averaging like maybe changing the color of the double ticks

165

so as soon as session microservice communicates that to a the the double ticks might be changed to double blue ticks.

166

So that would be point number four, I believe.

167

This is point number four.

168

Yeah, that makes sense.

169

Cool, yeah, that makes sense.

170

So this makes sense for peer-to-peer texts and images.

171

The texts and images are not stored.

172

They're just transmitted through the network.

173

We have sent, delivered, and read receipts.

174

Can we cover the group messages here?

175

So now let us talk about the group messaging.

176

So what essentially are we trying to achieve here is step number one, some user will create a group.

177

Step number two, the user will add some X number of people.

178

By the way, I forgot to ask this Kevin, how many, what is the maximum number of people who can be in the group?

179

yeah for simplicity let's say 10 people okay maybe I think I can write

180

that down real quick max 10 members yeah

181

and feel free to tell me

182

if in the future we want to change this to like 99

183

or 999 how that would change so maybe I think I can write

184

that down um should be scalable to more than 100 plus members okay got it

185

so maybe i'll think i'll start with 10 first

186

and then let's see how we can uh make it more scalable kevin so yeah

187

so maybe i'm just thinking of how i can tweak the existing design a bit to start supporting the group messaging.

188

So here if you see when a message was sent,

189

we had this key value pair with only one user and only one box.

190

So what if we have a list of a map?

191

So whenever a group will get created.

192

So what would happen is a list will get created with

193

them with a map having the key as the user and its associated box number.

194

So by that way, what would happen is whenever a message is sent,

195

the microservice or the messaging microservice will iterate over each of the elements in the list

196

or rather the the key value pair it will check the you know the the you know the user name

197

and its associated box number and it will exactly follow all the procedures

198

that we have created for one does that make sense kevin yep that makes sense How can we ensure scalability here?

199

Okay, the problem here is that when we are sending a message, we don't want to send the message in sequential order.

200

We can actually parallel, you know, parallelize things here.

201

We can ensure that, like, say suppose there are 100 members in the list, we can separate them in a batch of 10 or 20.

202

And we can have a main thread who will initiate a message, you know, who will initiate the group messaging, but the child thread will,

203

you know, equally distribute the number of items in the list and then send it to them parallel. By that way,

204

the other set of members in the list do not have to wait until the first set of members are done.

205

Got it.

206

Cool.

207

All right.

208

That takes our group messaging.

209

I have one more question before we wrap things up.

210

So you have user A here connected to API Gateway 1, you have user B connected to API Gateway 2.

211

If we have user C, where would user C be connected to?

212

Is it to their own API gateway or would they share a gateway?

213

No, they can share their gateway.

214

It's not mandatory that they need to have their own gateway can definitely share the gateways okay

215

and how would the how are the users assigned to the gateways is it uh randomly

216

or is there some structure there uh well for now i don't think we need any structure

217

but yeah they will be assigned randomly given okay got it

218

cool thanks roshan uh i think i understand where you're getting with this uh you somehow want to ensure

219

that not all the users end up in getting connected to one gateway right right

220

so i think yeah in order to solve

221

that problem what we can do is we can have a

222

limit on the number of users getting connected to a gateway

223

so by that as soon as that

224

that count reaches the max count we know

225

that okay the gateway is fully occupied now we have to move to the next gateway yeah

226

that makes sense um yeah thanks for clarifying

227

that point for me all right cool um thanks rishan for

228

your time i have a few pieces of pieces of feedback here

229

that i'd love to point out

230

and then i'd love it to turn it back to you

231

maybe you can give some advice to the audience as well yeah

232

so you did a really good job prioritizing the features in

233

the beginning figuring out what should be in the mvp you know whatsapp is a huge app

234

and you you were able to pick the ones that are most important to discuss for the MVP.

235

I think you also did a really good job of distinguishing some of the ambiguous parts of the question.

236

So, like sending and receiving messages, this could be anything from text to photos to videos to audio messages.

237

And you did a good job pointing out that ambiguity and helping to hone in the scope there around text and images.

238

And the last point I wanted to make is

239

that you did a really good job checking in with me and figuring out what questions I was trying to ask you, not only at the end there, but also in the beginning.

240

After you finished talking about sending and receiving messages, you didn't just move on to the next part of the question.

241

You paused and you asked me if I had any questions before moving on.

242

So I really appreciate your mock interview here.

243

And before we wrap things up, do you have any pieces of advice for the audience if they have their own system design interview?

244

yeah of course thank you kevin thank you for acknowledging this mock interview

245

and for people who are you know watching this video right

246

now um maybe i think i would just summarize of whatever

247

kevin has said just try to ask as many clarifying questions

248

that you have

249

because uh the only person to whom you can talk during the interview is your interviewer

250

so they are the ones who who will who are you who are here to help you out

251

so maybe you can ask as much clarifying questions

252

and whenever you are designing something so whatever is going through your mind

253

or whatever you are drawing just uh you know call it out loud

254

so that the interviewer knows what is going through your mind

255

and in case if you make any mistakes they will immediately stop you

256

or you know they might tell you to uh you know tweak your solution a bit

257

so yeah the key thing here is during the system design interview it's really really important

258

that you keep talking to your interviewer instead of you know just keeping it with yourself

259

so yeah makes sense thank you roshan thanks for the audience for watching

260

and good luck with your upcoming system design mock interview thanks

261

so much for watching don't forget to hit the like

262

and subscribe buttons below to let us know that this video is valuable for you.

263

And of course, check out hundreds more videos just like this at tryexponent.com.

264

Thanks for watching and good luck on your upcoming interview.

הורד אפליקציה

כל מה שאתה צריך כדי לדבר בשטף

הגיית AIציון לכל משפט

תרגול IPAשלוט בכל צליל

אוצר מיליםבנה את מאגר המילים שלך

משחק אוצר מיליםלמד תוך כדי משחק

סרוק QR

Download on theApp Store Get it onGoogle Play

אותו ערוץ

FOR YOU

המלץ על סרטון

239 משפטים

Excellent 2 Years AWS DevOps Engineer Mock Interview with Questions and Answers | Cloud | Docker

Business EnglishInterview EnglishUniversity Students

324 משפטים

Distributed Task Scheduler: System Design Interview (Stripe & Amazon Offers)

Business EnglishInterview EnglishUniversity Students

715 משפטים

Mastering iOS Development: Mock Interview with Ramiro Neto

Business EnglishInterview EnglishUniversity Students

356 משפטים

Concurrency in Low-level Design Interviews w/ Staff Engineer

Business EnglishInterview EnglishUniversity Students

95 משפטים

API Gateways in System Design Interviews w/ Ex-Meta Staff Engineer

Business EnglishInterview EnglishUniversity Students

315 משפטים

Small Talk Tips From a Matchmaker: Start Your Story in the MIDDLE!

Business EnglishInterview EnglishUniversity Students

160 משפטים

[2026] TOEFL iBT Speaking Take an Interview | Step-by-Step Strategies #0008

TOEFL PrepBusiness EnglishInterview English

129 משפטים

How to Become a Great Software Developer — Best Advice from Top-Notch Engineers

Business EnglishInterview EnglishUniversity Students

96 משפטים

01 - Course Introduction - Shopify App development with Remix

Business EnglishUniversity StudentsWorking Adults

82 משפטים

Customer Support Mock Interview | Customer Support Interview Questions | Customer Support

Business EnglishInterview EnglishUniversity Students

אוצר מילים והערות הגייה לשיעור הזה

שיעור הדיבור הזה ברמה C1 מבוסס על הסרטון “System Design Mock Interview: Design WhatsApp”. המילים שחוזרות הכי הרבה: message, user, gateway, microservice, send. בסרטון הזה יש 264 משפטים ו-3264 מילים לתרגול Shadowing. הדיבור נמשך 22:22. הדובר שומר על קצב יציב של כ-146 מילים בדקה, קצב נוח לתרגול Shadowing. 86% מהמילים נמצאות בין 3,000 המילים הנפוצות ביותר באנגלית; כדאי ללמוד את השאר לפני שמתחילים.

אוצר מילים מרכזי בסרטון הזה

13 המילים המתקדמות ביותר בסרטון, עם ההגייה והמשמעות שלהן:

מילה	הגייה	משמעות
socket שם עצם	/ˈsɑkɪt/	שֶׁקַע
mock פועל	/mɑk/	סנט
clarify פועל	/ˈklæɹ.ɪ.faɪ/	הבהיר
tick שם עצם	/tɪk/	קַרְצִיָּה
summarize פועל	/ˈsʌməˌɹaɪz/	סיכם
ambiguous שם תואר	/æmˈbɪɡ.ju.əs/	דו משמעי
fetch פועל	/fɛt͡ʃ/	הביא, השיג
simplicity שם עצם	/sɪmˈplɪsɪti/	פשטות
distribute פועל	/dɪˈstɹɪbjuːt/	חילק
distinguish פועל	/dɪˈstɪŋ.ɡwɪʃ/	הבחין
sequel שם עצם	/ˈsiːkwəl/	המשך
pause שם עצם	/pɔːz/	אתנח
subscribe פועל	/səbˈskɹaɪb/	נִמְנָה

Phrasal verbs שתשמעו

מילה	משמעות
figure out פועל	הֵבִין, מצא תשובה
check out פועל	בדק

דקדוק בסרטון הזה

המבנים שהדובר משתמש בהם הכי הרבה, עם המילים המדויקות מהסרטון:

מבנה	בסרטון
משפטי תנאי (Conditional sentences) if + clause, will/would + verb — תנאי ותוצאה שלו	If we have user C, where would user · if you make any mistakes they will immediately
הווה מושלם (Present perfect) have/has + past participle — פעולה שקרתה בעבר ועדיין יש לה חשיבות או השפעה עכשיו	has sent · has been · has been delivered
סביל (Passive voice) be + past participle — הדגש הוא על מה שקורה, לא על מי שעושה את הפעולה	has been delivered · would be connected · is connected
משפטי זיקה (Relative clauses) who / which + clause — מידע נוסף על אדם או דבר	people who can · people who are · ones who who

הגייה ששווה לשים לב אליה

הדובר משתמש ב-28 קיצורים וצורות מקוצרות, כמו don't, I'll, I'm. אמרו אותם בצורה הקצרה, כפי שאתם שומעים אותם.

הצלילים של “sh” ו-“zh”: initiate /ɪˈnɪʃ.i.eɪt/, distinguish /dɪˈstɪŋ.ɡwɪʃ/, specially /ˈspɛʃəli/
מילים ארוכות — שימו לב להטעמה: acknowledgment /əkˈnɑ.lɪd͡ʒ.mənt/, scalability /ˌskeɪ.ləˈbɪl.ɪ.ti/, initiate /ɪˈnɪʃ.i.eɪt/, ambiguity /æm.bɪˈɡjuː.ɪ.ti/, prioritize /pɹaɪˈɒɹ.ə.taɪz/

צלילים שדוברי עברית מתקשים בהם:

/w/ — שפתיים מעוגלות, לא /v/: gateway /ˈɡeɪtˌweɪ/, tweak /twiːk/, sequential /səˈkwɛntʃəl/, distinguish /dɪˈstɪŋ.ɡwɪʃ/, sequel /ˈsiːkwəl/
/æ/ — פתוח יותר מה-“אֶ” העברית, לא כמו “a” ב-“cup”: clarify /ˈklæɹ.ɪ.faɪ/, randomly /ˈɹændm̩li/, ambiguity /æm.bɪˈɡjuː.ɪ.ti/, ambiguous /æmˈbɪɡ.ju.əs/, transmit /tɹænsˈmɪt/
/r/ — הלשון לא נוגעת בשום מקום, לא ה-“ר” הגרונית: receipt /ɹɪˈsiːt/, clarify /ˈklæɹ.ɪ.faɪ/, summarize /ˈsʌməˌɹaɪz/, randomly /ˈɹændm̩li/, iterate /ˈɪtəɹeɪt/

איך לתרגל עם הסרטון הזה

הקשיבו לכל הסרטון פעם אחת בלי לדבר, ורשמו את המילים שאתם לא מכירים.
תרגלו Shadowing משפט אחר משפט במהירות רגילה, וחזרו על כל משפט עד שהקצב שלכם תואם את הדובר.
הקליטו את עצמכם והשוו למקור, תוך תשומת לב למילים כמו socket, mock, clarify.

מהי טכניקת השאדואינג?

שאדואינג היא טכניקת למידת שפה מבוססת מדע שפותחה במקור להכשרת מתורגמנים מקצועיים ופופולרית על ידי הפוליגלוט ד"ר אלכסנדר ארגואלס. השיטה פשוטה אך עוצמתית: אתה מקשיב לאודיו באנגלית ילידית וחוזר עליו בקול רם מיד — כמו צל העוקב אחרי הדובר עם עיכוב של 1–2 שניות בלבד. בניגוד להאזנה פסיבית או תרגילי דקדוק, שאדואינג מכריח את המוח והשרירים בפה לעבד ולשחזר דפוסי דיבור אמיתיים בו זמנית. מחקרים מראים שזה משפר משמעותית את דיוק ההגייה, האינטונציה, הקצב, הדיבור המחובר, הבנת השמיעה ושטף הדיבור — מה שהופך אותו לאחת השיטות היעילות ביותר להכנה לIELTS Speaking ולתקשורת באנגלית בעולם האמיתי.

טכניקת Shadowing: קרא את המדריך המלא שלב אחר שלב →

Shadowing Practice: System Design Mock Interview: Design WhatsApp - Learn English Speaking with Video

בחר מצב תרגול

הורד אפליקציה

אותו ערוץ

Uber Data Engineering Mock Interview - Ride-Sharing Data Warehouse Schema

FULL Data Science Mock Interview | SQL, Statistics, Business

What is an API?

System Design Mock Interview: Design Facebook Messenger

How to Answer System Design Interview Questions (Complete Guide)

Senior Product Designer Mock Interview: App Critique of Yelp

Understanding TCP vs UDP

What REALLY Happens in Meta’s AI Product Sense Round

Anthropic Culture Fit | Behavioral Interview

המלץ על סרטון

Excellent 2 Years AWS DevOps Engineer Mock Interview with Questions and Answers | Cloud | Docker

Distributed Task Scheduler: System Design Interview (Stripe & Amazon Offers)

Mastering iOS Development: Mock Interview with Ramiro Neto

Concurrency in Low-level Design Interviews w/ Staff Engineer

API Gateways in System Design Interviews w/ Ex-Meta Staff Engineer

Small Talk Tips From a Matchmaker: Start Your Story in the MIDDLE!

[2026] TOEFL iBT Speaking Take an Interview | Step-by-Step Strategies #0008

How to Become a Great Software Developer — Best Advice from Top-Notch Engineers

01 - Course Introduction - Shopify App development with Remix

Customer Support Mock Interview | Customer Support Interview Questions | Customer Support

אוצר מילים והערות הגייה לשיעור הזה

אוצר מילים מרכזי בסרטון הזה

Phrasal verbs שתשמעו

דקדוק בסרטון הזה

הגייה ששווה לשים לב אליה

איך לתרגל עם הסרטון הזה

מהי טכניקת השאדואינג?