Handle teamwork, prioritization, and feedback scenarios

## A strong way to answer: STAR + “your role” + “result” Use **STAR** (Situation, Task, Action, Result). For senior candidates, add: - **Scope/constraints:** time, people, reliability, cost. - **Your specific role:** what you personally owned vs. the team. - **Trade-offs:** what you chose not to do and why. - **Measurable outcomes:** latency, revenue, incidents, adoption, deadlines. A good structure per answer (60–120 seconds): 1. **Situation/Task (20%)**: one sentence each. 2. **Actions (60%)**: 3–5 concrete actions, with rationale. 3. **Result (20%)**: metrics + reflection (what you’d do differently). ## 1) Complex project What interviewers want: - Technical depth + project management + ambiguity handling. Cover: - Problem statement and success metrics. - Architecture/approach, key risks, and milestones. - Collaboration (PM, design, infra, data). - Outcome: impact + lessons learned. ## 2) Resolve conflicts between teammates What they want: - Emotional maturity, facilitation, and focus on outcomes. Playbook: - Align on shared goal (customer/business impact). - Separate “facts” from “opinions.” - Propose options with trade-offs; run a small experiment if possible. - If still stuck: escalate with context, not blame. Example actions to mention: - Set up a 1:1 to understand each side. - Write a short decision doc (options, pros/cons, recommendation). - Agree on decision owner and timeline. ## 3) Help other people What they want: - Mentorship and leverage. Strong examples: - Unblocked someone with debugging/system knowledge. - Wrote documentation or tooling that helped the team repeatedly. - Paired to teach a concept, then verified they could run independently. ## 4) More work than you can handle + 5) How to decide priority Combine these into one coherent framework: Prioritization rubric: - **Impact** (customer/revenue/risk reduction) - **Urgency** (deadlines, incidents) - **Effort** (engineering cost) - **Dependencies** (unblocks others) Concrete steps: 1. List tasks and estimate impact/effort. 2. Communicate early to stakeholders with options. 3. Negotiate scope (MVP vs. nice-to-have). 4. Protect focus time; delegate where appropriate. 5. Revisit priorities when new information arrives. Show that you: - Don’t silently drown. - Make trade-offs explicit. ## 6) Recently learned something What they want: - Growth mindset + ability to apply learning. Good answers include: - What prompted the learning (a gap, a failure, curiosity). - How you learned (project, course, RFCs, mentoring). - How you applied it (shipped change, improved reliability/perf, taught team). ## 7) Give feedback + reaction What they want: - Direct but kind communication. Use a framework: - **SBI**: Situation–Behavior–Impact - Or “Start/Stop/Continue.” Key points: - Give feedback privately and promptly. - Be specific about behavior, not personality. - Invite their perspective; align on next steps. - Follow up after a week or two. ## 8) Someone took credit for the whole team’s work What they want: - Professionalism, fairness, and protecting team trust. A strong approach: 1. Assume positive intent first (could be misunderstanding). 2. Address privately: "I noticed X. The team contributed A/B/C; can we clarify in the next update?" 3. Redirect credit publicly in a non-accusatory way: "Building on what Alex shared, Priya led Y and Chen solved Z." 4. If repeated/patterned: document examples and involve your manager with a focus on team health. ## Final tips - Prepare 6–8 core stories you can reuse across prompts (project, conflict, failure, leadership without authority, mentoring, prioritization). - Add at least one metric to each story. - End with reflection: what you learned and how you changed your behavior.