A strong answer should show judgment, professionalism, and risk management rather than blame. **What the interviewer is evaluating** - Whether you stay objective under uncertainty - How you handle interpersonal tension without becoming political - Whether you protect delivery and quality while preserving trust - Whether you escalate appropriately and only when needed **How to structure the answer** Use a STAR-style response: 1. **Situation** Briefly describe a real work scenario where trust was low. Good examples: - A teammate repeatedly missed commitments - You found inconsistencies in status updates or technical claims - Critical code or data changes were made without review 2. **Task** Explain your responsibility. For example: - You owned a service deadline - You were responsible for production stability - You needed to coordinate across teams to deliver a launch 3. **Action** This is the most important part. Emphasize that you: - Focused on observable behavior, not personal attacks - Verified facts before concluding there was a trust issue - Increased transparency through checkpoints, written updates, design reviews, or test plans - Spoke directly and respectfully with the colleague - Brought in a manager only if the risk or pattern justified it - Protected the project with concrete safeguards such as code review, monitoring, rollback plans, or clearer ownership 4. **Result** End with a constructive outcome: - Delivery risk was reduced - Communication improved - Responsibilities became clearer - You learned not to assume bad intent too quickly **What makes an answer strong** - You distinguish between "I disliked their style" and "there was a real reliability risk" - You show maturity: trust problems are handled with process and communication - You do not gossip or attack the person - You describe a balanced outcome, not a dramatic conflict story **Good themes to highlight** - "I trusted the person less in that situation, so I increased verification mechanisms." - "I addressed the issue directly and respectfully." - "I focused on protecting the team and the customer, not proving someone wrong." - "I learned to create transparency earlier." **Common mistakes to avoid** - Saying you simply stopped trusting them and worked around them - Making the answer sound emotional or personal - Presenting yourself as always right and the other person as incompetent - Escalating too quickly without first clarifying expectations **Example answer outline** "On one project, a teammate owned an integration that was repeatedly reported as on track, but the delivered work did not match the agreed interface and testing had not been completed. I was responsible for the downstream service and saw schedule risk. Instead of assuming bad intent, I set up a direct working session to compare the implementation against the spec, and I proposed short written checkpoints and a shared test checklist. That made the gaps visible early. When the pattern continued, I involved our manager to clarify ownership and deadlines. We ultimately delivered with a smaller scope, avoided a production issue, and improved the team's review process. The main lesson for me was to respond to low trust with transparency and verification, not accusation."