Collaboration & Conflict
How you work with other people when it gets hard: disagreements, friction, feedback, and persuasion. Interviewers probe this because most engineering failures are coordination failures, and they want evidence you can disagree productively without burning relationships.
on this pageshowhide
explore
- Technical Disagreement9 questions
- Disagreeing with a Colleague2 questions
- Disagreeing with Your Manager2 questions
- Being Wrong & Changing Your Mind3 questions
- Deadlocks & Escalation2 questions
- Difficult Teammates6 questions
- Working with a Difficult Person3 questions
- Credit, Blame & Trust3 questions
- Giving Feedback2 questions
- Giving Hard Feedback2 questions
- Code-Review Conflict8 questions
- Pushing Back as a Reviewer3 questions
- Handling Review Pushback as Author3 questions
- Style Wars & Team Standards2 questions
- Cross-Team & Stakeholder Friction8 questions
- Blocked by Another Team2 questions
- Difficult Stakeholders3 questions
- Remote & Async Friction3 questions
- AI & Data Scientistrole
- AI Engineerrole
- AI Red Teamingrole
- Android Developerrole
- BI Analystrole
- Backend Developerrole
- Blockchain Developerrole
- Cyber Security Expertrole
- Data Analystrole
- Data Engineerrole
- DevOps / SRE Engineerrole
- DevSecOps Engineerrole
- Frontend Developerrole
- Full Stack Developerrole
- Game Developerrole
- Java Backend Developerrole
- Java SDETrole
- Kotlin Backend Developerrole
- MLOps Engineerrole
- Machine Learning Engineerrole
- Network Engineerrole
- PostgreSQL DBArole
- QA Engineerrole
- Software Architectrole
- iOS Developerrole
questions
page 2 of 2Tell me about a time your feedback to a colleague did not land well.
basics
~20 sProbes self-awareness and persistence. Answer with feedback that was right in substance but wrong in delivery, an honest diagnosis of what you got wrong, a second attempt you actually made, and what you changed in your habits afterward.
Tell me about a time you convinced a business stakeholder to fund technical work they did not want.
basics
~10 sTests whether you can translate engineering risk into business currency. Answer with one piece of technical work, its cost stated in something the stakeholder already tracks, a sized ask, and what the investment returned.
Tell me about a time a post-incident review started looking for someone to blame.
basics
~20 sTests whether you can hold a review on mechanisms rather than people. Name the moment it turned personal, the reframe you said out loud, the system questions you asked instead, and the trust that showed up afterwards.
showing 31–33 of 33