No, his responsibility is the operation of the service. The operation of the hardware it runs on is not the primary duty, it is a... side effect? Not sure how to put that. It's like saying a building manager should be a carpenter or a plumber. It might be an unsurprising de facto situation, but the primary duty is not to be a carpenter or plumber.
I should mention I was briefly working for him at this company, but ran away screaming for reasons not really related to him or the hardware, so I'm fairly familiar with what the deal is. It's not just grunt-level operations, it's operations engineering, complete with in-depth troubleshooting of application problems. This is what Google calls SRE.
And they're not buying systems one at a time, they buy them by the truckload from Rackable/SGI, and do have dedicated staff for the things you're talking about. That's the whole problem. The dedicated staff together with the other costs I mentioned end up being more than they would spend being a major customer of a dedicated "cloud" provider.