Source: originally from Hungary, lived in London for 6 years, moved to San Francisco 9 years ago. Have worked for US corps from London (as consultant); have been sitting in hiring positions for last 3 corps in US. Things which aren't salient from outside the US, but play major role in hiring non-specialist/non-contractor full-time employees:<p>* Cultural integration to generally to the US, and specifically to the US way of doing business. Except for a few rare cases, software is ubiquitously embedded in the culture that requires such solution. This has a _lot_ of non-salient culture-domain-specific parts that nonetheless comes as second nature to peeps growing up here. For example -I'm implementing a module that requires accounting for eg income tax brackets. A person from the EU would fire an email to product asking what these are. Here we come to the "US way of doing business", moving fast: a senior US sw engineer at a startup is enabled, and expected to do whatever it takes to drive things forward. So, the right move is to go to IRS website, look up the table, write an implementation, and note to product to double-check it.<p>* Related to this, "extremely remote" (different timezone + different country) requires a degree of autonomy, requires a level of trust, that is very difficult to build over videoconferences alone. Most successful "extreme remote" I've seen always added at least a weekend of flying peeps into retreats, doing mindmelt.<p>* The issue of trust: US is a high-trust country; it is default expected that everything you say is true, and you're not omitting materially relevant facts; and there are severe (but only country-wide) consequences of getting caught. For international peeps, trust level is highly varied, with very limited ability to enforce.<p>These are the top-level bits on making hiring decisions, and the root causes why none of the items on your list are being addressed.