Job Description & Details
This contract role drops you right into the middle of business-critical initiatives where your primary job is to clear roadblocks and keep cross-functional teams moving forward. You won't just be pushing Jira cards; you'll be actively coaching engineers, stakeholders, and product owners on how to actually deliver software without burning out.
What You'll Actually Be Doing
Your days will be spent facilitating the usual agile ceremonies—planning, PI planning, reviews, and retrospectives—while acting as the ultimate shock absorber between the development team and business stakeholders. You'll spend a lot of time helping Product Owners groom backlogs, writing crisp acceptance criteria, and managing risks before they blow up your sprint timeline. When things stall, you step in to remove impediments, keeping everyone accountable for their PI and sprint commitments.
The Core Tech Stack
While you won't be writing production code, you need a deep, practical mastery of Agile frameworks, Scrum, and Kanban methodologies. Fluency in backlog management tools like Jira or Azure DevOps is non-negotiable, along with a strong grasp of agile metrics like velocity, cycle time, and throughput. You need to know how to read these numbers to spot team bottlenecks before management asks for a status report.
Interview Expectations
Expect the hiring manager to ask you to describe a time when a sprint completely derailed halfway through and how you handled the stakeholders breathing down your neck. They want to see your conflict resolution skills and how you protect your team's velocity under pressure. Another favorite line of questioning will test your ability to coach a stubborn Product Owner who refuses to groom their backlog properly, so be ready with a real-world example of how you influenced product leadership without having direct authority.
Application Advice
To get past the ATS and grab the recruiter's attention, make sure your resume explicitly highlights your experience with Program Increment (PI) planning and cross-functional team leadership. Don't just list 'Scrum Master' as a title; use bullet points that showcase hard metrics, such as how you improved sprint predictability or reduced cycle times. Mirror the terminology from the job description—specifically mentioning risk management, impediment removal, and agile metrics tracking.