Answer common internship behavioral questions

### What a strong answer looks like (structure + evaluation criteria) Interviewers typically score you on: **clarity**, **ownership**, **judgment**, **bias for action**, **customer/impact focus**, and **reflection**. Use a consistent structure so your story is easy to follow: - **STAR**: Situation, Task, Action, Result - Add **R (Reflection)** at the end: what you learned / what you’d improve Aim for **2–3 minutes per story**, leaving room for follow-ups. --- ## 1) “Why this company?” ### What to include - **1–2 specific reasons** tied to the company’s products/tech/culture (not generic prestige). - **Role fit**: why your skills match what the team likely does. - **Learning goal**: what you want to gain during the internship. ### Good outline - **Reason #1 (product/mission)**: pick one domain you genuinely care about. - **Reason #2 (engineering culture)**: e.g., ownership, high standards, large-scale systems. - **Proof of intent**: reference something you built/studied that connects. ### Common pitfalls - Overly generic: “big company, good for growth.” - No linkage between your background and what you’ll do. --- ## 2) “Why this internship program / role?” ### What to include - **What you want to work on** (backend, ML, data, infra, etc.). - **Constraints you enjoy**: scale, reliability, latency, cost, experimentation. - **How you’ll contribute quickly**: languages, projects, collaboration style. ### Example content (template) - “I’m looking for an internship where I can own a scoped feature end-to-end, ship, and learn production practices (testing, monitoring, on-call mindset). My recent project doing X maps well because I had to do Y.” --- ## 3) “Quick decision” story ### What interviewers want - Can you decide with **incomplete info**? - Did you manage **risk** and communicate? - Did you validate quickly and adjust? ### Recommended STAR+R checklist - **Situation**: time pressure + why it mattered. - **Task**: what decision you owned. - **Actions**: - What info you gathered in minutes (logs, metrics, quick test, ask SME) - Your decision rule (e.g., minimize user impact; reversible vs irreversible) - Communication (who you notified; what you documented) - **Result**: measurable outcome (time saved, outage avoided, grade improved, etc.). - **Reflection**: what you’d change next time (runbook, pre-checks, automation). ### Strong trade-off framing - **Reversible decisions**: decide fast, iterate. - **Irreversible decisions**: escalate, gather more signal. --- ## 4) Deadline (DDL) story ### What interviewers want - Can you **plan**, **prioritize**, and **negotiate scope**? - Do you surface risks early? - Can you deliver an MVP and iterate? ### STAR+R checklist - **Situation**: deadline, dependencies, constraints. - **Task**: what “done” meant. - **Actions**: - Break down tasks; identify critical path - Prioritize: must-have vs nice-to-have - Manage stakeholders: communicate early, set expectations - Mitigate risk: parallelize work, create buffers, reduce scope - Quality: testing strategy under time pressure - **Result**: shipped on time / partial delivery with agreement / learned metrics. - **Reflection**: earlier risk flagging, better estimation, improved tooling. --- ## Follow-ups: how to handle them Common follow-ups include: - “What was your exact role vs the team’s role?” - “What data did you use to decide?” - “What would you do differently?” - “How did you handle conflict or pushback?” Best practice: be precise, quantify impact, and admit trade-offs. --- ## How to prepare quickly 1. Prepare **4 stories** you can reuse: - Quick decision - Deadline / prioritization - Conflict / disagreement - Failure / learning 2. For each story, write: - 1 sentence Situation - 1 sentence Task - 3 bullet Actions - 1–2 measurable Results - 1 Reflection 3. Practice aloud to fit **2–3 minutes**.