How do you deal with a team member who does not participate in ceremonies?
Assesses fundamental understanding of Agile & Scrum conventions, runtime behavior, and memory/performance considerations.
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
I start from curiosity, not accusation. Silence usually has a cause: they may feel the ceremonies are pointless, be overloaded, lack psychological safety, or simply prefer written communication.
I would speak to them privately and ask what would make the meetings useful for them. Often the answer reveals a team level problem rather than a personal one.
Then I address the cause. If the Daily Scrum feels like a status report, I refocus it on the Sprint Goal and make it a conversation among developers. If a few people dominate, I use structured formats or written input first. If they are overloaded, we look at workload with the Product Owner.
I also make participation expectations clear and give them a meaningful role, such as owning refinement for a feature.
Persistent disengagement after that is a performance conversation, but that is the last step, not the first.
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.