Things like CI times and build process strike me as opportunities. If they're bad, there's a spot you can contribute and make it better. A core piece of that i

Things like CI times and build process strike me as opportunities. If they're bad, there's a spot you can contribute and make it better. A core piece of that is figuring out if they're open to spending times on improvements like these, and figuring out why they haven't: recognition of a problem? Expertise to fix it? Constant time crunch? No prioritization input from dev team? A question might be something along the lines of "As a team would you spend 3x once to save x time for every subsequent sprint/release after that? What's the last example of where you did this?" This applies to CI/build process, unit testing, other automated testing, deployments, etc.