Lesson 177 — Advanced
Capstone: Full Mock GenAI Interview Loop
Capstone mein tum poore L15 ko ek functioning loop mein jodoge: ek full mock interview jo tum khud conduct karo, khud score karo, aur khud improve karo. Design round se debugging scenario tak, project defense se behavioral tak — har round ke liye ek plan, har round ke liye ek rubric, aur ek honest scorecard jo agle hafte ka prep plan khud likhe degi. Ye hi woh artifact hai jo "maine interview prep ki hai" ko "yeh raha proof" bana deta hai.
Capstone kya hai — deliverables
Kya hai?
Full mock GenAI interview loop: warmup → AI system design → debugging scenario → project defense → behavioral — 60 minute, timer ke saath, aloud. Har round ke baad rubric pe score, aur ek action plan jo agla mock improve kare.
Kab kaam aata hai?
Real interview se pehle ke 2-4 hafte mein, weekly ek loop. Aur har mock ke baad — kyunki bina score ke mock sirf ek baithak hai, practice nahi.
Kahan milta hai?
Dost ke saath mutual mocks, ya khud camera/record ke saath. Ye capability hi interview ke alawa on-call drills aur design reviews mein bhi kaam aati hai.
Capstone ka success criteria: tumhare paas ek scored mock loop ka record hai — schedule, questions, rubric scores, aur improvement notes. Aur tumne apni sabse kamzor jagah ko ek specific drill bana diya hai, general "aur padhunga" nahi. L15.1 ke prep plan ka yahi aakhri delivery hai.
60-minute loop ka plan
mock_loop: # timer laga lo, aloud bolo, record karo
warmup_5min: "apne ek project ka 2-minute version" (ice-breaker)
design_15min: "design karo: <enterprise assistant ya coding assistant>"
-> assumptions, simplest architecture, trade-offs, break-first
debugging_10min: "RAG quality ek hafte baad giri — kya karoge?"
-> stage-wise isolation, golden set, rollback/investigate
project_defense_15min: ek project deep-dive: choices, numbers, failures
behavioral_10min: "ek time batao jab design galat nikli" + pressure questions
questions_5min: tum interviewer se poochho (bhi ek signal hai)
after: 15min scoring + notes (record suno/jo bola wo likho)
- Design round: L15.6 wala frame — assumptions sheet, simplest viable, har add justified, break-first. Timer 15 min, zyada nahi.
- Debugging round: L15.5 wala frame — timeline, stage-wise suspects, "verify karunga" wali lines. Ye round sabse zyada practice maangta hai.
- Project defense: apna one-pager (L15.8) kholo, par bina padhe bolo — jitna ratt gaya hai wahi dikhega.
- Behavioral: structure (situation → decision → result → lessons) + assumptions-first habit. Ek round hi, par recorded.
- Question bhi poochho: interview ke end mein 2-3 sawaal poochhna bhi signal hai — curiosity aur preparation dono.
Self-scoring rubric — scorecard jo action likhe
rubric_per_round: # 1-5, evidence ke saath (kahan dikha)
assumptions_stated: kya assumptions pehle boli (ya chupke se le li)
structure_followed: frame (L15.5/6/8) follow hua ya random bolayi
tradeoffs_named: har major choice ke saath cost boli
numbers_used: real numbers aaye (yaad/estimate label ke saath)
honesty: nahi pata wali jagah plan diya ya guess kiya
recovery: galat jaane pe checkpoint se wapas aaye
action_plan: # har mock ke baad, ek page se zyada nahi
weakest_round: <round>
weakest_item: <rubric line>
next_drill: <ek specific drill, jaise "5 debugging scenarios aloud">
next_mock_date: <date>
- Evidence ke saath score do: "structure 2 — 8 minute mein assumptions hi nahi boli, recording 03:12 pe". Bina evidence ke score self-hype ya self-criticism ban jaata hai.
- Har mock ke baad ek page ka action plan: weakest round, weakest rubric item, ek specific drill, aur agli mock ki date. Itna kaafi hai.
- Improvement ka pattern dekho: 3 mocks ke scores jod kar dekho — kaunsa rubric item sudhar raha hai, kaunsa atak gaya. Atakne wale pe hi agla drill.
- Score ko compare mat karo doosron se: apne pehle mock se compare — wahi asli measurement hai.
Final checklist — loop se pehle aur baad mein
pehle (once):
[ ] 2-3 projects ke one-pagers ready (problem -> numbers)
[ ] L15.6 wala assumption sheet rakhna yaad (mental copy)
[ ] debugging frames: timeline + stage isolation + golden set
[ ] "why not RAG / fine-tune / agent" ke teen jawab draft
[ ] "how do you stay current" wala process answer
baad mein (har mock):
[ ] recording se 3 cheezein note (1 achi, 1 sudhaarne wali, 1 surprise)
[ ] rubric scores + evidence
[ ] action plan: weakest item -> ek drill -> next date
[ ] honest iknow_not list update (jo abhi bhi nahi aata)
- Interviewers kya probe karte hain: assumptions, trade-offs, numbers, honesty, recovery — rubric mein yehi paanch line hain. Loop isi pe hona chahiye.
- Jo abhi bhi nahi aata: usko chhupao mat — ek "iknow_not list" rakho aur har mock mein usse ek drill add karo. Ye list hi tumhari finishing school hai.
- Recovery practice: mock mein jaan-boojh kar ek assumption galat bolo (ya dost se bolwao) — wapas aane ki practice bhi ek rubric item hai.
- Energy aur pacing: 60 minute aloud bolna thaka deta hai — real interview bhi wahi hai. Mock ki thakan hi pacing ki feedback hai.
Exercise
Question: Mock loop ka warmup round kis cheez se hota hai — ek project ka 2-minute version ya resume reading?
Question: Rubric ke paanch items mein se ek — "nahi pata" wali jagah kya karna chahiye: guess ya plan?
Question: Mock ke baad improvement ka source kya hai — rubric scores ya dobara attempt bina review?
Question: Design round mein sabse pehle kya bolo — assumptions ya architecture?
Question: Action plan mein weakest item ke saath kya likha jaata hai — ek specific drill ya "aur padhunga"?
Common mistakes
- Mock ko bina rubric ke lena: Achha laga / bura laga — feeling koi measurement nahi. Fix: paanch-item rubric, evidence ke saath, har round ka score.
- Sirf apne favourite round ki practice: Design smooth, debugging blank — jo chhup raha hai wahi interview mein aayega. Fix: weakest round pe sabse zyada drills, calendar mein pehle se.
- Recording bina review karna: Record kar liya par kabhi dekha nahi — "maine 3 baar assume kiya" pata hi nahi chalega. Fix: recording se 3 notes: achi cheez, sudhaar, surprise.
- Scores ko seriously na lena: Mock mein 2/5 aaya aur next week bhi wahi — loop hi nahi bana. Fix: score ke turant baad action plan + next mock date, wahi ritual asli improvement hai.
T20 match se pehle nets kyun? Kyunki match ki thakan, pressure aur shot selection sirf net mein practice se dikhte hain. Tumhara mock loop wahi nets hai: har round ek net session, rubric scorecard coaching report, aur weakest shot (rubric item) pe hi agli practice:
nets ka plan -> warmup, phir match simulation (60-min loop)
coach ki report -> rubric: assumptions, structure, trade-offs, honesty
weak shot -> "trade-offs 2/5" -> agle hafte sirf wahi drill
match day -> asli interview = aur ek net, bas purse jud gaya- Q: Capstone loop ka structure? — Warmup 5, design 15, debugging 10, project defense 15, behavioral 10, questions 5 — timer, aloud, recorded; phir scoring.
- Q: Rubric ke paanch items? — Assumptions stated, structure followed, trade-offs named, numbers used, honesty — plus recovery; sab evidence ke saath.
- Q: Score ke baad kya? — Weakest round + weakest item + ek specific drill + next mock date — ek page ka action plan, wahi asli deliverable hai.
- Q: Solo mock kaise karoge? — Camera ke saamne aloud, timer, recording; recording ko interviewer maan kar rubric. Awkward hona zaroori hai, improvement isi se.
- Q: "Maine prep kar li" ka proof kya hai? — Scored mock loops ka record + iknow_not list jo chhoti ho rahi hai. Notes nahi, evidence.
Capstone complete — ab tumhara interview prep ek measurable loop hai: mock, score, drill, repeat. L15 GenAI / AI Engineer Interview Prep yahan poora hua — ab jo bhi interview do, tum usmein soch, trade-offs aur imandari ke saath jaoge. All the best!