How do you handle credit, leadership, and feedback?

## What interviewers are really assessing Across these prompts, they typically score you on: - **Collaboration & integrity:** Do you protect the team outcome while handling fairness professionally? - **Influence without authority:** Can you change behavior/process without formal power? - **Leadership maturity:** Do you define leadership as enabling others, clarity, and accountability? - **Self-awareness & growth:** Can you receive/give feedback well and learn? - **Communication:** Clear, concise, non-blaming storytelling. Use a consistent structure: **STAR** plus a brief **reflection** (what you learned, what you’d do differently). --- ## 1) Teammate takes all the credit: strong answer structure ### Step-by-step approach 1. **Assume positive intent first** (could be misunderstanding, different communication style). 2. **Document facts**: keep a simple record of contributions (PRs, design docs, meeting notes). 3. **Address privately, quickly, and directly**: - Describe observable behavior (not motive). - Explain impact on team trust/visibility. - Propose a fix (shared updates, explicit attribution). 4. **Create system-level clarity**: - Team status updates that list contributors. - Shared artifacts (RFCs) with authors. - Rotate presenters. 5. **Escalate only if needed** (pattern continues): involve manager with evidence and a solution-oriented framing. ### What to say (example phrasing) - “In our last two updates, my work on X wasn’t mentioned. I might be misunderstanding—can we align on how we represent contributions? I’d like us to present outcomes as a team and call out owners explicitly.” ### Pitfalls to avoid - Public call-outs or sarcasm. - Making it personal (“you’re stealing credit”). - Over-escalating before attempting a direct conversation. --- ## 2) Working in an unstructured team + making it structured ### How to describe your experience (what to include) - Symptoms: unclear priorities, constant context switching, ambiguous ownership, reactive deadlines. - Your role: what you owned and what you influenced. - Actions: how you introduced lightweight structure. - Results: measurable outcomes (cycle time, fewer incidents, clearer roadmap). ### Practical ways to add structure (lightweight, scalable) Pick 2–4 tactics appropriate to the situation: 1. **Clarify goals and success metrics** - Define a quarterly objective and a small set of measurable key results. 2. **Define ownership** - Use a simple **DRI** (Directly Responsible Individual) per project. - RACI only if the org is large; otherwise keep it simple. 3. **Establish a decision process** - Write short RFCs for non-trivial changes (1–2 pages). - Time-box decisions; record rationale. 4. **Create an execution cadence** - Weekly planning + mid-week checkpoint. - Single source of truth for tasks (board/backlog). 5. **Reduce coordination load** - Clear on-call/triage policy. - Templates for updates and incident reviews. ### Key tradeoff to mention Structure should **reduce ambiguity and rework**, not add meetings. State how you kept it lean (e.g., “one weekly planning meeting, everything else async”). --- ## 3) What makes a good leader/mentor + example ### Strong leadership traits (pick 3–5 and define them) - **Clarity:** sets direction, defines success, prioritizes. - **Trust & empowerment:** delegates ownership, avoids micromanagement. - **Coaching:** asks questions, provides context, grows people. - **Accountability:** holds a high bar while being supportive. - **Psychological safety:** encourages dissent, blameless learning. - **Systems thinking:** improves processes, not just one-off fixes. ### How to give the example Use STAR and emphasize behaviors: - “They set a clear goal, gave me autonomy, reviewed my design, and after a production issue they ran a blameless retrospective and improved the runbook.” ### Pitfall Avoid hero-worship or vague adjectives (“great communicator”). Always attach **observable behaviors**. --- ## 4) Career plan: a credible, non-overcommitted answer ### A safe and strong structure 1. **Near term (1–2 years):** deepen craft in current role, deliver impact, expand scope. 2. **Mid term (3–5 years):** lead larger initiatives / become staff-level IC or people manager (choose one, or explain what you’re exploring). 3. **Why this company/team:** connect to product domain, technical challenges, mentorship, scale. 4. **Learning plan:** concrete skills (system design, mentoring, domain expertise). ### Pitfalls - Overly rigid plans (“I will be a director in 2 years”). - Making it all about title rather than impact. --- ## 5) Good vs bad feedback + examples ### Define “good feedback” Good feedback is: - **Specific** (behavior + situation) rather than personality. - **Actionable** (clear next steps). - **Timely** (close to the event). - **Bi-directional** (invites dialogue). - **Aligned to expectations** (shared bar/goal). A common framework: **SBI** (Situation–Behavior–Impact) + request. ### Define “bad feedback” Bad feedback is: - Vague (“be more proactive”), delayed, or delivered publicly. - Judgmental labels (“you’re careless”). - Not paired with examples or support. ### Example templates - **Giving feedback:** - Situation: “In yesterday’s design review…” - Behavior: “you interrupted twice while others were explaining…” - Impact: “it reduced participation and we missed a key edge case…” - Request: “can we let speakers finish and capture questions in notes?” - **Receiving feedback:** - Thank, clarify with questions, restate, propose an action plan, follow up with progress. ### Pitfall Do not present feedback as “I told them what they did wrong.” Emphasize coaching and shared goals. --- ## How to practice (quick checklist) - Prepare **2–3 stories** that can flex across prompts (conflict, ambiguity, leadership, failure/learning). - Include **metrics** where possible (time saved, incidents reduced, delivery improved). - End with a **reflection**: what you learned and how you changed your behavior.