Eastern Europe. One job was on East Coast, which is not that terrible in terms of timezone differences. The other one was in SF, which I honestly though would b

Eastern Europe. One job was on East Coast, which is not that terrible in terms of timezone differences. The other one was in SF, which I honestly though would be too much of a stretch (but applied anyway) - it turns out they found a way to make a tightly-knight coding team across nine timezones work reasonably well. As for finding remote jobs, I think it's good to be experienced with something niche or in very high demand like Clojure, Haskel, Spark etc. Companies can easily find locals to work on popular technologies, but for the uncommon or hot ones, they sometimes need to bite the bullet and build a remote team - even if they would prefer not to.