Answer common behavioral questions for new grad

## Overall approach - Use **STAR** (Situation, Task, Action, Result) for experience-based questions, and **structured bullet points** for opinion/strategy questions. - Keep an “executive summary” first (1–2 sentences), then details. - Quantify impact when possible (latency %, users, revenue, time saved, etc.). - Prepare **2–3 core stories** you can reuse (conflict, leadership without authority, failure/learning, project ownership). --- ## 1) Self-introduction (60–90 seconds) **Goal:** Quickly answer “Who are you?” + “What’s your strength?” + “Why are you relevant to this role?” **Template** 1. Present: school/role + focus area 2. 1–2 strongest technical experiences (intern/project) with impact 3. Your engineering strengths (e.g., systems, ML, frontend, collaboration) 4. Why you’re excited about this role/team **Example skeleton** - “I’m a CS new grad focused on backend and distributed systems.” - “Recently I built X, improving Y by Z% / serving N requests/day.” - “I enjoy turning ambiguous problems into measurable outcomes, and I’m excited about Google’s scale and product impact.” Pitfalls: too long, full resume walk-through, no impact. --- ## 2) Why Google? **Goal:** Show intentionality + fit. **Strong structure (3 parts)** 1. **Mission/product alignment:** which products/areas excite you (Search/YouTube/Cloud/Android/etc.). 2. **Scale + engineering culture:** reliability, performance, tooling, code review culture, research-to-product. 3. **Your specific match:** connect your past projects to what you want to do next. **Good signals** - Mentions concrete themes: reliability at scale, user trust/privacy, latency, accessibility, internationalization. - Avoids generic lines (“good brand, smart people”) without specifics. --- ## 3) Product thinking: “Build a product used by all users—what would you do?” This is an **ambiguity + strategy** question. Drive it with a framework. ### Step-by-step framework 1. **Clarify the goal** - “All users” means what? (global reach? all existing users? all demographics?) - Success metric: adoption, DAU/MAU, retention, NPS, revenue, accessibility compliance. 2. **Identify user segments & core jobs-to-be-done** - Segment by needs (new vs power users), region, device/network constraints, accessibility. 3. **Define MVP and wedge** - Start with a narrow, high-value use case that can expand. 4. **Distribution strategy** - Default placement, partnerships, pre-installs, SEO, integrations, referral loops. 5. **Trust, safety, and privacy** - Abuse prevention, data minimization, transparency. 6. **Scale & reliability** - Global latency targets, offline/low bandwidth mode, graceful degradation. 7. **Measure and iterate** - A/B tests, cohort retention, funnel metrics. ### What the interviewer is testing - Can you ask clarifying questions? - Do you think in **metrics** and **tradeoffs**? - Can you balance **user value + safety + feasibility**? --- ## 4) Short-term / long-term goals **Short-term (1–2 years):** ramp-up, become productive, own a component, deepen in an area. **Long-term (3–5+ years):** technical leadership, staff-level trajectory, product ownership, or domain expertise. **Template** - Short-term: “Become strong in X stack, deliver Y impact, learn Z best practices.” - Long-term: “Grow into someone who leads projects end-to-end and mentors others / becomes a domain expert in …” Pitfall: overly specific to a role you can’t guarantee (“I will be PM in 1 year”). --- ## 5) Heavy workload: what would you do? Show prioritization, communication, and execution. **Best-practice answer structure** 1. **List and clarify tasks** (scope, deadlines, dependencies) 2. **Prioritize by impact vs urgency** (and risk) 3. **Negotiate scope/timeline** with stakeholders early 4. **Break down work** into milestones; unblock dependencies 5. **Ask for help / delegate** appropriately 6. **Communicate status** proactively (weekly updates, risks) 7. **Protect quality** (tests, code review) and avoid burnout **Signals interviewers like** - You don’t silently grind; you align expectations. - You can say “no” or “not now” with data. --- ## 6) Weakness Pick a real weakness that is **not fatal** for the role, show **self-awareness** and **improvement loop**. **Template** - Weakness: specific behavior - Context: when it shows up - Actions: what you changed (tools/habits) - Evidence: measurable improvement **Examples (safer options)** - “I used to over-polish solutions; now I timebox and align on ‘definition of done’.” - “I was hesitant to ask for help; now I escalate with a clear summary after 30–60 minutes blocked.” Avoid: “I’m a perfectionist” with no substance, or core weaknesses like “I miss deadlines frequently.” --- ## Final prep checklist - Prepare 2–3 STAR stories with metrics. - For each story: conflict/tradeoff, what *you* did, result, what you learned. - Practice concise delivery: 60–120 seconds per answer + 30 seconds buffer for follow-ups.