Change and Configuration Coordinator

Job Description

Job Description

The Change & Coordination Coordinator will support Operations by coordinating and managing application releases across cloud, web, data, and client-server environments. This is a 6-month contract role intended as short-term support, with a target start date of November 15 and a hard end date of June 1, 2026.

• QA or purely Business Analyst profiles will not be considered

This position focuses on release and change coordination, ensuring deployment plans, dependencies, and stakeholder communication are effectively managed. The selected candidate should be able to ramp up within 1–2 weeks and immediately assist ongoing operational and project-based initiatives.

Key Focus Areas

• Coordinate release and change activities across assigned applications.
• Develop and maintain deployment plans, release calendars, and change documentation.
• Support release meetings and communicate progress, risks, and dependencies.
• Perform basic reporting and data analysis using Excel and SharePoint.
• Ensure releases align with established processes and governance.
• Collaborate closely with internal stakeholders to ensure smooth execution.

Skills and Tools Highlighted by the Manager

• Release Management / Coordination experience
• SAFe and Scrum methodologies
• JIRA and ServiceNow (core daily tools)
• SQL – basic data analysis capability (not development)
• Cloud Apps / Web Apps / Client-Server / Java Application Architecture understanding
• SharePoint and Excel for documentation and tracking
• Strong communication and collaboration skills — critical for stakeholder interaction

Requirements & Preferences

• Minimum 5 years of IT experience, preferably in Release or Change Management roles
• ITIL or SAFe certification is nice to have but not required
• Candidates should have a strong working knowledge of IT environments and cross-team coordination

• Location: Austin, TX preferred, Taylor, TX

– Local candidates: In-office Wednesdays and Thursdays
– Remote candidates: Considered only if no local fit; expected onsite 1–2 times per month