Chapter 3 · Hinglish · Sunne-wala Sabak
Interview Framework — Chaar Steps
System design interview ko ek guided conversation banane ka chaar-step routine. Niche "Play all" dabaiye aur browser pura chapter padh kar sunayega. Kisi bhi section par "Suniye" se wahin se shuru karein.
▶ Companion slides kholेंTip: jo voice sabse natural lage wahi chuniye — ek Hindi (hi-IN) ya Indian-English (en-IN) voice aam taur par best chalti hai.
Kya grade hota hai Slide 2
Chapter teen, system design interview ka framework. Open-ended design sawaal sirf tab chaotic lagte hain jab aap bina plan ke jaate ho. Sabse pehle yeh samajh lo ki interviewer kya grade kar raha hai. Woh ek finished blueprint nahi dekh raha, balki aapka thought process dekh raha hai. Chaar cheezein dekhi jaati hain. Ek, aap vague prompt ko bounded problem mein kaise badalte ho. Do, aapko building blocks ki kitni samajh hai. Teen, jab aap kuch choose karte ho to kya tradeoff batate ho. Aur chaar, aap interviewer ke saath kaise collaborate karte ho.
Chaar-step framework Slide 3
Ab framework. Chaar phases, isi order mein, har baar. Pehla, understand aur scope. Doosra, high-level design banao. Teesra, deep dive. Chautha, wrap up. Chahe sawaal chat app ho, ya ride-share, ya metrics pipeline, yahi loop chalega. Ise deliberately chalao to interview improv jaisa nahi lagega.
Step 1 — scope karo Slide 4
Pehla step, understand aur scope, lagbhag paanch se das minute. Clarifying questions koi delay nahi hain, wahi asli design hain. Sabse badi galti hoti hai aisi problem solve karna jo interviewer ne poochi hi nahi. Pehle functional requirements poocho, yaani do ya teen core user flows kya hain, kya scope se bahar hai, aur system read-heavy hai ya write-heavy. Phir non-functional, yaani scale, latency, availability, aur consistency. Yeh sab board ke corner mein likh do.
Step 2 — high-level design Slide 5
Doosra step, high-level design, lagbhag das se pandrah minute. Bas boxes aur arrows. Client, load balancer, stateless API service, cache, primary database, aur ek async path with queue aur workers. Paanch ya chhah boxes kaafi hain. Saath mein teen ya chaar API endpoints aur do ya teen core entities bata do, aur SQL ya NoSQL ka choice ek line mein justify kar do. Yeh ek skeleton hai, finished product nahi.
Step 3 — deep dive Slide 6
Teesra step, deep dive, lagbhag pandrah se bees minute. Yahin sabse zyada signal banta hai. Interviewer aam taur par aapko nudge karta hai, jaise feed kaise generate hota hai, ya agar worker beech mein mar jaaye to kya hoga. Us hint ko lo. Ek ya do components chuno aur unhe khol do. Pehle quantify karo, phir do ya teen real options batao, ek choose karo aur uska cost batao. Phir ek write aur ek read ko apne design se loud chalakar dikhao. Aur agar interviewer redirect kare, to turant current thread chhod kar naye pointer ko follow karo.
Step 4 — wrap up Slide 7
Chautha step, wrap up, lagbhag teen se paanch minute. Loop ko close karo. Dikhao ki aapko pata hai design abhi production-ready nahi hai. Bottlenecks specifically batao. Phir next moves batao, jaise database ko aur shard karna, per region read replica, ya ek CDN. Aur operations bhi, yaani aap kya log karoge, kis par alert karoge, aur SLI kya hai. Ek achhi closing line hai. Agar mujhe aur time milta to main sabse pehle X ko revisit karta, kyunki wahan maine ek tradeoff liya jiska mujhe sabse kam bharosa hai. Apni uncertainty ko own karna senior lagta hai.
Time budget Slide 8
Pacing utni hi important hai jitna content. Ek pentaalis minute ke interview ko roughly aise baanto. Scope par lagbhag aath minute, high-level design par baarah, deep dive par attharah, aur wrap up par paanch minute. Sabse common galti hai pachees minute clarifications mein laga dena aur kabhi real design tak na pahunchna. Deep dive ka hissa hamesha sabse bada rakho.
Communication Slide 9
Aap kaise baat karte ho, wahi aadha answer hai. Whiteboard par dus minute ki chuppi sabse mehngi hoti hai, kyunki interviewer wahi score kar sakta hai jo woh sunta hai. Loud socho. Assume karne se pehle confirm karo. Har choice par tradeoff narrate karo. Certainties ki jagah hypotheses se steer karo. Hint ko gracefully lo. Aur galti ho to khulkar correct karo, kyunki visible self-correction ek strength hai, weakness nahi.
Red flags Slide 10
Chaar tareeke jinse smart log bhi yeh round fail karte hain. Ek, seedha solution par kood jaana bina scope pooche. Do, scale ko ignore karna aur chupke se single database maan lena. Teen, sirf verdict dena bina tradeoff ke. Aur chaar, pushback par defensive ho jaana. Yaad rakho, interviewer ke sawaal attack nahi, invitation hote hain.
Strong-hire kaisa dikhta hai Slide 11
Ab dekho ek strong-hire signal kaisa dikhta hai. Strong hire conversation ko drive karta hai, design se pehle quantify karta hai, multiple options deta hai, ek chunta hai aur uska cost batata hai, aur apni galtiyan khud pakadta hai. Hire light prompting se kaam karta hai. Mixed candidate ko har step par steer karna padta hai. Aur no hire clarification skip karta hai, ek hi technology par atak jaata hai, aur pushback par defensive ho jaata hai. Dhyaan do, strong hire hona sahi architecture ke baare mein nahi, balki aap kaise operate karte ho uske baare mein hai.
Chhah cheezein Slide 12
To chhah cheezein yaad rakho. Ek, sketch se pehle scope karo. Do, pehle skeleton phir muscle. Teen, har choice ka cost batao. Chaar, pointer ko follow karo. Paanch, clock par nazar rakho. Aur chhah, apne gaps ko own karo.
Aage kya
Bas, yahi hai chapter teen. Ek kaam karo, koi ek classic prompt lo, jaise design Twitter, aur is chaar-step loop ko loud chalao, bina koi box banaye, sirf scope se shuru karke. Method ko reflex bana lo. Agle chapter mein hum apna pehla real system design karenge, ek rate limiter.