41–50 of 57 posts
I think the biggest challenge is finding the right people that meet your level of expectations. This is a challenge no matter where the person is located.
No. At least not through the normal application process. I have worked with many brilliant Indian people, and some of my favorite colleagues were Indian. However, there is so much "noise" in India's talent pool [1] - bad communication, fake degrees, fake profiles, sloppy work - that it just takes too much effort filtering through it. I understand that it's biased, but simply not hiring from India seems to be the bett…
No, I do not even accept applications from India. The credentials are usually faked and the work sloppy.
> sloppy work Or as I have recently taken to call it, geeksforgeeks culture.
No, I do not even accept applications from India. The credentials are usually faked and the work sloppy.
A bunch of white people bashing devs in India and another group of wannabe NRIs sucking up to them. Let me show the perspective of an Indian engineer. I don't want to work for remotely for a team with half a day of time zone difference. India has tons of interesting startups doing exciting work. Most of the bright engineers are happy with the jobs or have their own network of other bright engineers to help with job h…
I'm sure the marketplace will reward you with all that you earn and deserve. Best of luck and we'll see you out there.
Would you consider Github/tech blogs before rejecting the applicant right away? As an Indian I agree with the sloppy work culture and almost zero effort in actually learning things.
I am in Seattle, and have worked on teams with engineers located across the US, across Europe and in Mexico. I have found talented engineers everywhere. As mentioned below, there are political reasons you might not want to this. And, there are some logistical hurdles in terms of local regulations which, in my experience, can be overcome and plenty of companies have shown that is the case. So, to answer your question…
All you say is true. The solution is to centralize engineering in a time zone. It doesn't need to be a time zone in the US.
Earlier quoted context omitted.
Congrats on this bold justification you’ve created to justify your role in the exploitation process, but you’re not fooling anyone. There is no moral or material logic for this nonsense.
But hang on, not all US teams are paid the same either. A dev in kansas gets less than a dev in SV. Are you arguing that all devs everywhere should be paid the same for moral reasons? (genuine question) Is it not more morally ethical to hire 2 devs in denver for the price of 1 in New York, thus providing employment for twice as many americans?
It’s important to take seriously because the logical outcome of this turn to remote work will otherwise be greater class divisions than the world has ever known, within the same economic structures.
Earlier quoted context omitted.
Congrats on this bold justification you’ve created to justify your role in the exploitation process, but you’re not fooling anyone. There is no moral or material logic for this nonsense.
So are you saying if you hire a foreign remote worker, they should be get the same salary as a US worker? Moreover, how could paying a standard wage for a country ever be considered exploitation?
The global labor trade has proven a disaster for decades on end. It has destroyed the American middle class. There is no moral justification for any of it.
Earlier quoted context omitted.
All you say is true. The solution is to centralize engineering in a time zone. It doesn't need to be a time zone in the US.
To my way of thinking, there is also a lot of communication with "requesters" (business people, designers, product managers, etc.), so they need to be in the time zone as the engineers too.