Quote:
Originally Posted by iheartthed
I think that's such a bad idea from a career perspective. My friend is an engineer at Apple and was telling me several years ago that Apple was forcing all of its remote workers to either resign or move to California. Not sure if they are still doing it, but it's hardly the only company that has been reconsidering their remote worker policies.
If you're working in a place like Traverse City and get cut, the market is probably pretty shallow. You'll have to scramble to find another remote gig or relocate to a bigger city.
|
He's been working remotely for one of the largest medical insurance providers in the country for over 15 years, and his work is for a long-term government contract. He could retire at any time, but he likes his work and he just keeps socking away savings.
Maybe it doesn't suit everybody in every situation, but there is so much work out there that it's totally feasible to live and work remotely with a lot of programming or computer-related jobs if you don't want to work for Apple or Google. It's just ridiculous to me that anyone would subject themselves to those SF rents or housing costs unless it was absolutely necessary.
Here in Portland a lot of Intel employees work remotely at least part of the week and you can tell which days of the week because the traffic is dramatically worse or better.
State of Oregon employees work remotely all over the state. Same with a lot of HUD field staff. These are big city wages without the need to live in expensive areas. We're going to see this more and more.