I would also like information about remote coding for my students. I will e-mail you in just a bit. I usually tell my students that it is not practical for them to think they can get a remote coding job until they have some experience behind them. Some of them do want this to be their long term goal so I would appreciate information I can pass on to them so that they are discouraged.
I coded remotely for 4 years for a billing company. Although I had coding experience when I was hired, my boss told me in the interview that often times, she
prefers to hire new coders without experience because then she doesn't have any "bad habits" to break and she can more easily mold them as coders. So...I say that to say, don't rule out remote coding for newbees. I liked coding remote okay, but after a while, it got really, really, really boring. I think it depends on the kind of coding you're doing. I was doing ED and I mean, even though it's ED, it's still your standard, nausea, chest pain, vomiting, bug bites (yes people come to the ED for bug bites), etc. The hospital that I coded for wasn't trauma 1 so, the chief complaints were pretty basic and eventually it became pretty monotonous. I liked the flexibility of schedule, but I want to be clear, I
did not have the luxury of working at my own pace. It was a production based job in which I was expected to code (score E&M, any surgeries: fracture care, aspirations, repairs, etc., ancillary charges: EKGs, pulse ox, etc.
AND correct diagnoses) between 150-200 charts in an 8 hour time period once my probationary period ended. So...there are upsides and downsides to remote coding. I'd say do plenty of research on the company for which you contemplate working, find out their expectations, etc., and speak with those who code or have coded remotely. Best wishes!
