Job Title: Senior Release Train Engineer / Atlassian Administrator

Role Summary

The Release Train Engineer / Atlassian Administrator is a hands-on role that combines cross-team delivery support with Jira and Confluence administration. This person works directly with teams, Product Managers, Technical Leads, and delivery leads to plan work, manage dependencies, clear blockers, and keep things moving. They also handle Jira and Confluence administration and improvement so the tools match how teams actually work.

This role is part of day-to-day delivery, not a layer above it. It covers core Release Train Engineer responsibilities across teams, including planning support, keeping teams in sync, managing dependencies, raising risks when needed, and helping with release or milestone readiness. It also serves as the hands-on Atlassian administrator responsible for configuration, reporting support, data quality, cleanup, audits, and ongoing platform improvement.

The role helps teams turn priorities into work they can execute, stay aligned as delivery moves, and use Jira and Confluence as practical working tools.

Responsibilities:

Delivery Execution and Coordination

•          Work directly with teams on planning, execution, and follow-through.
•          Help turn priorities into clear work that teams can pick up and execute.
•          Help teams work through ambiguity, keep momentum, and adjust as priorities or conditions change.
•          Make sure planning decisions turn into clear actions, owners, and follow-up.
•          Stay close enough to the work to spot issues early and help move them toward resolution.

Cross-Team Planning and Release Train Support

•          Run or support cross-team syncs such as Scrum of Scrums, planning reviews, dependency reviews, and execution check-ins.
•          Support Program Increment, quarterly, release, or other multi-team planning cadences used by the organization.
•          Keep track of cross-team commitments, dependencies, milestone status, and delivery risks.
•          Follow up on planning decisions to make sure they turn into assigned work and action.
•          Help teams get ahead of unresolved dependencies, delivery risks, and gaps that could affect release or milestone readiness.
•          Support retrospectives, inspect-and-adapt sessions, and similar working sessions aimed at improving delivery.

Dependency, Risk, and Blocker Management

•          Track and help resolve cross-team dependencies.
•          Identify blockers, bottlenecks, overload, and process issues while work is underway.
•          Work with teams and leads to remove impediments quickly.
•          Raise risks or constraints when they need leadership attention or support beyond the team level.
•          Help address recurring delivery issues by identifying root causes and getting them worked to closure.

Jira and Confluence Administration

•          Serve as the primary hands-on administrator for Jira and Confluence in support of team delivery.
•          Configure and maintain workflows, issue types, screens, fields, schemes, permissions, boards, dashboards, filters, automations, and page structures.
•          Troubleshoot user issues related to workflows, access, permissions, reporting, dashboards, and usability.
•          Adjust configuration based on what teams are running into in day-to-day work.
•          Simplify workflows and structures where the tools are slowing teams down or causing confusion.

Reporting, Dashboards, and Delivery Insight

•          Build and maintain dashboards, filters, boards, saved views, and reports used by teams and leadership.
•          Make sure reporting helps teams manage dependencies, track readiness, and follow work through completion.
•          Improve reporting accuracy by tightening workflow use, issue hygiene, and field consistency.
•          Help teams and leads get useful status and delivery information without constant manual collection.

Data Governance, Audit, and Cleanup

•          Maintain accurate and consistent Jira and Confluence data used for delivery, reporting, and traceability.
•          Set and reinforce clear expectations for issue hygiene, status use, field completion, linking, ownership, and metadata.
•          Conduct regular audits of workflows, issue types, fields, dashboards, automations, permissions, spaces, and excess configuration.
•          Identify and correct stale data, duplicate fields, unused workflows, broken automations, outdated dashboards, and orphaned Confluence content.
•          Lead cleanup work that reduces clutter, makes the tools easier to use, and improves confidence in the data.
•          Work with teams and stakeholders to keep data current and usable as part of normal day-to-day work.

Platform Improvement and User Support

•          Maintain a backlog of platform fixes, support needs, cleanup work, automation opportunities, and usability improvements.
•          Use automation where it clearly reduces manual work.
•          Develop lightweight guidance, SOPs, job aids, templates, and training materials as needed.
•          Coach users on effective Jira and Confluence use in the context of actual delivery work.
•          Use repeat support issues to identify where configuration, cleanup, simplification, or user guidance needs to improve.

________________________________________

Key Collaboration Relationships

•          Product Managers / Product Owners: backlog readiness, scope clarity, planning inputs, prioritization changes
•          Technical Leads: sequencing, technical dependencies, delivery risks, release impacts, environment constraints
•          Team Leads / Scrum Masters / Delivery Leads: day-to-day execution challenges, blockers, dependency coordination, flow issues
•          Teams: work tracking, issue hygiene, tool usability, planning and execution support
•          Flow / Reporting / Insights roles: measurement needs, reporting reliability, dashboard requirements, data quality concerns
•          Program or Section Leadership: execution concerns, milestone risks, cross-team constraints, visibility needs
•          Enterprise Atlassian support personnel: broader platform issues or changes requiring higher-level support

________________________________________

Skills and Qualifications:

Required Education

•  Bachelor’s degree in Business Administration or a related field, or an equivalent combination of education and 5–7 years of relevant experience.

Required Qualifications

•  Experience serving in a Release Train Engineer, Agile delivery, delivery operations, or similar multi-team execution role.
•  Hands-on experience administering Jira and Confluence.
•  Experience facilitating cross-team planning, Scrum of Scrums, dependency management, and release or milestone coordination.
•  Ability to configure workflows, boards, fields, dashboards, automations, filters, and permissions in Jira and Confluence.
•  Ability to identify and improve execution friction, flow issues, and coordination problems across teams.
•  Experience supporting reporting, dashboard design, and delivery visibility needs.
•  Experience with data hygiene, audit practices, platform cleanup, and reporting reliability.
•  Strong judgment in balancing team usability, reporting needs, and maintainable configuration.
•  Strong collaboration skills across product, technical, delivery, and leadership stakeholders.
•          Teams get practical support that helps work move.
•          Cross-team syncs result in clear actions, owners, and follow-through.
•          Dependencies, blockers, and milestone risks are identified and addressed early.
•          Planning decisions carry through into execution with less churn, confusion, or delay.
•          Jira and Confluence are easier to use and better aligned to delivery needs.
•          Reporting and dashboards reflect reliable underlying data.
•          Duplicate, stale, unused, or low-value configuration decreases over time.
•          Issue hygiene and data consistency improve across teams.
•          Cleanup and audit work improve confidence in Jira and Confluence as working systems.
•          Delivery flow, coordination, and predictability improve over time.