I jumped straight to 'have a direct conversation' which felt right but also kind of obvious.
Start by assuming positive intent and seek to understand the root cause through a private, empathetic conversation. Then collaboratively address the issue by clarifying expectations, offering support, and if necessary, escalating to ensure quality standards are met.
Pro tip: Frame the conversation around shared goals and team impact rather than personal blame, and document the discussion to protect both the developer and the team.
Gather specific examples of untested code and consider possible reasons such as lack of time, unclear expectations, or skill gaps. Approach the developer privately to discuss.
Use a non-confrontational tone to express concern, ask open-ended questions, and listen actively to their perspective. Focus on the impact on the team and product.
Work together to identify solutions, such as pairing, training, adjusting deadlines, or implementing automated testing. Set clear expectations and offer support.
Schedule check-ins to review progress and provide feedback. Recognize improvements and address any ongoing issues promptly.
If the behavior persists, involve a manager or HR according to company policy, emphasizing the importance of quality and team accountability.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.