Answer behavioral questions on projects and feedback

## Core approach: structure + specificity Use **STAR** (Situation, Task, Action, Result) plus a brief **Reflection** (what you learned, what you’d do differently). Expect interviewers to probe on: - your exact role and scope - tradeoffs and decision criteria - how you handled conflict/ambiguity - measurable outcomes A good template: 1. **S/T (20–30 sec):** context, constraints, what “good” meant. 2. **A (60–90 sec):** 2–4 concrete actions you personally drove. 3. **R (20–30 sec):** metrics/impact + what changed. 4. **Reflection (10–20 sec):** learning, how you’d scale it. ## 1) “Project you’re proud of” ### What to include - A clear goal and why it mattered. - Technical depth + collaboration. - A measurable outcome (latency, cost, revenue, reliability, adoption). ### Common follow-ups - “What was the hardest part?” - “What would you do differently?” - “How did you measure success?” ## 2) “Ambiguous project” ### What interviewers want Evidence you can create clarity: - identify stakeholders and success metrics - reduce ambiguity via prototypes, experiments, and written alignment ### Strong storyline beats - Enumerate unknowns → propose assumptions. - Drive a doc: problem statement, non-goals, options, decision. - Run a small experiment to de-risk. ### Pitfalls - Saying “requirements were unclear so we waited.” ## 3) “Project changed midway” ### What to demonstrate - Adaptability without thrash. - Change management: re-plan, re-scope, communicate. ### Concrete actions to mention - Re-baseline milestones; explicitly drop/park low-value scope. - Re-evaluate risks and dependencies. - Communicate impact (timeline, quality, resourcing) early. ## 4) “Constructive feedback you received” ### What makes it credible - Pick feedback that was real (not a humblebrag). - Show behavior change and proof it worked. Example arc: - Feedback: “Your design docs were too late / too long / not aligned.” - Change: earlier doc, decision log, more stakeholder pre-reads. - Result: faster approvals, fewer reversals. ## 5) “Constructive feedback you gave” ### What to emphasize - You were respectful, specific, and aimed at improvement. - You verified impact after. Use **SBI** (Situation–Behavior–Impact): - Situation: when/where. - Behavior: observable actions. - Impact: consequence. - Next: specific alternative + offer help. Avoid: - attacking character (“you’re careless”) - public shaming ## 6) “Managing others” (direct or indirect leadership) If you haven’t had formal reports, use examples of **tech lead / mentorship / incident leadership**. Include: - goal setting and delegation - leveling expectations (what “done” means) - unblock mechanisms (pairing, office hours, docs) - handling performance issues (early signals, coaching plan) - giving credit and building psychological safety ## Final preparation checklist - Prepare 5–6 stories that can be re-used across prompts. - For each story, write down: - your role, constraints, 2–3 key decisions - 1–2 metrics - one mistake and what you learned - Practice concise delivery (2 minutes), then be ready for deep dives.