Behavioral Interview Prep — STAR Stories

Phase 3. Build out Months 7-9. Prep at least 8 stories.

STAR framework

• Situation: 1-2 sentences setup. Time, project, role.
• Task: what was the goal/challenge? Specific.
• Action: what YOU did. Use "I" not "we". Concrete steps.
• Result: outcome. Numbers if possible. What you learned.

Each story = 90 seconds spoken. Write them, rehearse out loud, time yourself.

Stories Yash needs (TODO — fill in as Pillars 1-3 ship)

1. Shipped under deadline (Story slot)

Situation: 7-day Max-week sprint to ship 4 products simultaneously. Task: Launch supplement-store + InvoiceAI + Content Engine + Life OS skeleton in 7 days. Action: TODO after week is done. Result: TODO with metrics.

2. Failure / what I learned

TODO — pick from a real situation. Examples: a launched product that didn't get users, a feature that had to be ripped out.

3. Conflict / disagreement

TODO — find one from your distributor relationship, customer feedback, or Reddit launch reception.

4. Most technically complex thing built

Situation: Built a faceless content engine producing 90 reels/month across 3 niches. Task: Orchestrate Claude scripts → ElevenLabs TTS → fal.ai images → WhisperX captions → Remotion video assembly → Metricool posting on cron, all error-tolerant. Action: TODO with specifics on architecture decisions (why Remotion, why BullMQ, etc.) Result: TODO with metrics (reels/day, views, conversions).

5. Built something for users you didn't know

Situation: Built InvoiceAI for Indian freelancers without being one full-time. Task: Identify pain points, validate, ship. Action: 5 customer dev calls before code, dogfooded by sending invoices to clients myself. Result: TODO.

6. Disagreed with a manager / mentor / customer

TODO.

7. Time you took ownership of something nobody asked you to

TODO.

8. Mistake you made

TODO.

Common Google behavioral questions

• "Tell me about yourself" (60 seconds, technical-focused)
• "Tell me about a project you're most proud of"
• "Describe a time you faced ambiguity"
• "Tell me about a conflict with a teammate"
• "Tell me about a time you failed"
• "How do you prioritize when you have too many things to do?" (relevant — your 4 pillars)
• "Tell me about a time you had to learn something quickly"
• "Why Google?"

"Why Google?" specifically

Don't say:

• ❌ "It's a great company"
• ❌ "I want to work on big problems"
• ❌ "FAANG was always my dream"

Do say:

• ✅ Specific products you use and why ("I've been using Google Cloud for X, and the architectural decisions in Y inspired how I built Z")
• ✅ Specific people whose work you've followed ("I read Jeff Dean's papers on MapReduce before building my own job queue")
• ✅ Specific Google open source projects you've contributed to or studied (gVisor, Bazel, gRPC, etc.)

By Month 9 you should have at least one OSS contribution to a Google project on your GitHub. Even tiny (typo fix counts).

Practice schedule

• Months 7-8: Write all 8 stories. Record yourself telling each one. Get times under 90s.
• Month 9: Practice on Pramp / interviewing.io. Iterate.
• Month 10+: Refine based on actual interview feedback.

Don't lie

• Don't invent stories, scale of impact, or team sizes.
• Don't claim "I" when it was "we" — interviewers can smell it.
• "We worked on this, and my specific contribution was X" is the right framing for team work.
• For solo projects, "I" is honest.