Lead Software Engineer

Role Overview

You will serve as the primary facilitator for core Scrum events including Sprint Planning, Daily Scrums, Reviews, and Retrospectives to ensure your team consistently delivers committed outcomes. You'll coach teams on Agile/Scrum fundamentals, reinforce working agreements (Definition of Ready/Done), and partner with Product Owners to refine backlogs and clarify acceptance criteria.

Key Responsibilities

• Eliminate or escalate impediments promptly, guiding the team through blockers, risks, and dependencies in collaboration with senior leaders.
• Leverage Jira/Azure Boards to maintain accurate boards, sprint metrics (velocity/throughput), and transparency logs.
• Drive cross-functional collaboration across engineering, product, and partners to enhance flow, quality, and delivery predictability.
• Spearhead continuous improvement by helping teams identify, prioritize, and track actions from retrospectives.
• Engage in PI planning and SAFe ceremonies where applicable to manage commitments and dependencies effectively.

Required Qualifications

• Bachelor's degree in Computer Science or related field (or equivalent experience).
• 2+ years as a Scrum Master supporting technology delivery teams, with familiarity of one-on-one agile coaching skills.
• Holds required certifications such as Certified ScrumMaster (CSM), Professional Scrum Master I/II (PSM-I/II), or SAFe Agilist certification from recognized bodies like Scrum.org or Scaled Agile Inc. Experience supporting multiple sprint cycles is essential.

Technical Skills

• Proficiency with Jira and/or Azure Boards for backlog management, reporting, and process visualization.
• Familiarity with Confluence for documenting team agreements, decisions, and artifacts.
• Solid understanding of SDLCs, release environments, and how Agile teams plan execution.

Soft Skills

• Demonstrated ability to address conflict constructively while escalating appropriately when necessary.
• Strong analytical skills for tracking dependencies, risks, and impediments across partner functions.