SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
eVisit is seeking a Release Manager to own the mechanics of moving code from merge to production across all delivery teams. This role serves as air traffic control for each release: you know what is in it, coordinate contributing teams, own technical and business go/no-go decisions, and drive releases from cut to production. You also own environments, the deployment pipeline, and change-control records that make releases safe and auditable.
This is not a runbook-execution seat. You are expected to understand why the release process works, handle non-standard releases on their merits, and continuously improve the process.
Key Responsibilities:
- Execute standard and limited (audience-scoped) releases, including configuring and verifying audience scoping. Execute approved hotfixes: cut the branch, ship it, close it out. Define rollback paths per release type and make the call when deployments fail technically.
- Own technical and business go/no-go on every grouped release, including Release Readiness and Milestone Reviews. Surface technical coupling and deployment-ordering constraints. Handle non-standard releases such as running migrations separately, staging two-phase deploys, or sequencing schema changes ahead of dependent code. Produce release manifests for every release.
- Enforce branching model across repositories: branch creation, merge and squash discipline, cherry-picks into release branches, release branch cut and close, tag and version discipline. Gate what enters a release branch after cut.
- Own known-state, availability, and scheduling of Devtest, Acceptance, Beta, and Production environments, including data refresh and configuration parity.
- Own build-promotion and deployment pipeline end to end, drive out manual steps, and verify each deployment landed cleanly.
- Keep deploy-pending and validation statuses accurate. Report release frequency, cycle time from code-complete to production, failed-deployment rate, rollback rate, hotfix rate, and hotfix-to-scheduled-release ratio. Run retrospectives on failed or rolled-back releases. Own release runbooks and documentation.
- Produce and retain change-control records for every production push: what changed, who approved it, what validation passed, when it went out, and rollback path. Serve as system of record for release history in security, compliance, and customer audits.
- Derive cut dates and code-freeze windows from the Technical Delivery Manager's release calendar, communicate them, and enforce them at the branch. Communicate release details and schedules to business, including Sales, CS, and leadership. Notify teams and stakeholders of deployment start, completion, and failure in real time.
You are process-first and write things down. You automate repeated manual steps rather than executing them well twice. You can tell a team it missed the cut with no authority over those people and hold that line under pressure. When your own release fails, you run a blameless post-mortem.
Requirements (Must-Haves):
- U.S. citizenship and full-time U.S. residency, driven by contractual obligations with customers.
- Availability for off-hours release work. Releases commonly run outside business hours; this role must be reliably present for most of them on a sustainable schedule.
- Strong Git competency: branching strategies, merges and squashes, cherry-picking, tagging, and managing Git workflows that underpin release processes.
- Strong technical fluency. Not a software engineer or DBA, but a working mental model of CI/CD pipelines, containers and images, build artifacts, frontend vs. backend systems, deployment architecture, and MySQL concepts such as migrations, indexes, and the impact of database changes.
- Proven release management experience in a SaaS environment, including managing multiple releases concurrently across cross-functional teams.
- Excellent project and process management: tracking scope, chasing dependencies, enforcing process at the gate, and designing process where none exists.
- Strong communication and documentation skills, working closely with Engineering, QA, Product, and CS.
- Bachelor's degree in Computer Science, Information Systems, or a related field, or equivalent practical experience.
Strongly Preferred Qualifications:
- Prior software engineering, engineering management, Agile/Scrum/Ops, or database experience.
- AWS familiarity.
- Regulated-industry release experience (HIPAA, SOC 2, FedRAMP change control).
- Zero-downtime deployment and database migration experience.
- Feature-flag or progressive-delivery experience, directly relevant to Limited Releases.
- Scripting and automation experience, plus familiarity with defect tracking and configuration management tools.
