Mohajerian interview questions

As I walk into the office building, I take a deep breath to calm my nerves. Today's my Scrum Master interview with a tech company I've been eager to join. I've prepared extensively, but interviews always bring a mix of excitement and anxiety. The receptionist greets me warmly and offers water while I wait. I use these few minutes to mentally review the Agile principles and Scrum ceremonies I've practiced facilitating over the years. Soon, a woman introduces herself as Sarah, the Agile Coach, and leads me to a conference room where two others wait: James, the Engineering Manager, and Priya, a Product Owner. "Tell us about your Agile journey," Sarah begins after introductions. I share my story of transitioning from a developer role to Scrum Master, highlighting how I've helped teams improve their velocity and collaboration. I emphasize my servant-leadership approach and my belief that a Scrum Master's success lies in making the team successful. The questions become more specific: "How would you handle a team member who consistently misses sprint commitments?" "Tell us about a time you helped remove impediments for your team." "How do you facilitate productive retrospectives when the team seems disengaged?" "What metrics do you find most valuable for measuring team health?" James presents a scenario: "Our team struggles with constant scope changes mid-sprint. How would you address this?" I explain my approach to protecting the team while still maintaining flexibility: "I would work with the Product Owner to ensure the backlog is well-refined, implement a buffer for emergent work, and facilitate a discussion about the impact of mid-sprint changes on team morale and predictability." Priya asks me to role-play facilitating a Sprint Planning session with a challenging team member. I demonstrate how I would ensure everyone's voice is heard while keeping the meeting on track. As we wrap up, they ask if I have questions. I inquire about their Agile maturity, biggest challenges, and team dynamics. Their answers give me valuable insights into what I might be walking into. Leaving the building, I feel energized rather than drained. The interview wasn't just them assessing me—it was also my opportunity to evaluate if this is an environment where I could help a team thrive. Whether I get the offer or not, I know I represented my skills and passion for Agile principles authentically.