Collaboration

Collaboration signals include specific code review, clear technical writing, calm incident communication, and documentation that preserves decisions for future readers. Interviewers look for behaviors that make teams faster next quarter—not heroics during crises alone.

Subtopics: code review, technical communication, incident communication, documentation.

On interviews: describe a review comment you would leave on a risky PR; outline an incident update template; explain what belongs in an ADR versus a runbook.

Common pitfalls: vague "consider refactoring" comments; silent incident channels; docs that only describe happy paths.

The trade-off is time spent on communication artifacts versus tribal knowledge and repeated mistakes.

Checklist:

• Tie review feedback to correctness, tests, or user impact.
• Incident updates: impact, mitigation, owner, next update.
• Document decisions, constraints, and failure modes.
• Write for the reader who joins in six months.