3 ms·
I'd be curious to know as well, but I'm guessing he means Europe. I used to work with other Data Scientists based in Europe and was always shocked to learn how
by extr 5y ago
I'd be curious to know as well, but I'm guessing he means Europe. I used to work with other Data Scientists based in Europe and was always shocked to learn how little they got paid, usually less than 50% of american counterparts. And for work like DS where objectives are more abstract and harder to specify, Europeans have enough cultural and literal fluency to be able to fully replace someone from the US. This is in comparison to the situation as I understand it for India-based pure software development, where communication/cultural barriers requires tighter management to use the talent effectively (this is going off what I've heard, I have no personal experience here. so feel free to correct me if my understanding isn't accurate).
So previously being able to utilize offshore talent was basically a skill unto itself. Now you did two interviews with similarly skills candidates and one wants 50% less pay, they just have a british accent.
- EMM_386 5y ago> I'd be curious to know as well, but I'm guessing he means Europe. Other commenters have addressed this, but the term is normally used for teams within +/- the same timezone but at far lower rates for (hopefully) good engineering quality. So if you are US EST, there are "near shore" companies in the US that will coordinate you with South American teams. They generally have a PM in the US and developers outside.
- llampx 5y agoNear-shoring usually refers to someone on the same timezone or nearby physically, like South America or Mexico for the US, or Eastern Europe for Western Europe. In terms of European talent being paid less, yes I agree they are, but there are hidden costs in terms of taxes and compliance that means that companies would rather go to countries which promise an order of magnitude cheaper resources rather than just 50% off.