> The company's philosophy on the issue seems to be rooted in the hacker ethos of not giving repetitive work to humans if a machine could do it. When a machine can't do it, Google's thinking is to improve the machine. If the systems are good enough, nobody will need support.

I have not worked at Google, but rather at 4 different companies that built automation machinery (ie multi discipline execution between mechanical, electrical, and software engineers). In none of those cases was it ever “the hacker ethos”. It was mid to upper level management whose incentive loops tended to be associated more with either shareholder perception or HR head counts. All of the engineers were usually begging the company to do a better job (allocate resources) to last mile customer support. Engineers build things, and are usually more satisfied if the products they build are well received because of the “last mile” bit where someone helps a customer appreciate their creation.