## Prompt Tell me about a time you helped a colleague resolve a difficult problem. Explain how you learned what they needed, how you contributed without taking away ownership, and what the team gained from the interaction. ### Constraints & Assumptions - Use a specific incident with a meaningful obstacle. - Distinguish coaching, collaboration, and doing the work for someone. - Credit the colleague's contribution and explain any lasting improvement. - Do not frame help as rescuing an incapable teammate. ### Clarifying Questions to Ask - Can the colleague be outside the candidate's immediate team? - Should the example emphasize technical debugging or broader support? - Is the outcome expected to include knowledge sharing? ```hint Diagnose before prescribing Ask the colleague to show the failure, their current model, and what they have already ruled out before offering a solution. ``` ### What a Strong Answer Covers - The colleague's goal and obstacle are described respectfully. - The candidate listens, narrows the problem, and chooses a proportionate way to help. - Ownership stays clear; both people's contributions are visible. - The immediate problem is solved or materially advanced. - Knowledge, tooling, or documentation reduces the chance that the same blocker recurs. - The answer reflects on boundaries and avoids creating dependency. ### Follow-up Questions 1. How did you know your help was wanted? 2. What did the colleague discover that you had missed? 3. What would you do if helping threatened your own commitment? 4. How did you make the solution useful to others?