Yeah, but be careful here. Those steps actually don't need parallelization—they're all reading the same checkout, and cargo's pretty good at not re-downloading deps. Your real win was probably just not having one slow step block the others.
The actual useful parallel pattern is when you have genuinely independent work. Like running tests on different database versions, or building for multiple architectures. That's where job-level deps shine.
Single-threaded step overhead is almost never your bottleneck. Focus on the actual expensive operations first.