I think it depends to a large extent on whether you're paying for results or time.
The remote contracting market, especially for fixed rate contracts, is not driven by locations. It's driven by who in the globe can do a particular job at a particular price, and there's a wide variety in how much that translates to in "goats" for different developers.
Traditional remote jobs are still driven mostly by paying for a fixed amount of time working on the job per week. As such, they're not hiring for a "job to be done"—they're hiring you as an individual. To do that, they just need to pay more than the next best option, which is frequently determined by the local labor market.
Given that, option 1 makes a lot of sense, with the catch that you have to have a clear policy so it's known ahead of time. Also realize that Ann might try to get a better replacement offer and then you'll have to match to the "new" market for that location.
The remote contracting market, especially for fixed rate contracts, is not driven by locations. It's driven by who in the globe can do a particular job at a particular price, and there's a wide variety in how much that translates to in "goats" for different developers.
Traditional remote jobs are still driven mostly by paying for a fixed amount of time working on the job per week. As such, they're not hiring for a "job to be done"—they're hiring you as an individual. To do that, they just need to pay more than the next best option, which is frequently determined by the local labor market.
Given that, option 1 makes a lot of sense, with the catch that you have to have a clear policy so it's known ahead of time. Also realize that Ann might try to get a better replacement offer and then you'll have to match to the "new" market for that location.
reply