The article title is intentionally click-baity. The extent to which it's true entirely depends on what "your job" is. Routine, non-creative work that can be p

The article title is intentionally click-baity. The extent to which it's true entirely depends on what "your job" is. Routine, non-creative work that can be performed asynchronously, with limited contact with others - the tech equivalent of craft piecework - sure, that can usually be done from anywhere: things like answering (simple) tech support requests, maintaining a static codebase with no new requirements, or implementing a feature for which the requirements and technical design have already been specified by others. Having myself worked on teams that located such tasks in lower-cost-of-labor regions, I can attest that most of those cost savings have already been realized. But creative work, like proposing the problems to solve in the first place, facilitating the discussion of how to solve them, and designing the technical and human solution - especially for problems at the intersection of technology and culture - those are not easily shifted to remote work. If the outsourced/remote worker is competent enough to work in that kind of capacity remotely, they will cost as much the non-remote worker.