And they are good at it.
Remote work makes that easier now, but with silicon / EE its not always the most optimal way to work.
Middle America EE is also not building data center class chips or infrastructure most of the time, would it be easier to get one of them up to speed, yes. But it's the equivalent of throwing a front-end engineer into C or embedded programming or vice versa.
My question is more on software roles, those CRUD or React component roles, where the work can be done remotely. Instead of Americans filling those positions, companies may/will simply hire those engineers abroad.
H1B and offshore jobs can be beneficial to America though, and that was why the program started. Sufficient guardrails just never went up and now there is opportunity for some abuse. But that abuse isn't across the board, there is still beneficial H1B and offshoring going on mixed in with abuse.
How would that work if the remote people were employed by a different company that was given a contract by the home company to provide certain pieces of software or specific computing services?
My best effort, the contract is a red herring, we only care about the company that employs the abroad remote employees which is the contractual company in this case. If that contractual company is also abroad, we tax (tariff?) the contract.
But but but I was told that unions will force employers to retrain folks instead of laying them off.
Its Azure Hardware division that manages its first party silicon and its deployment has a huge hardware and electrical engineering presence. These fields don't have as many people in America in them, because Software has paid so much more for the last two decades, why would anyone go EE when they could go CS and make 2-3x more. In other countries, these degrees were paid similar so there is a larger pool to pull from then in America.
You can't train a software engineer overnight to be a silicon engineer