In my anecdotal experience, you can't do anything outside of the C-suite. If a company is going to replace in-house employees and local contractors with offsho

In my anecdotal experience, you can't do anything outside of the C-suite. If a company is going to replace in-house employees and local contractors with offshore contractors, nothing will stop that, except for a few months of working with offshore contractors. If they get a good offshore team, they won't ever go back. If they get a bad one, they might learn a lesson from it. You can't save them from themselves. As an employee, keep your skills polished and your resume ready. Build up a reserve of savings so that if you are ever asked to transition your job to your replacement, you can more safely quit the doomed job and focus on looking for a new job with a future instead. As a contractor, cultivate a greater diversity of clients and ask for more money than you think you're worth. Companies that squirm at the asking price will try to replace you with someone cheaper eventually, so you might as well make it easy for them to signal their cheapness as early as possible. Also anecdotally, cleaning up the mess from an offshoring gone bad is not enjoyable work. I wouldn't scream it from the rooftops, but other developers in your network who might be tapped by that company to do it in the future will probably appreciate a heads-up on what happened, to either avoid the client or charge a premium. You could follow up with the company yourself, but would you really want to?