Alot of HQ jobs, like CBG HQs etc, could likely be done by well trained civilian clerical staff e.g., pay and benefits, claims and other financial transactions, as well as a host of HR and other, EA/Admin roles.
Ops and training roles, not so much., although it doesn't take an experienced Capt/WO to call someone and make training area/ range bookings...
I guess for context I mean very specific technical kind of jobs, but probably would also apply to more detail orientated supply jobs as well on the logistics side or financial side where there is a set of rules and standards, and then actually doing things that makes sense for the CAF within them.
For the Navy, the 3 PMOs, and the EGPM have a lot of the LCdr - Cdr jobs for naval technical officers, and is a mix of some specific technical niches, general contracting/QC and all the other things that go into supporting/building/delivering ships. With things like sub replacement on the horizon in general those are almost all Ottawa based jobs, and is a huge centre of gravity for the trade.
Those are all mix of military and civilian staff, but I guess what I had in mind when I meant when talking about longer postings (if the person wanted to). Some of the specific positions are soul sucking, thankless nightmares so YMMV, but sending someone off to do some kind of 2 year PG on radars, ammo, fire control, damage control etc, then sticking them in the sponsor position for a year or 2 before posting them to jobs where they don't touch that specialist knowledge again doesn't really seem like a good ROI.
One easy example; getting ships built to commercial standards. Standard commercial firemain design, based on civilain context, doesn't actually work because we do offensive firefighting and have some more advanced hose handling that doesn't use constant water streams. This is pretty obvious if you are a sailor trained in our FF, but if you are just ticking a box for class society looks fine, so an engineer off the street wouldn't know that. Stuff like that is why we have CAF folks as part of projects, but it takes a while to get comfortable in the job before you even notice things like that.
So obvious benefits for the operational side, as the tech staff on the PMO considers real world context, so getting to IOC/FOC should generally be easier (assuming comments on the design review actually result in changes vice being ignored).
It's also pretty normal to bounce back and forth between the coasts, MEPM and the PMOs for NTOs, but with the CoL and housing these days, it's unpalatable for a lot of people, especially if you lose money once or twice on a move to bounce around if staying in a geolocation is an option.