How to speed up CI builds without cutting test coverage

I worked on a service where the CI build had slowly grown to almost half an hour. Nobody owned it because it was not exactly a product bug, but every small change felt heavier than it should. The first useful step was not adding more runners. We printed the slowest jobs for two weeks and found three boring problems: integration tests creating the same fixtures over and over, frontend lint running…