Skip to main content

Kaseya Careers

Release Train Engineer

Miami, FLmidAdded yesterday

About this role

Kaseya seeks a Release Train Engineer to establish a new Agile Release Train capability for the Business Applications Team transforming their Lead-to-Cash platform. This is a greenfield role requiring someone who has built ART structures from scratch—there's no existing playbook, and success depends on earning trust across engineering and product to systematically establish ceremonies, practices, and dependency management infrastructure.

What you'll do

  • Conduct rapid organizational assessment to map team topology, current ceremonies, tooling, and identify delivery bottlenecks
  • Define and socialize the RTE function across the organization and build buy-in with engineering leads, product managers, and senior leadership
  • Stand up or retrofit Program Increment Planning cadences and establish predictable release ceremonies
  • Own the dependency board—actively track, visualize, and resolve cross-team dependencies using tools like Jira
  • Build and scale SAFe or similar agile frameworks across multiple teams to improve delivery predictability
  • Partner with engineering and product leadership to remove impediments and optimize flow

What they're looking for

  • Agile Release Train (ART) and SAFe framework experience
  • Organizational design and change management
  • Dependency tracking and cross-functional coordination
  • Jira and agile tooling expertise
  • Program-level planning and PI Planning facilitation
  • Stakeholder management and influence without authority
  • Technical acumen in software delivery
  • Ability to operate without predefined structure
Apply on the employer's site

Opens the official application on the employer’s site. No login required.

Kaseya Careers

View all jobs at Kaseya Careers

Likely interview questions

  • Walk us through a time when you built an ART or release train capability from scratch—what was the existing state, and how did you gain buy-in from skeptical engineers or product teams?
  • How do you approach identifying and surfacing cross-team dependencies in a large, complex organization?