×
Register Here to Apply for Jobs or Post Jobs. X

Release Manager

Job in Chandler, Maricopa County, Arizona, 85249, USA
Listing for: StrongMind, Inc.
Full Time position
Listed on 2025-12-23
Job specializations:
  • IT/Tech
    IT Project Manager, IT Support, Systems Analyst, Technical Support
Salary/Wage Range or Industry Benchmark: 80000 - 110000 USD Yearly USD 80000.00 110000.00 YEAR
Job Description & How to Apply Below

About Strong Mind

Strong Mind builds digital learning experiences for K–12 online schools and homeschool families. We’re turning Strong Mind Core (SMC) into an online school operating system – a product/platform hybrid that powers students, parents, and teachers across multiple experiences.

About the role

We’re hiring a Release Manager to own end-to-end coordination of software releases across our K–12 customer base. You’ll ensure schools, districts, partners, internal support, and educators are aligned on what’s changing, when it’s changing, and how to adopt it—without disrupting instruction.

This role blends release operations, stakeholder coordination, customer enablement, and communication, with hands‑on ownership of feature‑flagged rollouts and strong execution using Jira.

Release planning and execution
  • Own the release calendar and coordinate release readiness across Product, Engineering, QA, Support, Customer Success, and Partnerships
  • Run release rituals (release planning, go/no‑go, launch reviews, post‑release retrospectives)
  • Use Jira to track release scope, dependencies, risks, and readiness status across teams
  • Coordinate staged deployments aligned to K–12 schedules (time zones, assessment windows, back‑to‑school periods)
School, district, and partner coordination
  • Communicate release timelines, scope, and rollout plans to schools/districts and partners
  • Ensure stakeholders are prepared and know what to expect before changes land
Feature flags and controlled rollouts
  • Manage feature flag configuration by school/district/client (on/off, phased cohorts, pilots)
  • Maintain an auditable record of feature availability per customer and keep Support/CS aligned on what’s live where
  • Partner with Engineering Managers to support safe launches, canaries, gradual ramps, and rapid rollback when needed through feature flagging so that you can act independently
Release communications
  • Write clear, educator‑friendly release notes (impact, benefits, who is affected, required actions)
  • Produce launch comms (emails, FAQs, partner notices, release notes) in coordination with Product/CS/Support
  • Maintain a consistent and discoverable release notes/changelog process
Training and enablement
  • Create and/or coordinate training materials (short videos, walkthroughs, guides) for teachers and admins
  • Deliver webinars or live demos as needed and package recordings for on‑demand access
  • Ensure Support and Customer Success readiness (briefings, internal playbooks, known issues, escalation paths)
Quality, risk, and disruption management
  • Coordinate release readiness checks, including backward compatibility expectations and operational risk review
  • Monitor early rollout signals (tickets, incidents, adoption, feedback) and coordinate response
  • Drive process improvements based on post‑release learnings and stakeholder feedback
Success metrics (how performance is measured) Enablement and communication effectiveness
  • Release note timeliness: release notes published by (or before) release time for 100% of releases
  • Internal readiness SLA:
    Support/CS trained and “ready” by a defined lead time (e.g., 3–5 business days pre‑release)
  • Training coverage: % of major releases with companion materials (video + FAQ/guide) and stakeholder comms
Adoption and rollout control
  • Feature adoption rate: usage of launched features by target segments within X weeks (teachers/admins)
  • Pilot‑to‑general‑availability conversion: % of pilots that progress to broader rollout on schedule
  • Feature flag accuracy: % of customers with correct flag state vs. plan (auditable, no surprises)
Process maturity
  • Release cycle time: time from “code complete” to “fully rolled out” (measured and improving where appropriate)
  • Retrospective completion rate: % of meaningful releases with documented post‑release learnings and action items closed
  • Stakeholder satisfaction: periodic CS/Support and key district stakeholder feedback on release clarity and preparedness
Requirements
  • 4–8+ years of experience in release management, technical program management, product operations, or similar roles in a SaaS environment
  • Strong cross‑functional management and coordination skills; able to run release processes end‑to‑end
  • Knowledge of…
To View & Apply for jobs on this site that accept applications from your location or country, tap the button below to make a Search.
(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).
 
 
 
Search for further Jobs Here:
(Try combinations for better Results! Or enter less keywords for broader Results)
Location
Increase/decrease your Search Radius (miles)

Job Posting Language
Employment Category
Education (minimum level)
Filters
Education Level
Experience Level (years)
Posted in last:
Salary