This is a remote position.

The Senior Scrum Master / Project Manager is the primary guiding authority for Agile ceremonies, structure, and delivery discipline across the engineering organization. This role sets and enforces the standard for how Agile is practiced organization-wide — directly coaching and overseeing a cohort of Scrum Masters across a broad portfolio of teams, while personally serving as the acting Scrum Master for a subset of teams to stay close to day-to-day delivery.

The role owns the organization's Agile Development Metrics & Quality Accountability Framework end-to-end, translating Jira and GitHub activity into trustworthy delivery and quality signals for engineering and business leadership. This role also serves as the primary Agile conduit between Product Management / Product Ownership and the engineering teams, ensuring scaled Agile practices connect roadmap intent to sprint execution cleanly and predictably.

Core Responsibilities

Agile Program Leadership & Scrum Master Coaching

•     Set and enforce the standard for Agile ceremonies and structure across 12 teams; directly coach and performance-support 6–7 Scrum Masters.

•     Maintain a consistent Agile operating model (definitions of ready/done, estimation, cadences, escalation paths) across all teams.

•     Resolve cross-team delivery impediments and run a Scrum Master community of practice.

Direct Scrum Mastery

•     Act as Scrum Master for 2 assigned teams — ceremonies, backlog hygiene, and impediment removal — to stay grounded in day-to-day delivery.

Agile Development Metrics & Quality Accountability Framework

•     Own, implement, and evolve a comprehensive metrics framework spanning sprint execution, code review discipline, and defect accountability — from first commit through production — using Jira and GitHub as the systems of record.

•     Implement and maintain core delivery metrics in Jira: velocity, sprint predictability, cycle time, lead time, throughput, WIP, scope creep, and carryover rate at team, sprint, and rolling-quarter cadence.

•     Implement code review rigor metrics from GitHub PR activity: change-requested rate, rework commits per PR, review cycles to approval, time in review, and senior reviewer comment density; partner with engineering leadership on branch protection rules and senior-reviewer group definitions.

•     Own the defect discovery-by-phase taxonomy on the Bug issue type in Jira (Unit/TDD, Code Review, Dev/Integration Testing, QA/Release Testing, Production/Escaped) and the resulting metrics: defect detection distribution, escape rate, production escape rate, phase containment effectiveness, defect density, and MTTD.

•     Maintain the escaped-defect attribution chain linking each bug to its originating story/task, the merged PR(s) that implemented it, and the author/reviewers of record — via Jira links and GitHub smart-commit/PR referencing.

•     Own the recurring per-release and quarterly Contractor/Team Accountability Rollup reporting cycle; review trend lines (improving, flat, worsening) with the relevant teams and leads.

•     Own the reporting and BI delivery mechanic — including administration of eazyBI (or equivalent BI layer) connected to Jira and GitHub — to produce recurring dashboards and reports without a separate data pipeline.

•     Refine the framework's guiding principles: metrics must be actionable, paired for balance (speed vs. quality), system-focused (with defect attribution as the narrow, explicitly scoped exception), trend-driven, diagnostic rather than target-driven, and passively instrumented from existing Jira/GitHub workflow artifacts.

Agile Conduit for Product Management

•     Serve as the primary Agile conduit between Product Managers, Product Owners, and the engineering organization, translating roadmap and portfolio intent into scaled Agile execution across the 12 teams.

•     Apply scaled Agile methodologies (e.g., SAFe, Scrum@Scale, or the organization's equivalent) to coordinate cross-team dependencies, program increment / release planning, and backlog alignment.

•     Facilitate program-level ceremonies (PI planning, scrum-of-scrums, cross-team dependency reviews) that connect Product Owner intent with delivery capacity and constraints.

•     Provide Product Management / Product Ownership with visibility into delivery health and quality signals from the framework to inform prioritization and roadmap tradeoffs.

Required Qualifications

•     Bachelor's degree in a related field, or equivalent experience.

•     5+ years of experience as a Scrum Master or Agile Project Manager in a professional software development environment, including experience coaching or leading other Scrum Masters.

•     Demonstrated experience running Agile ceremonies and delivery practices across multiple concurrent teams.

•     Working knowledge of scaled Agile methodologies (e.g., SAFe, Scrum@Scale, LeSS) and experience serving as a conduit between Product Management / Product Ownership and engineering teams.

•     Hands-on proficiency administering Jira for Agile delivery, including custom fields, workflows, and sprint/board configuration.

•     Working knowledge of GitHub pull request workflows, branch protection, and Jira–GitHub linkage (smart commits) sufficient to own a metrics framework built on that data.

•     Demonstrated ability to design, implement, and evolve delivery and quality metrics programs, and to translate them into reporting non-technical stakeholders can act on.

•     Familiarity with AI-assisted engineering tooling and workflows.