How would you answer an interview scenario involving reusable workflows?

In an interview, I would first define reusable workflows and the problem it solves, then explain how I would define a stable interface, version shared workflows, keep permissions explicit, document required secrets and outputs, test changes before broad rollout, and avoid hiding repository-specific logic in a generic template. I would also call out the main failure mode: changing a shared workflow in place without version control or compatibility testing can break many repositories at once. Finally, I would describe how I would test, monitor, and safely roll back or recover the solution.