Not sure what asynchronous means in this context -- sounds like freelancing.<p>If you can add value and solve business problems effectively then you can do most programming/IT jobs remotely and on your own schedule. Some jobs require on-site presence (system admin for a data center, for example). I have worked at freelance programming and system admin (cloud servers) for over a decade while traveling all over the world, for quite a few US-based companies. My customers have business problems to solve, they don't care where I do it from or what hours I keep.<p>When selling yourself to a customer (or employer) you have to persuade them that you can add value and solve problems. You don't want to start the discussion making demands about your work habits. Focus on what they need you to do, not where or when or how you will do it. Don't filter potential jobs by "remote," almost all jobs in this field can work remotely for the right person, meaning a person who solves problems and doesn't create headaches for the customer/employer.<p>In my experience, listening to my customers and keeping them informed gives me a significant advantage. Domain expertise helps a lot -- understanding the business requirements and needs so you deliver what your customer wants. The most common complaint I hear from my customers: The last developer, freelancer, or outsourcing shop didn't communicate. That means answering emails, Slack messages, phone calls right away so your customer (or employer) doesn't think you disappeared.<p>Cloud server infrastructure/administration lends itself to remote work. I do a lot of that.<p>Programming also lends itself to remote work on my own schedule. I specialize in working on abandoned and legacy code bases -- meaning the original developers left or no longer answer emails and calls from the customer. Most of that work involves web sites and databases.