So if I can outsource most of my functions to another country and pay 75% less, should I also give my US staff a 75% pay cut?
Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:I’m federal government and we decrease pay based on where you live remotely. Except I think you can’t make more than where your work is located. Like we get the DC pay scale and you can’t be paid the nyc scale even if you’re working in nyc because we don’t need you to be in nyc.
This is kind of the opposite of how it works. There is a base salary for your work. Then the government increases pay based on cost of living where your work is located. If it's an office in DC, you get DC locality pay on top of the "base." If you go remote to a lower cost area, then you get whatever the locality pay is for that area because that's your new work location. E.g. Atlanta gets a slightly smaller COL increase than DC, and rural northern PA gets just the base.
You are right that you can't opt to get higher pay than where your office is located, because that would be a net loss to the government of having you work remotely.
Honestly, none of this seems remotely unfair to me.
It does to me. If we apply locality pay, I think we should also pay single people less. After all, they don’t have a family to support. Or what about people who have a working spouse?
I think an employer should pay a salary commensurate with the job and job market - not the lifestyle of the employee.
So if I can outsource most of my functions to another country and pay 75% less, should I also give my US staff a 75% pay cut?
DP. Sweet pea, you are trying to operate way above your pay grade. Maybe take an intro to economics course.
Cool.
Wanna answer the question, or just want to insult?
If your company would still need some US-based employees, then you will need to pay a salary that will attract the necessary employees, even if it more than you would need to pay similar employees in another country. If you want to outsource the rest, that is your choice.
For those US-based employees, if you need them near your physical office in a high COL area, then you need to pay huge local rate for that job. If the job can be done remotely, you can cut costs by employing people from lower COL areas. This is pretty basic management.
I am an attorney, and have been amazed at the shortsightedness of our legal assistants and other support staff clamoring to work from home full-time. They seem to have zero appreciation that if they demonstrate the job can be done just as efficiently fully remotely, there is no reason for us to pay DC wages for local legal assistants when we can hire people in the Midwest for a fraction of the cost.
Because companies are inefficient and everyone knows this. Technically anyone who works on a computer could have their job replaced via outsourcing. Including your job. But the reality is that it doesn’t happen. There are a variety of challenges in outsourcing work - the language barrier, time zone, culture, expense of one of these outsource workers traveling the globe to reach the home office etc.
Technically most office workers just demonstrated for two years that their job could be done remotely. Why don’t you try to save your company some money and hire legal assistants in India?
Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:I’m federal government and we decrease pay based on where you live remotely. Except I think you can’t make more than where your work is located. Like we get the DC pay scale and you can’t be paid the nyc scale even if you’re working in nyc because we don’t need you to be in nyc.
This is kind of the opposite of how it works. There is a base salary for your work. Then the government increases pay based on cost of living where your work is located. If it's an office in DC, you get DC locality pay on top of the "base." If you go remote to a lower cost area, then you get whatever the locality pay is for that area because that's your new work location. E.g. Atlanta gets a slightly smaller COL increase than DC, and rural northern PA gets just the base.
You are right that you can't opt to get higher pay than where your office is located, because that would be a net loss to the government of having you work remotely.
Honestly, none of this seems remotely unfair to me.
It does to me. If we apply locality pay, I think we should also pay single people less. After all, they don’t have a family to support. Or what about people who have a working spouse?
I think an employer should pay a salary commensurate with the job and job market - not the lifestyle of the employee.
So if I can outsource most of my functions to another country and pay 75% less, should I also give my US staff a 75% pay cut?
DP. Sweet pea, you are trying to operate way above your pay grade. Maybe take an intro to economics course.
Cool.
Wanna answer the question, or just want to insult?
If your company would still need some US-based employees, then you will need to pay a salary that will attract the necessary employees, even if it more than you would need to pay similar employees in another country. If you want to outsource the rest, that is your choice.
For those US-based employees, if you need them near your physical office in a high COL area, then you need to pay huge local rate for that job. If the job can be done remotely, you can cut costs by employing people from lower COL areas. This is pretty basic management.
I am an attorney, and have been amazed at the shortsightedness of our legal assistants and other support staff clamoring to work from home full-time. They seem to have zero appreciation that if they demonstrate the job can be done just as efficiently fully remotely, there is no reason for us to pay DC wages for local legal assistants when we can hire people in the Midwest for a fraction of the cost.
Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:I’m federal government and we decrease pay based on where you live remotely. Except I think you can’t make more than where your work is located. Like we get the DC pay scale and you can’t be paid the nyc scale even if you’re working in nyc because we don’t need you to be in nyc.
This is kind of the opposite of how it works. There is a base salary for your work. Then the government increases pay based on cost of living where your work is located. If it's an office in DC, you get DC locality pay on top of the "base." If you go remote to a lower cost area, then you get whatever the locality pay is for that area because that's your new work location. E.g. Atlanta gets a slightly smaller COL increase than DC, and rural northern PA gets just the base.
You are right that you can't opt to get higher pay than where your office is located, because that would be a net loss to the government of having you work remotely.
Honestly, none of this seems remotely unfair to me.
It does to me. If we apply locality pay, I think we should also pay single people less. After all, they don’t have a family to support. Or what about people who have a working spouse?
I think an employer should pay a salary commensurate with the job and job market - not the lifestyle of the employee.
So if I can outsource most of my functions to another country and pay 75% less, should I also give my US staff a 75% pay cut?
DP. Sweet pea, you are trying to operate way above your pay grade. Maybe take an intro to economics course.
Cool.
Wanna answer the question, or just want to insult?
If your company would still need some US-based employees, then you will need to pay a salary that will attract the necessary employees, even if it more than you would need to pay similar employees in another country. If you want to outsource the rest, that is your choice.
For those US-based employees, if you need them near your physical office in a high COL area, then you need to pay huge local rate for that job. If the job can be done remotely, you can cut costs by employing people from lower COL areas. This is pretty basic management.
I am an attorney, and have been amazed at the shortsightedness of our legal assistants and other support staff clamoring to work from home full-time. They seem to have zero appreciation that if they demonstrate the job can be done just as efficiently fully remotely, there is no reason for us to pay DC wages for local legal assistants when we can hire people in the Midwest for a fraction of the cost.
Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:I’m federal government and we decrease pay based on where you live remotely. Except I think you can’t make more than where your work is located. Like we get the DC pay scale and you can’t be paid the nyc scale even if you’re working in nyc because we don’t need you to be in nyc.
This is kind of the opposite of how it works. There is a base salary for your work. Then the government increases pay based on cost of living where your work is located. If it's an office in DC, you get DC locality pay on top of the "base." If you go remote to a lower cost area, then you get whatever the locality pay is for that area because that's your new work location. E.g. Atlanta gets a slightly smaller COL increase than DC, and rural northern PA gets just the base.
You are right that you can't opt to get higher pay than where your office is located, because that would be a net loss to the government of having you work remotely.
Honestly, none of this seems remotely unfair to me.
It does to me. If we apply locality pay, I think we should also pay single people less. After all, they don’t have a family to support. Or what about people who have a working spouse?
I think an employer should pay a salary commensurate with the job and job market - not the lifestyle of the employee.
DP.. you seem really young and idealistic. That isn't how it works. It's about COL and commiserate pay. You having kids has nothing to do with your employer. Your employer is paying for your work and will pay you market rate of where you live. That's standard practice.
Don’t see how COL is any more or less than familial status. Or perhaps suburban versus. Perhaps they should lower salaries of workers who live in exurbs? Or what about employees who inherited their home?
Again, you seem really young and naive.
Your family life choices have nothing to do with your employer.
Exurbs are still part of the metro area, and pay will commiserate.
Then why are you suggesting that moving my a family to a different city should result in a decrease in pay?
Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:I’m federal government and we decrease pay based on where you live remotely. Except I think you can’t make more than where your work is located. Like we get the DC pay scale and you can’t be paid the nyc scale even if you’re working in nyc because we don’t need you to be in nyc.
This is kind of the opposite of how it works. There is a base salary for your work. Then the government increases pay based on cost of living where your work is located. If it's an office in DC, you get DC locality pay on top of the "base." If you go remote to a lower cost area, then you get whatever the locality pay is for that area because that's your new work location. E.g. Atlanta gets a slightly smaller COL increase than DC, and rural northern PA gets just the base.
You are right that you can't opt to get higher pay than where your office is located, because that would be a net loss to the government of having you work remotely.
Honestly, none of this seems remotely unfair to me.
It does to me. If we apply locality pay, I think we should also pay single people less. After all, they don’t have a family to support. Or what about people who have a working spouse?
I think an employer should pay a salary commensurate with the job and job market - not the lifestyle of the employee.
So if I can outsource most of my functions to another country and pay 75% less, should I also give my US staff a 75% pay cut?
DP. Sweet pea, you are trying to operate way above your pay grade. Maybe take an intro to economics course.
Cool.
Wanna answer the question, or just want to insult?
Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:+1 There was a hug thread about this in late 2020 (I think) when Facebook announced this approach. Even with adjusting for cost of living differences, it’s not like these big tech companies are paying small company crap wages. Why should Google pay SV wages for the employees that opted to move to Idaho?Anonymous wrote:This is what many companies are doing. Its not an uncommon practice. PreCovid we had many threads about how much of a pay cut was worth a remote position. I took one and it worked well for me for many years! No surprises here
Because wages should be tied to the work and not the location.
You can believe that all you want, but employers disagree.
That's BS. Most employee who work remotely are highly sought after. The ones who go into office have to b/c they don't have options.
That’s not always true. Plenty of grunt work that didn’t require much talent gets shoveled off to remote employees. I think some full-time remote workers think too much of themselves and that’s part of the problem. It exists in-office too, but remote workers aren’t around people who can help deflate their self-perceptions.
Just b/c someone is in the office, doesn't mean they are productive. Plenty of people go to office and waste time--go out to lunch, shop online, gossip, etc. Oh but b/c they are in person, they must be working or are more committed...![]()
You missed the point entirely. Many full time remote workers tend to think they are more valuable than they really are. They don’t have anyone to keep them in check or to give them a sense of reality. I’m not talking strictly about productivity. You are correct that people can waste time in either setting. And just because you’re remote working full time doesn’t mean you got to do that because you’re some Demi-god.
Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:I’m federal government and we decrease pay based on where you live remotely. Except I think you can’t make more than where your work is located. Like we get the DC pay scale and you can’t be paid the nyc scale even if you’re working in nyc because we don’t need you to be in nyc.
This is kind of the opposite of how it works. There is a base salary for your work. Then the government increases pay based on cost of living where your work is located. If it's an office in DC, you get DC locality pay on top of the "base." If you go remote to a lower cost area, then you get whatever the locality pay is for that area because that's your new work location. E.g. Atlanta gets a slightly smaller COL increase than DC, and rural northern PA gets just the base.
You are right that you can't opt to get higher pay than where your office is located, because that would be a net loss to the government of having you work remotely.
Honestly, none of this seems remotely unfair to me.
It does to me. If we apply locality pay, I think we should also pay single people less. After all, they don’t have a family to support. Or what about people who have a working spouse?
I think an employer should pay a salary commensurate with the job and job market - not the lifestyle of the employee.
DP.. you seem really young and idealistic. That isn't how it works. It's about COL and commiserate pay. You having kids has nothing to do with your employer. Your employer is paying for your work and will pay you market rate of where you live. That's standard practice.
Don’t see how COL is any more or less than familial status. Or perhaps suburban versus. Perhaps they should lower salaries of workers who live in exurbs? Or what about employees who inherited their home?
Again, you seem really young and naive.
Your family life choices have nothing to do with your employer.
Exurbs are still part of the metro area, and pay will commiserate.
Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:I’m federal government and we decrease pay based on where you live remotely. Except I think you can’t make more than where your work is located. Like we get the DC pay scale and you can’t be paid the nyc scale even if you’re working in nyc because we don’t need you to be in nyc.
This is kind of the opposite of how it works. There is a base salary for your work. Then the government increases pay based on cost of living where your work is located. If it's an office in DC, you get DC locality pay on top of the "base." If you go remote to a lower cost area, then you get whatever the locality pay is for that area because that's your new work location. E.g. Atlanta gets a slightly smaller COL increase than DC, and rural northern PA gets just the base.
You are right that you can't opt to get higher pay than where your office is located, because that would be a net loss to the government of having you work remotely.
Honestly, none of this seems remotely unfair to me.
It does to me. If we apply locality pay, I think we should also pay single people less. After all, they don’t have a family to support. Or what about people who have a working spouse?
I think an employer should pay a salary commensurate with the job and job market - not the lifestyle of the employee.
So if I can outsource most of my functions to another country and pay 75% less, should I also give my US staff a 75% pay cut?
DP. Sweet pea, you are trying to operate way above your pay grade. Maybe take an intro to economics course.
Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:I’m federal government and we decrease pay based on where you live remotely. Except I think you can’t make more than where your work is located. Like we get the DC pay scale and you can’t be paid the nyc scale even if you’re working in nyc because we don’t need you to be in nyc.
This is kind of the opposite of how it works. There is a base salary for your work. Then the government increases pay based on cost of living where your work is located. If it's an office in DC, you get DC locality pay on top of the "base." If you go remote to a lower cost area, then you get whatever the locality pay is for that area because that's your new work location. E.g. Atlanta gets a slightly smaller COL increase than DC, and rural northern PA gets just the base.
You are right that you can't opt to get higher pay than where your office is located, because that would be a net loss to the government of having you work remotely.
Honestly, none of this seems remotely unfair to me.
It does to me. If we apply locality pay, I think we should also pay single people less. After all, they don’t have a family to support. Or what about people who have a working spouse?
I think an employer should pay a salary commensurate with the job and job market - not the lifestyle of the employee.
So if I can outsource most of my functions to another country and pay 75% less, should I also give my US staff a 75% pay cut?
Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:I’m federal government and we decrease pay based on where you live remotely. Except I think you can’t make more than where your work is located. Like we get the DC pay scale and you can’t be paid the nyc scale even if you’re working in nyc because we don’t need you to be in nyc.
This is kind of the opposite of how it works. There is a base salary for your work. Then the government increases pay based on cost of living where your work is located. If it's an office in DC, you get DC locality pay on top of the "base." If you go remote to a lower cost area, then you get whatever the locality pay is for that area because that's your new work location. E.g. Atlanta gets a slightly smaller COL increase than DC, and rural northern PA gets just the base.
You are right that you can't opt to get higher pay than where your office is located, because that would be a net loss to the government of having you work remotely.
Honestly, none of this seems remotely unfair to me.
It does to me. If we apply locality pay, I think we should also pay single people less. After all, they don’t have a family to support. Or what about people who have a working spouse?
I think an employer should pay a salary commensurate with the job and job market - not the lifestyle of the employee.
DP.. you seem really young and idealistic. That isn't how it works. It's about COL and commiserate pay. You having kids has nothing to do with your employer. Your employer is paying for your work and will pay you market rate of where you live. That's standard practice.
Don’t see how COL is any more or less than familial status. Or perhaps suburban versus. Perhaps they should lower salaries of workers who live in exurbs? Or what about employees who inherited their home?
Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:I’m federal government and we decrease pay based on where you live remotely. Except I think you can’t make more than where your work is located. Like we get the DC pay scale and you can’t be paid the nyc scale even if you’re working in nyc because we don’t need you to be in nyc.
This is kind of the opposite of how it works. There is a base salary for your work. Then the government increases pay based on cost of living where your work is located. If it's an office in DC, you get DC locality pay on top of the "base." If you go remote to a lower cost area, then you get whatever the locality pay is for that area because that's your new work location. E.g. Atlanta gets a slightly smaller COL increase than DC, and rural northern PA gets just the base.
You are right that you can't opt to get higher pay than where your office is located, because that would be a net loss to the government of having you work remotely.
Honestly, none of this seems remotely unfair to me.
It does to me. If we apply locality pay, I think we should also pay single people less. After all, they don’t have a family to support. Or what about people who have a working spouse?
I think an employer should pay a salary commensurate with the job and job market - not the lifestyle of the employee.
DP.. you seem really young and idealistic. That isn't how it works. It's about COL and commiserate pay. You having kids has nothing to do with your employer. Your employer is paying for your work and will pay you market rate of where you live. That's standard practice.
Don’t see how COL is any more or less than familial status. Or perhaps suburban versus. Perhaps they should lower salaries of workers who live in exurbs? Or what about employees who inherited their home?
Anonymous wrote:Anonymous wrote:Anonymous wrote:I’m federal government and we decrease pay based on where you live remotely. Except I think you can’t make more than where your work is located. Like we get the DC pay scale and you can’t be paid the nyc scale even if you’re working in nyc because we don’t need you to be in nyc.
This is kind of the opposite of how it works. There is a base salary for your work. Then the government increases pay based on cost of living where your work is located. If it's an office in DC, you get DC locality pay on top of the "base." If you go remote to a lower cost area, then you get whatever the locality pay is for that area because that's your new work location. E.g. Atlanta gets a slightly smaller COL increase than DC, and rural northern PA gets just the base.
You are right that you can't opt to get higher pay than where your office is located, because that would be a net loss to the government of having you work remotely.
Honestly, none of this seems remotely unfair to me.
It does to me. If we apply locality pay, I think we should also pay single people less. After all, they don’t have a family to support. Or what about people who have a working spouse?
I think an employer should pay a salary commensurate with the job and job market - not the lifestyle of the employee.
Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:I’m federal government and we decrease pay based on where you live remotely. Except I think you can’t make more than where your work is located. Like we get the DC pay scale and you can’t be paid the nyc scale even if you’re working in nyc because we don’t need you to be in nyc.
This is kind of the opposite of how it works. There is a base salary for your work. Then the government increases pay based on cost of living where your work is located. If it's an office in DC, you get DC locality pay on top of the "base." If you go remote to a lower cost area, then you get whatever the locality pay is for that area because that's your new work location. E.g. Atlanta gets a slightly smaller COL increase than DC, and rural northern PA gets just the base.
You are right that you can't opt to get higher pay than where your office is located, because that would be a net loss to the government of having you work remotely.
Honestly, none of this seems remotely unfair to me.
It does to me. If we apply locality pay, I think we should also pay single people less. After all, they don’t have a family to support. Or what about people who have a working spouse?
I think an employer should pay a salary commensurate with the job and job market - not the lifestyle of the employee.
DP.. you seem really young and idealistic. That isn't how it works. It's about COL and commiserate pay. You having kids has nothing to do with your employer. Your employer is paying for your work and will pay you market rate of where you live. That's standard practice.