> Markdown version of [/jobs/ext/3474218-release-manager](https://www.wearedevelopers.com/jobs/ext/3474218-release-manager). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Release Manager

- **Company:** Mitchell Martin
- **Location:** New York, NY, United States
- **Experience:** Experienced
- **Salary:** $112,112.0 - $160,160.0
- **Contract:** Permanent contract
- **Skills:** Microsoft Windows, Agile Methodology, Confluence, JIRA, Release Management, Servicenow
- **Published:** September 21, 2026
- **Apply:** https://www.dice.com/job-detail/6b649a9e-630b-4a55-aa8c-2226096606a0

## About the Role

Bachelor's degree or equivalent experience with at least four years in a related field.
Three years of experience in release management or technology delivery coordination.
Proven experience in managing software releases across multiple teams and systems.
Strong organizational and communication skills with the ability to manage competing priorities.
Experience working in Agile or modern software delivery environments.

Core Technologies
Jira | Confluence | ServiceNow | Microsoft 365

## Description

Join our team as a Release Manager in the bustling city of New York.
This contract position requires coordinating delivery milestones and ensuring production readiness for technology initiatives.
You'll work closely with engineering, QA, and business partners to manage releases, identify risks, and ensure smooth production transitions.
Experience in modern software delivery environments and proficiency in change management tools is essential., Develop and maintain integrated release plans, ensuring alignment of milestones and dependencies.
Coordinate cross-functional teams to meet release commitments and manage handoffs.
Track progress, identify blockers, and facilitate timely resolutions and escalations.
Lead release readiness checkpoints and coordinate go/no-go decisions.
Capture lessons learned and recommend improvements for release predictability and documentation quality.